- RSS Channel Showcase 4772123
- RSS Channel Showcase 2296842
- RSS Channel Showcase 2041547
- RSS Channel Showcase 9226173
Articles on this Page
- 06/22/17--17:43: _Re: NSX Edge Gatewa...
- 06/22/17--17:48: _Re: VMware ESXi 5.5...
- 06/22/17--17:57: _Re: Client Integrat...
- 06/22/17--18:03: _Re: NSX Monitoring
- 06/22/17--18:14: _Re: vSAN Adding Gla...
- 06/22/17--18:33: _Re: vSAN Adding Gla...
- 06/22/17--18:34: _Re: Unmount datasto...
- 06/22/17--18:47: _Re: Upgrade Vcenter...
- 06/22/17--19:26: _ESXi not showing lo...
- 06/22/17--19:32: _macOS Sierra VM res...
- 06/22/17--19:56: _Re: VCSA 6.0 ISO?
- 06/22/17--20:25: _Re: Linux Host: Ker...
- 06/22/17--20:37: _Re: Cisco UCS serve...
- 06/22/17--20:55: _Passing host name t...
- 06/23/17--10:29: _Re: Cannot upgrade ...
- 06/23/17--10:47: _Re: About Live Stor...
- 06/23/17--10:48: _Relationships betwe...
- 06/23/17--10:50: _Re: Win10 Workstati...
- 06/23/17--10:51: _Re: Can the ITSM pl...
- 06/23/17--10:51: _Re: The connection ...
- 06/22/17--17:43: Re: NSX Edge Gateway - HA
- 06/22/17--17:48: Re: VMware ESXi 5.5 U2 - TcpAckFrequency
- 06/22/17--17:57: Re: Client Integration Plug-In 6.0 installed but not working
- 06/22/17--18:03: Re: NSX Monitoring
- 06/22/17--18:14: Re: vSAN Adding Glance Images ( http error Gone 410 )
- 06/22/17--18:33: Re: vSAN Adding Glance Images ( http error Gone 410 )
- 06/22/17--18:34: Re: Unmount datastores from all hosts
- 06/22/17--18:47: Re: Upgrade Vcenter 5.5 to 6.5 with View composer as well
- 06/22/17--19:26: ESXi not showing local disks after patch
- 06/22/17--19:32: macOS Sierra VM resolution is blurry
- 06/22/17--19:56: Re: VCSA 6.0 ISO?
- 06/22/17--20:25: Re: Linux Host: Kernel 4.12 Breaks vmmon..
- 06/22/17--20:37: Re: Cisco UCS server local disks - Do not support UNMAP
- 06/22/17--20:55: Passing host name to triggered alarm
- 06/23/17--10:47: Re: About Live Storage Migration in VMware ESX5.1
- 06/23/17--10:50: Re: Win10 Workstation USB won't work
I had the above scenario.
The edge gateway was in Active - Standby. I have kept the OSPF timers as 30 & 120 as recommended by VMware. The HA Dead timer = 9 seconds recommended by VMWare.
When I shutdown the active Edge Gateway , there was interruption of nearly 150 seconds for the north south traffic.
The switch over of Edge gateway from Active - Standby was ok but there is long interruption of 150 seconds with the timers of 30/120 OSPF recommended by VMWare.
Is this normal ?
If it is normal what is the reason for this.
Request any ones input at the earliest.
I am still seeing a noticeable difference in performance on
host 6.0.0, 5224934
exchange 2016, windows 2012r2, windows 7 clients.
messing with the ack on clients does resolve it but not something we want to engage in.
I have the same issue after installing Firefox 44.0 Windows 7 or 10 and Client integration Plugin 6.0.0. After installing the fire fox 44.0 we are able to install the Client Integration Plugin on the server.
We had to deinstall Firefox and the Client Integration Plugin and delete the complete Firefox Profile (only the places.sqlite we import to the new installation).
After restart and complete new installation (ff 44.0 and CIP 6.0.0) it works.
Follow the below link to fix this issue.
I understand that Log Insight can be used for Monitoring but is there any way I can monitor NSX components by inbuild features of NSX or vCenter to generate alerts or error messges.
We managed to get the image imported by changing the glance-api.conf
The default setting is
We changed it to
Now the image imports but the image is stored in /var/lib/glance/images and not on the vSAN datastore.
I think we may have to modify the glance-api.conf file so that it stores in a directory on the vSAN datastore. There is a setting in the configuration file.
We shall give it a go and report back soon.
OK thanks - it's erroring out though:
Get-View : Cannot bind parameter 'Id'. Cannot convert the
"VMware.Vim.DatastoreHostMount" value of type "VMware.Vim.DatastoreHostMount" to
At C:\scripts\vmware_remove_datastores.ps1:22 char:25
+ $esx = Get-View -Id $_.ExtensionData.host
+ CategoryInfo : InvalidArgument: (:) [Get-View], ParameterBindingExce
+ FullyQualifiedErrorId : CannotConvertArgumentNoMessage,VMware.VimAutomation.V
Any ideas? I'm sure it is getting the datastore OK and passing it down the pipe but it looks like $_.Extensiondata.host isn't returning a result...
Thank you very much for the answer Warren!
We got some HP ProLiant Gen9 boxes running ESXi 6.0 Update 2.
Today I've applied ESXi-6.0.0-20170604001-standard patch and rebooted the server. There was no issues during the patching process at all.
But after ESXi got rebooted, the local disks are not going to be shown on vSphere client. Also an alert about non-persistent syslog are shown.
This is a totally odd situation, because apparently the RAID controller is detected during boot, but after ESXi is loaded, there are no local disks being shown, and we are unable to access it also via SSH, as it doesn't appears as a mounted device / vmfs volume.
After rolling back the update, we got local disks showing again.
I am thinking in reapply this update without installing the scsi-hpsa vib which I think that could be the problem as it was reported in an KB about causing controller detection issues, but it was on 6.0U1:
So, have someone any clue about this case?
Thank you in advance!
I’m running a macOS Sierra 10.12.5 VM on ESXi 6.5 but when I change the VM resolution to the same as the native resolution of my MacBook Pro 15” w/ Retina (2880×1800) the image is too large for the screen. A VM resolution of 1440×900 creates the correct size image but it’s not very sharp; it’s somewhat blurry. Any idea on how I can correct this? Thanks in advance!
hello,you can look at website below,hope can help you.
VMware 12.5.7 is out, and I can confirm that this now works OK with Kernel 4.12 (tested with 4.12-rc6)
Thanks for your help~ Sureshkumar M,
Actually, I have a Windows 7 VM, which is the thin-provisioned VM and the used space is 75.6GB.
Current VM spaces (Used 75.6GB):
Current datastore used space on the VM (Have the Virtual Disk of the VM used 85,829,632.00 KB ~around 85 GB):
Can reclaim the space of 10 GB back???... Now, I deleted more 5GB. When can it reclaim back? Local Disk cannot reclaim??
Have configured alarm action to run a command, Is there a way for me to pass the Esxi host name for which the alarm has been triggered ?
BACKUP THE DATABASE, then connect to the database and execute the SQL command:
alter table VPX_EXT_PRIVS drop constraint PK_VPX_EXT_PRIVS
...then try the upgrade again.
How Storage vMotion Works
1. First, vSphere copies over the nonvolatile files that make up a VM: the configuration file (VMX), VMkernel swap, log files, and snapshots.
2. Next, vSphere starts a ghost or shadow VM on the destination datastore. Because thisghost VM does not yet have a virtual disk (that hasn’t been copied over yet), it sits idle waiting for its virtual disk.
3. Storage vMotion fi rst creates the destination disk. Then a mirror device—a new driver that mirrors I/Os between the source and destination—is inserted into the data path between the VM and the underlying storage. SVM Mirror Device Information in the Logs If you review the vmkernel log fi les on an ESXi host during and after a Storage vMotion operation, you will see log entries prefi xed with SVM that show the creation of the mirror device and that provide information about the operation of the mirror device.
4. With the I/O mirroring driver in place, vSphere makes a single-pass copy of the virtual disk(s) from the source to the destination. As changes are made to the source, the I/O mirror driver ensures that those changes are also reflected at the destination.
5. When the virtual disk copy is complete, vSphere quickly suspends and resumes in order to transfer control over to the ghost VM created on the destination datastore earlier. This generally happens so quickly that there is no disruption of service, as with vMotion.
6. The files on the source datastore are deleted.
Book Titled "Mastering VMware vSphere 5.5" by Nick Marshall and Scott Lowe
Note: More on I/O mirroring driver
– This is the legacy Data Mover, the most basic version. It is the slowest because the data moves all the
way up the stack and then down again.
(software) – This is the software Data Mover, which was introduced with vSphere 4.0 and contained
some substantial optimizations whereby data does not travel through all stacks.
(hardware) – This is the hardware offload Data Mover, introduced with vSphere 4.1. It still is the fs3dm,
but VAAI hardware offload is leveraged with this version. fs3dm is used in software mode when hardware
offload (VAAI) capabilities are not available.
When the source filesystem uses a different blocksize from the destination filesystem, the legacy datamover (FSDM) is used. When the blocksizes of source and destination are equal, the new datamover (FS3DM) is used. FS3DM uses VAAI or just the software component. In either case, null blocks are not reclaimed.
If you found this or any other answer helpful, please consider the use of the Helpful to award points.
Is there a way to show these relationships in vRA? Ideally, we'd want all the networks and associated items that come along with the deployment to fall under a parent/child relationship.
This is probably caused by USB devices with remote device wakeup capability.
You can try if the following steps work around the issue
1. Go to device manager on the host
2. Right click on the failing device
3. Click on the 'Power Management' tab
4. Uncheck 'Allow the computer to turn off this device to save power
Any updates on extra fields being passed into CMDB such as IP address, Storage info, Datastores, Cluster?
The cause may be the same as the following one