Virtualization Nesting is already complicated, now I hope my subject for this discussion is not too confusing.

Server: Dell PowerEdge R730 Dual E2640

• Outer Hypervisor: ESXi 5.5.0u2  (Dell customized image, pre-installed on server), 4 NICs (NIC0, NIC1 in use)
  • Management IP address 10.200.200.9/  subnet mask: 255.255.255.0 / gateway: 10.200.200.1

• Inner Hypervisor: Windows Server 2012 R2 Datacenter, using 2x E1000E virtual network adapters
  • IP address 10.200.200.10 (for OS)
  • IP address 10.200.200.11 (for Guest VMs)

Basically I followed the instruction to create a new VM with Virtual hardware version 10, modify the vmx file, allocate and reserve 64GB RAM with 8 vCPU for the Windows Server,

vhv.enable = “TRUE”

hypervisor.cpuid.v0 = “FALSE”

mce.enable = “TRUE”

At this stage everything works fine -- I am able to install the Windows server 2012 R2, with Hyper-V feature. I also installed VMware Tools on this Windows 2012 datacenter Hyper-V, joined domain, ran iSCSI to connect to our NAS and restarted the hyper-V without issues on ESXi.

But when I try to install a new guest VM within Hyper-V, the network is not working correctly.

I install a Windows 2012 Standard on Hyper-V (the inner hypervisor) without issue, and the guest OS gets an IP address of 10.200.200.86 (assigned by DHCP in the same subnet)

From this guest OS, I am able to ping it's 1st-layer Hyper-V host (10.200.200.10 and 10.200.200.11) and 2nd ESXi host (10.200.200.9), but unable to contact further to gateway (10.200.200.1).

And of course, I got an exclamation sign on the network icon of taskbar of this Windows 2012 Standard saying "no internet connection".

*I was still able to join this Guest Windows 2012 Std to domain.

**Existing on the same subnet is another Hyper-V on physical server hosting multiple guest VMs including Domain controller and DHCP servers, etc.

I did try using PCIe pass-through with Dell server's NIC3 , but it crashed the ESXi, and gave me an IERR error message (errors of CPU 1) on my Dell server front display.

I ended up not using PCIe pass-through (although I really want to use if this solve my issue), because I learned that it may cause problems with Intel CPUs from other discussion threads.

Has anyone also had similar issues? what did you do to resolve this? I have been stuck for days not being able to connect guest VM to internet ....

My goals for this setup are to

(1) simplify my VM backup strategy (only backup the 2012 Hyper-V to capture all VM settings)

(2) keep actual guest VMs on the NAS.

(3) use this new nested Hyper-V with another Hyper-V (on another older physical server, not nested) to provide high availability

Andrew

I'm trying to install Windows 2008 server 64 bit operating system on VMWARE workstation 9 which is installed on WINDOWS 7 HOME PREMIUM 64 BIT . and i'm getting this error

"

"

can anybody help me on this problem ?

Hi:

    VMware WS 11.1.3 Host Windows 10. 

     Windows 2016 Server 2016 runs great in a VM (even on a nested ESi 6 server VM).  However when I tried to install the Hyper-V role and rebooted the machine did not go past the the Windows logo  (not even the circular progress circle.  I had defined this machine as a Windows 2012 Server. Enabled the processor virtualization option of course.  I tried a few things but none worked.  Changed OS type to hyper-v (unsupported) - no luck.  Changed OS type to Windows 10- x64 and added to vmx file.

hypervisor.cpuid.v0 = “FALSE"

mce.enable = “TRUE”

Actually I got a "dictionary" error or vmx corrupted msg in that case.

Fortunately I can just download the working 2016 VM from my physical ESXi and try again if I had a clue as to what I could do.

Has anybody gotten nested Hyper-V to work under a Windows Server 2016 VM?

I am running VMware Player 12 on the host. If I install VMware player 7 on the guest it conflicts with VMware tools on the guest and show "vmci.sys incorrect version" error. I can't install VMware 12 on the guest because it is 32 bit operation system. What should I do? Is the only option to not use VMware tools on guest?

Hi All,

I have installed an ESXi5.5 VM on top of WOrkstation10 and made a clone of it. Both of them are accessible and working fine on their own.

However, when I try to a add these hosts to vCenter, it starts complaining that :

"Datastore 'datastore1' conflicts with an existing datastore in the datacenter that has the same url"

and doesn't let me add the second host. Is there a way to resolve this issue?

Any help would be much appreciated..

Guys,

I am trying to install ESXi 6.0 on Virtual Box

I have chosen OS to be RHEL 64 bit

CPU - 4

Memory - 3 GB

HDD - 30 GB

I am getting an error which essentially stalls installation.

Anyone seen this before or knows a workaround?

Hi All,

I am using nested virtualization where I have installed ESXi 5.5 inside KVM. However,I am unable to spawn a VM with 64-bit VM (ubuntu 12.04) on my ESXi host and getting the following error:

"This Virtual Machine is configured for 64-bit operating systems. However, 64-bit operation is not possible. This host does not support Intel VT-x."

• I have the following configs set in .vmx file of the VM:
  • vhv.enable = "TRUE" and
  • vmx.allowNested = "TRUE
• I also have vhv.allow = "TRUE" set in /etc/vmware/config. (Though, its mentioned in some of your threads [https://communities.vmware.com/message/2220460#2220460]  that this option is not needed in ESXi 5.1 and above.
• Regarding my machine settings:
  • Supports 64-bit Longmode : Yes
  • Supports 64-bit VMware : Yes
  • Supported EVC Modes : None

and;

$> cat /sys/module/kvm_intel/parameters/nested

Y

$ cat /sys/module/kvm_intel/parameters/ept

Y

The vmware log is as follows:

(Complete vmware.log attached)

2014-01-16T08:41:29.345Z| vmx| I120: Tools: sending 'OS_PowerOn' (state = 3) state change request

2014-01-16T08:41:29.345Z| vmx| I120: Tools: Delaying state change request to state 3.

2014-01-16T08:41:29.345Z| vmx| I120: TOOLS INSTALL initializing state to IDLE on power on.

2014-01-16T08:41:29.357Z| vmx| I120: FeatureCompat: VM masks:

2014-01-16T08:41:29.357Z| vmx| I120: MonPmc: ctrBase 0xc1 selBase 0x186/1 PGC 0/0 SMM 0 drain 0 flush 0

2014-01-16T08:41:29.357Z| vmx| I120+ MonPmc:   gen counters num: 2 width 0 write width 0

2014-01-16T08:41:29.357Z| vmx| I120+ MonPmc:   fix counters num: 0 width 0

2014-01-16T08:41:29.357Z| vmx| I120+ MonPmc:   unavailable counters: 0

2014-01-16T08:41:29.359Z| vmx| I120: guestCpuFeatures = 0xf8

2014-01-16T08:41:29.364Z| vmx| I120: Guest CPUID differences from hostCPUID.

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 00000001, 0: 0x00000663 0x00010800 0x80800001 0x078bfbfd

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 00000006, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 00000007, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 00000008, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 00000009, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000a, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000b, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000c, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 2: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 3: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 4: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 5: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 6: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 7: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 8: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 9: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, a: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, b: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, c: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, d: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, e: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, f: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 10: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 11: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 12: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 13: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 14: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 15: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 16: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 17: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 18: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 19: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 1a: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 1b: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 1c: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 1d: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 1e: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 1f: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 20: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 21: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 22: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 23: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 24: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 25: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 26: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 27: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 28: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 29: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 2a: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 2b: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 2c: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 2d: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 2e: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 2f: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 30: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 31: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 32: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 33: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 34: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 35: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 36: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 37: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 38: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 39: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 3a: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 3b: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 3c: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 3d: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 0000000d, 3e: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 40000000, 0: 0x40000010 0x61774d56 0x4d566572 0x65726177

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 40000001, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 40000002, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 40000003, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 40000004, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 40000005, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 40000006, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 40000007, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 40000008, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 40000009, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 4000000a, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 4000000b, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 4000000c, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 4000000d, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 4000000e, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 4000000f, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 40000010, 0: 0x00260a9e 0x000101d0 0x00000000 0x00000000

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 80000001, 0: 0x00000663 0x00000000 0x00000000 0x0191abfd

2014-01-16T08:41:29.364Z| vmx| I120: guestCPUID level 80000007, 0: 0x00000000 0x00000000 0x00000000 0x00000100

2014-01-16T08:41:29.364Z| vmx| I120: Msg_Post: Error

2014-01-16T08:41:29.364Z| vmx| I120: [msg.cpuid.noLongmode2] This virtual machine is configured for 64-bit guest operating systems. However, 64-bit operation is not possible.

2014-01-16T08:41:29.364Z| vmx| I120+ This host does not support Intel VT-x.

2014-01-16T08:41:29.364Z| vmx| I120+ For more detailed information, see http://vmware.com/info?id=152.

2014-01-16T08:41:29.364Z| vmx| I120: ----------------------------------------

2014-01-16T08:41:29.370Z| vmx| I120: Module CPUID power on failed.

2014-01-16T08:41:29.370Z| vmx| I120: VMX_PowerOn: ModuleTable_PowerOn = 0

2014-01-16T08:41:29.376Z| vmx| I120: SVMotion_PowerOff: Not running Storage vMotion. Nothing to do

2014-01-16T08:41:29.376Z| svga| I120: SVGA thread is exiting

2014-01-16T08:41:29.376Z| vmx| I120: Destroying virtual dev for scsi0:0 vscsi=8196

2014-01-16T08:41:29.376Z| vmx| I120: VMMon_VSCSIStopVports: No such target on adapter

2014-01-16T08:41:29.377Z| mks| I120: MKS PowerOff

2014-01-16T08:41:29.377Z| mks| I120: MKS thread is exiting

2014-01-16T08:41:29.377Z| vmx| I120: scsi0:0: numIOs = 0 numMergedIOs = 0 numSplitIOs = 0 ( 0.0%)

2014-01-16T08:41:29.377Z| vmx| I120: Closing disk scsi0:0

2014-01-16T08:41:29.378Z| vmx| I120: DISKLIB-VMFS  : "/vmfs/volumes/52d413a8-96276407-888d-5254002a4c29/vm1/vm1-flat.vmdk" : closed.

2014-01-16T08:41:29.378Z| vmx| I120: SVMotion_PowerOff: Not running Storage vMotion. Nothing to do

2014-01-16T08:41:29.381Z| vmx| I120: WORKER: asyncOps=2 maxActiveOps=1 maxPending=1 maxCompleted=1

2014-01-16T08:41:29.381Z| vmx| I120: Vix: [39054 mainDispatch.c:1201]: VMAutomationPowerOff: Powering off.

2014-01-16T08:41:29.382Z| vmx| W110: /vmfs/volumes/52d413a8-96276407-888d-5254002a4c29/vm1/vm1.vmx: Cannot remove symlink /var/run/vmware/root_0/1389861689012676_39054/configFile: No such file or directory

2014-01-16T08:41:29.405Z| vmx| I120: Vix: [39054 mainDispatch.c:3964]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1 additionalError=0

2014-01-16T08:41:29.405Z| vmx| I120: Vix: [39054 mainDispatch.c:3964]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1 additionalError=0

2014-01-16T08:41:29.405Z| vmx| I120: Transitioned vmx/execState/val to poweredOff

2014-01-16T08:41:29.405Z| vmx| I120: Vix: [39054 mainDispatch.c:3964]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=0 additionalError=0

2014-01-16T08:41:29.405Z| vmx| I120: Vix: [39054 mainDispatch.c:4003]: Error VIX_E_FAIL in VMAutomation_ReportPowerOpFinished(): Unknown error

2014-01-16T08:41:29.405Z| vmx| I120: Vix: [39054 mainDispatch.c:3964]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1 additionalError=0

2014-01-16T08:41:29.405Z| vmx| I120: Transitioned vmx/execState/val to poweredOff

2014-01-16T08:41:29.405Z| vmx| I120: VMIOP: Exit

2014-01-16T08:41:29.433Z| vmx| I120: Vix: [39054 mainDispatch.c:849]: VMAutomation_LateShutdown()

2014-01-16T08:41:29.433Z| vmx| I120: Vix: [39054 mainDispatch.c:799]: VMAutomationCloseListenerSocket. Closing listener socket.

2014-01-16T08:41:29.437Z| vmx| I120: Flushing VMX VMDB connections

2014-01-16T08:41:29.437Z| vmx| I120: VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#1/'

2014-01-16T08:41:29.437Z| vmx| I120: VmdbCnxDisconnect: Disconnect: closed pipe for pub cnx '/db/connection/#1/' (0)

2014-01-16T08:41:29.446Z| vmx| I120: VMX exit (0).

2014-01-16T08:41:29.446Z| vmx| I120: AIOMGR-S : stat o=1 r=3 w=0 i=0 br=49152 bw=0

2014-01-16T08:41:29.446Z| vmx| I120: OBJLIB-LIB: ObjLib cleanup done.

2014-01-16T08:41:29.447Z| vmx| W110: VMX has left the building: 0.

Any help would be much appreciated..

hello:

i have installed VMware Workstation 10, configured for nesting virtualisation, i have installed Windows 2012 r2 as vm then i add hyper-v role, all work fine

but now when i try installing a new vm on hyper-v i acnnot assign to the new vm no more than 32 MB, on the host computer where i have installed VMware Workstation 10 i have 32 GB

thank you

Hi All,

I have ESXi 5.5 running and on top of ESXi VM with windows 7 (2 vCPU / 16 GB RAM / 160 GB HDD) . The VM is enabled with Nested (Hardware Virtualization - Expose hardware assisted virtualization to the guest OS) on CPU.

My Question is by enabling Nested VM do i have performance issues on the ESXi , If yes is there a way to resolve it?

Thanks in Advance.

Hello

i have 1 hard disk (size 1 TB).

i installed Esxi 5.5 on this hard disk.

i want to add another hard disk (Same size).

my questions :

1.is the Esxi OS will recognize the disk automatically ?

2.Will i see the disk as "datastore 2" ?

Hello,

I Installed a virtule Esxi  On a Physica Esxi (v5.5)

The Vm On The Virtual Esxi They Have not ping to My server or other devices on the network

The have a dhcp from server.

What Do I Need To Configure ?

I have installed ESXi 6.0 on VirtualBox and I have enabled Hardware Virtualization from VirtualBox as well. However when I create VM in ESXi and start it , It giing me an error

"You are running VMware ESX through an incompatible hypervisor. You cannot power on a virtual machine until this hypervisor is disabled."

I have tried everything . I am not getting  this entry mx.allowNested = TRUE for my VM .vmx file

Hi,

I am getting error when try to clone a server as below

LocalizedMethodFault Object

(

  [fault] =>

  [localizedMessage] => The operation is not supported on the object.

)

I am following https://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.VirtualMachine.html#clone

I have ESXi 5.0 .

Hi jmattson !!!!.

I have a question.

I have a nested Windows 2012 R2 Hyper-V as virtual machine on VMware Workstation 10.0.0 buil-1295980.

I created a NIC Team (2 NICs) in my Hyper-V. It works fine.

I need to create virtual NICs bound to that NIC Teaming becasue I am preparing an environment about network converged, but in Hyper-V.

However, when I create a Virtual Switch External bounded to the NIC Team from Hyper-V Manager, my Hyper-V loses network connectivity.

As soon as the NIC Team is unbinded from the virtual switch or if the virtual switch is deleted, the Hyper-V connects. Therefore, the NIC Team works fine.

Does VMware Workstation allow NIC Teaming inbound with a virtual switch in Hyper-V?. Or any workaround?

If your answer is negative. I can upgrade to VMware Workstation 12 Pro. Does VMware Workstation 12 Pro support my question?

Plese, help me :).

Thank you for your response !!.

Klem.

Greetings, I'm running Hyper-V (2012 not R2) nested on vSphere 6.0

Everything works except the Hyper-V integration services. The virtual machines on Hyper-V for some reason thinks they are a physical system and they don´t let start/install/upgrade the integration services. Some screenshots documenting the issue:

I've tried everything I know or been able to find:

• Use different options in the vmx file: hypervisor.cpuid.v0, vhv.enable, winHyperV guest OS, etc.
• Use different options in the hyper-V host (virtual machine).
• Running different hardware versions on the Hyper-V vm (9,10,11).
• Tried with and without vmware tools on the Hyper-V hosts.
• Tried different OS within Hyper-V (server 2008 R2 and 2012).
• Several patches and upgrades on the host/guest side.

I've seen this issue documented in this post: http://vblog.is/?p=94 and the solution seems to downgrade the ESXi 6.0 host to 5.5 and that is not an option for me (and I really need the integration services running for testing purposes).

Any help will be appreciated, thanks,

The time has come for me to move on to the next chapter of my life, but I leave the Nested Virtualization forum in the capable hands of covelli.  Thanks to all of you who have supported nested virtualization in VMware's products over the years, and best of luck to those of you who are using nested virtualization under other hypervisors.

Hi all,

I'm working on a virtual networking lab leveraging ESXi nested virtualization technology. Host is a Cisco UCS server based on dual socket Intel Xeon E5-2690 equipped with 128 GB RAM and running ESXi 6.0. Basically ESXi 6.0 supports a VM (16 vCPU, 64GB RAM assigned) running unetlab software. Internally unetlab, based on linux 64-bit kernel, supports multiple VMs (each of them implementing a network node - basically a "router") leveraging QEMU/KVM technology.

To enable Virtualized Hardware-Assisted Virtualization (VHV) for the VM running on ESXi I set vhv.enable = "true" in the .vmx configuration file.

nested VM instances running router OS have problems when multiple-vcpu are assigned to them (basically OS crash and try to reboot). No issues seen however when configured to run with just 1 vcpu assigned.

Note that when unetlab runs on bare metal server no issue is seen even with multiple vcpus assigned to router VMs running on top QEMU/KVM.

Any idea to troubleshoot the issue above ?

thanks for your help !

We are seeing a number of crashes, either "#PF Exception 14"   or "Recursive Panics w/ VSCSI timeouts"  on the ESXi 6.0 hosts running in VMs in on 5.5 VMs (VM Version 9).

In 5 out of 5 cases I looked at, there was a VM migration slightly before the crash.    I'm guessing that the 6.0 host has short I/O timeouts for swapping, etc., and those are not met on migration.

Is there any way to reduce the frequency of these events?

Thanks

PS I've also observed these messages just before some of the crashes, and I couldn't find any references to this message anywhere.

2016-03-23T04:01:02.023Z cpu0:323721)WARNING: HeapMgr: 1189: Unable to map MPN ranges for heap growth.

Hello All,

I am not an expert in Vmware, kindly bear with me.

The customer is trying to deploy OVA of our application which is packaged into Ubuntu 14.04. Our application requires VT-X and EPT technologies also required nested virtualization.

The OVA is deployed in UCS-C240_M35, ESXI 6.0 and a cluster in which has EVC enabled and runs on EVC mode Penryn. when we power on the VM we get the following error.

The Host details

We also get the following error while trying to migrate.

The Host CPU Intel Xeon E5-2680 supports VT-x and EPT, so there is no reason for that error to pop in. Will EVC limit the VTX capabilities running in EVC mode Penyrn?

Thanks in Advance,

Romal

Hi,

In the beginning I must say that I don't consider myself a VMware's product expert.

I've been struggling with my test nested environment for quite a while and finally decided to (hopefully) get some help from pros.

Environment looks like this:

• Physical VMware ESXi 5.1.0 (promiscuous mode turned on for the vSwitch)
  • Couple of virtual machines, one of them being Hyper-V server (Windows Server 2012 R2) which is configured for nested virtualization - 10.106.5.27
    • On Hyper-V server I have one VM being Windows Server 2012 R2 - 10.106.5.28

Hyper-V server has one NIC and full network connectivity (internal and external: Internet) and in Hyper-V Manager a Virtual Switch is configured in external mode.

VM is connected to this virtual switch via Virtual Network Adapter. It has static IP assigned with subnet mask, default gateway and DNSs same as Hyper-V host. I can ping the host from VM and vice versa both by IP and DNS name. I can't ping other resources from the VM including default gateway and DNS servers ("request timed out"). On VM network status in Network and Sharing Center is:

• unidentified network
• Public network
• access type: no internet access

When I run Troubleshoot Problems tool on VM it says "The default gateway is not available". As I mentioned I can't ping it.

I think that all my connectivity problems are caused by unavailability of default gateway on the VM, but I have no idea of how to solve this issue. When changing the VM's adapter settings from static to DHCP I can't even ping the Hyper-V host.

All of the servers are joined to same domain (VM was migrated from ESXi so it was joined to domain before, but I can't login using domain accounts, probably because of the network problem).

I hope that I described the problem enough but please let me know if you need more information.