Hyper-V does not allow to be installed on a machine that's already virtual (such as on another Hyper-V or VMWare). For VMWare, you can circumvent this by adding custom configuration parameters to the VM's configuration.
Add these to the VM's configuration, either through the vSphere (web)client, or by directly editing the VMX-file:
hvh.enable = TRUE hypervisor.cpuid.v0 = FALSE
If you're editing the VMX-file, you need to enclose the values (behind the =) in double quotes (").
I wrote a script to list virtual disk information for a specified VM, including VMDK path, SCSI IDs and more. It is loosely based on this script but excludes all WMI info.
It is possible to install the integration plugins for VMware on an ESX host directly from the Nimble website, provided your hosts have internet access:
esxcli software vib install -d http://update.nimblestorage.com/esx5/ncm
With PowerCLI, you can generate all sorts of lists. To retrieve the configured and reported OS version of your VMs, try running this one-liner:
read moreGet-VM | Sort |
Get-View -Property @("Name", "Config.GuestFullName", "Guest.GuestFullName", "Guest.IpAddress") |
Select -Property Name,
@{N="Configured OS";E={$_.Config.GuestFullName}},
@{N="Running OS";E={$_.Guest.GuestFullName}},
@{N="IP Address";E={@($_.Guest.IpAddress)}} |
Export-CSV -Delimiter ";" -Path "vms.csv"Found this interesting read on VMFS Extents and some of the (negative) myths that have arisen over the years:
https://blogs.vmware.com/vsphere/2012/02/vmfs-extents-are-they-bad-or-simply-misunderstood.html
You can quickly get a list of VMs, the datastores they are using and the logical folder they are in through PowerCLI:
Get-VM | Select Name,@{N="Datastore";E={[string]::Join(',',(Get-Datastore -Id $_.DatastoreIdList | Select -ExpandProperty Name))}},@{N="Folder";E={$_.Folder.Name}}
Combine it with Export-CSV to export the results to a CSV file.
You can download installation files and ISOs of any of the latest versions of VMWare Tools for each released version of ESX:
→ https://packages.vmware.com/tools/esx/index.html
This is useful if you need support for a certain OS version but are not able to upgrade the ESX host in order to get it (e.g. Windows 10 support on ESX 5.5 "non-u3").
Note that, although officially unsupported, VMWare Tools is technically backwards compatible, meaning you can install a newer version on a guest running on an older ESX host.
Windows 10 is not out of the box supported on ESX 5.5, unless you're running 5.5u3. One of the issues is that earlier versions do not have a compatible video driver for Windows 10.
However, for older versions of ESX 5.5, you can manually download the VMWare Tools and install them:
→ https://packages.vmware.com/tools/esx/5.5u3/windows/index.html
If your vCenter server has a self-signed certificate, you will get a warning about this when connecting to it from vSphere PowerCLI. You can disable this warning through PowerCLI with the Set-PowerCLIConfiguration cmdlet.
Set-PowerCLIConfiguration -InvalidCertificateAction Ignore
After making the change, new connections to the vCenter server will no longer produce a warning about the certificate.
