Same issue after upgrading from vCenter 6.5.0 Update 1c to Update 1g.
↧
Re: Failed to start Create Volatile Files and Directories (/usr/lib/tmpfiles.d/named.conf:1] Unknown user 'named'.)
↧
Re: Unable to locate VM and VMX file after unregistered it from a host
Thanks guys!
After running the command find /vmfs/ -iname *.vmx I was still unable to locate the vm. So, I decided to go and restore the vm from backup and I noticed that the virtual machines files names were completely different that the actual virtual machine. So, at some point that server had a different name. Long story short I was able to find the actual server and re associate the vmx file to a host. All is well now. Thank you guys for the assistance and advice.
↧
↧
VM Disk Latency in Seconds - Why the large delta.
Hello, I have been scratching my head with the results of a report from Vrealize Operations Manager. It is listed under Performance, Summary| MAX Vm Disk Latency (ms)
There is a VM Disk Latency (95th percentile) column. Out of our 30-40 datastores, there are two used for VDI's that are in seconds. I have been unable to find a reason for this. I have looked at the flash storage array, the hosts, used esxtop, used iometer... I do see a reference in the vRealize Operations Manager manual that Datastore | Disk Command Latency shows the adjusted read and write latency on the datastore level. I did see that there was quite a bit more read IO's than write IO's.
At this point I'm wondering if it has to do with firmware/drivers/incorrect readings? Esx is at 6.5.0, on a Cisco UCS.
I appreciate any thoughts/ideas.
| Max VM Disk Latency | VM Disk Latency (95th percentile) | VMs |
| 68,832.89 | 10.27 ms | 6 |
| 65,418.18 | 17.57 ms | 20 |
| 58,868.16 | 129.02 ms | 25 |
| 24,742.77 | 5.73 ms | 26 |
| 24,719 | 8.47 Second(s) | 42 |
| 21,058.99 | 1.59 Second(s) | 24 |
| 3,297.15 | 329.07 ms | 14 |
| 1,419.53 | 826.2 μs | 24 |
| 916.58 | 133.33 μs | 20 |
| 674.07 | 4.57 ms | 45 |
| 197.6 | 321.57 μs | 26 |
| 86.33 | 130.02 μs | 28 |
| 82.91 | 16.02 μs | 7 |
| 69.39 | 70.28 μs | 19 |
| 68.69 | 913.98 μs | 12 |
| 55.07 | 14.48 ms | 19 |
| 53.67 | 20.56 ms | 18 |
| 51.07 | 1 ms | 18 |
↧
Re: vCenter 6.7 vPostGres SQL Crashing vCenter Appliance
Attached is the vpxd-profiler.log
↧
Re: VM Disk Latency in Seconds - Why the large delta.
The datastores listed are across four different datastore clusters across multiple arrays. The two datastores with VM Disk Latency in seconds, are the only ones on 6.5.0 and using a PureStorage all flash array. The others are 6.0.0 running on on flash arrays. Connectivity is via fiber channel. I attempted to look for correlations between the high latency and other metrics (read, write, io, etc...) and do not see one (for example backups).
↧
↧
Re: vCenter 6.7 vPostGres SQL Crashing vCenter Appliance
Attach vpxd.log as well.
↧
Re: vCenter 6.7 vPostGres SQL Crashing vCenter Appliance
vpxd log attached
↧
Passthrough of Adaptec ASR-51645 successful but StorageManager will not find the card in Windows VM.
Hi everyone;
I've been trying to find a solution to this issue with no avail. I have an ESXi 6.5U2 Server that is currently running a Windows 2012R2 file server. This file server used to be a Windows standalone box with the RAID controller in the subject line. I have moved this to a virtual server and was able to see the original disk volume. The problem is when I load Adaptec Storage Manager, it will not find the controller even though Windows says it's there and the driver is loaded, current and I have unfettered access to the old disk volume. Has anyone ran into this before? I checked the firmware on the card and it is also current.
↧
Re: vCenter 6.7 vPostGres SQL Crashing vCenter Appliance
I've sent you a DM.
↧
↧
Re: vRealize Operations Manager dashboard that shows ESXi event warning and error
In vRLI, create a query like this:
appname contains vcenter-server
text contains esxihost.example.com
vc_event_type contains vim.event.hostconnectionlostEvent
The event types correspond to the vcenter events you see in the vsphere client when you have the Event Type ID column shown.
↧
Re: How to shrink a thick-provisioned disk
Converter will always be one of the slowest options ....
Just had another idea ....
Why dont you add a new 200 GB vmdk to that VM and then use robocopy to copy the data to the new drive.
Then you just need a short period without activity to do a final sync and then switch driveletters so that the new disk gets the driveletter of the old - large vmdk.
↧
Re: How to shrink a thick-provisioned disk
I've thought about that idea, of using a new drive and RoboCopy. That would definitely speed up a basic file copy and still might look into that. If I remember right, RoboCopy can preserve security permissions on the copy.
So, I ran through your earlier directions on a test server that had a 100GB drive, and only 25GB being used. I do show that the drive is now "Thin", but it still registers the size as 100GB. How do I fully reclaim that space now that VMware sees it as thin-provisioned? Thanks!
↧
Re:Vra 7.5 Patch HF5 installation loop indefinetly on HF4 uninstallation step
I had this problem also. Look at the trouble shooting section of the KB https://kb.vmware.com/kb/60310.
Basically you need to uninstall the management agent agents from all the IAAS servers. Then extract the new agent from the update package using 7-zip. Then manually reinstall the new agent on all the IAAS servers,. SSH into the virtual appliance master node and replace the "isApplied" value to true:
- sed -i 's/false/true/g' /usr/lib/vcac/patches/repo/contents/vRA-patch/self-patch.json
Then rerun the HF5patch install. Its a PITA especially if you have like 12 IAAS servers.
↧
↧
Re: How to shrink a thick-provisioned disk
Hi BillClarkCNB,
Disable SSL for VMware Converter and you will surprised by the increase: Disabling SSL encryption on VMware Converter Standalone 5.x and 6.0 (2020517) | VMware KB
Obviously this makes it less secure and people could read the traffic over the wire but if needs must do this. In my experience this can bring the speed up from MB/sec to 10-100’s MB/sec. Other factors in here such as network and storage speeds but it certainly makes for a better experience. Test anyway and see.
Otherwise as mentioned RoboCopy maybe an option but with little files it can be painful. In this case use the ”MT” switch to increase threads. This really helps with small files as others are in flight while acknowledgements are being done. I find somewhere between 8 - 16 is the sweet point but you mileage may vary.
Kind regards.
↧
Re: How to shrink a thick-provisioned disk
Hi BillClarkCNB,
Check what is allocated vs provisioned. The provisioned size will be 100GB however the allocation should only be the data consumed.
Look from the datastore view or on the VM summary page and the storage allocated should be displayed.
Kind regards.
↧
Re: nsx not showing the cluster
in the url is up to date, i manage to update vcsa to 6.7 and all is working now
i'm going to post a new question, refering to host preparation
but this is solved update vcsa, thanks for your help
↧
Re: ESXi 6.5 U1 expired
↧
↧
host preparation - vmk not applicable
hi experts,
please can you help me, in the cluster it show as not applicable but in the host preparation section
i already deploy the 3 controllers in the cluster but the nic show something like this,
this al maked in the vmk interfaces for all the host in the cluster
do i need to change the mtu to 1600
to be ready for host preparation? or do i need something more?
connection is open for vcenter connectivity, no firewall in the setup
nsx is deploy in the nsx manager
↧
Re: How to shrink a thick-provisioned disk
It shows "Provisioned Space = 100GB", and "Used Space = 22.61GB". So I think I'm forgetting how thin-provisioning works, and that you do set a "max" size of the disk, but it doesn't pre-allocate it all. Even though it shows 100GB, it is only using 22GB on the SAN. Is that correct? Looking at the overall free space on the LUN, it does appear that it increased after this test. I'm going to test with another server just to verify....
↧
Re: How to shrink a thick-provisioned disk
> but it still registers the size as 100GB.
All vmkfstools -i commands do not change the "nominal size".
To change that you need to
1. resize the partition inside the guest
2. power off the guest
3. cut down the flat.vmdk with a dd-command
4. adjust the size in the vmdk descriptor
5. boot the VM with a Linux LiveCD that can rebuild the GPT-backup at the end of the disk
6. reboot the VM
For many users step 3 is too scary - so they rather do not use this approach.
↧