Reado
Contributor
Contributor

You may not power on a virtual machine in a virtual machine

Jump to solution

I keep getting this message when I try to power on a VM into ESXi, which is running inside VMware Workstation 6.5. I'm doing this to test everything before formatting my production server and installing ESXi. Does anyone know how I can get around this message?

Thanks in advance!

0 Kudos
1 Solution

Accepted Solutions
fejf
Expert
Expert

Edit your .vmx file and change/add the following settings (I tested them, they work and are taken from: http://vinf.net/2008/05/18/running-esx-35-and-3i-under-vmware-workstation-65-beta-build-91182/ )

ethernet0.virtualDev = “e1000″

monitor.virtual_exec = “hardware”

monitor_control.restrict_backdoor = “true”

--

There are 10 types of people. Those who understand binary and the rest. And those who understand gray-code.

-- There are 10 types of people. Those who understand binary and the rest. And those who understand gray-code.

View solution in original post

0 Kudos
54 Replies
fejf
Expert
Expert

Edit your .vmx file and change/add the following settings (I tested them, they work and are taken from: http://vinf.net/2008/05/18/running-esx-35-and-3i-under-vmware-workstation-65-beta-build-91182/ )

ethernet0.virtualDev = “e1000″

monitor.virtual_exec = “hardware”

monitor_control.restrict_backdoor = “true”

--

There are 10 types of people. Those who understand binary and the rest. And those who understand gray-code.

-- There are 10 types of people. Those who understand binary and the rest. And those who understand gray-code.

View solution in original post

0 Kudos
Reado
Contributor
Contributor

Spot on answer. Thanks mate. I appreciate it. Smiley Happy

0 Kudos
anichhatre1977
Contributor
Contributor

Hi,

I have added following lines to .vmx file. but still I am not able to start virtual machine from ESX 3.5 VM client. When I power ON the Virtual guest OS it gives error "you may not power on virtual machine in virtual machine"

ethernet0.virtualDev = "e1000″

monitor.virtual_exec = "hardware"

monitor_control.restrict_backdoor = "true"

Please help.....Thanks in Advance

Aniruddha

0 Kudos
admin
Immortal
Immortal

Did you add these configuration options to the .vmx file for the outer VM (i.e. the ESX VM)? If so, which VMware product are you using to run the outer VM?

0 Kudos
anichhatre1977
Contributor
Contributor

Hi Jmattson,

Thanks for your response, I m using following configuration:

AMD Phenom Quad core + 2GB RAM, I have installed VMware Workstation 6 and installed this ESX 3.5 Server under VMware workstation 6. I m trying to create virtual guest machine using VMware infra Client 2.5. After configuring Windows 2003 server as guest OS under ESX server I am not able to power on it gives error "You may not power on a virtual machine in a virtual machine". Also I have configured those given entries for .vmx file for VMware ESX3.5 server only. Do I need to do same for Newly configured Windows 2003 Server guest OS??

Best regards;

Aniruddha

0 Kudos
admin
Immortal
Immortal

To run nested VMs under ESX 3.5, you will need to upgrade to Workstation 6.5.

Nonetheless, the settings you've listed are correct, and with the backdoor restricted, you should not be getting the message about running a VM inside a VM. Check for typos in the line that reads:

monitor_control.restrict_backdoor = "true"

0 Kudos
anichhatre1977
Contributor
Contributor

Hi Jmattson

Thanks for suggession, After updating to VMware workstation 6.5.1 and adding monitor backdoor entry to .vmx file, I am able to power on VM guest OS under my Virtual Host ESXi 3.5 server.

Cheers,:D

Aniruddha

0 Kudos
Zee
Contributor
Contributor

Which VMX file i need to edit please let me know i am new to ESX. do i need to edit ESX server 3.5 VMX file or the Vm machine i created. please let me know if i need to edit ESx 3.5 VMX file then how and where i can find this file. i did change My XP vm (VMX file) but still i am getting error " you may not power on a virtula machine in a virtual machine:

Thanks

0 Kudos
admin
Immortal
Immortal

You need to change your ESX Server 3.5 configuration file. When you open the ESX VM in Workstation (before you power it on), the path to the configuration file is shown at the top of the window.

0 Kudos
Zee
Contributor
Contributor

Thanks for your quick reply. yes i did change my Esx3.5 VMX file and my ESX is running under my VM worstatin 6.5.1 fine here is the my VMs file contents. let me tell you what i am using.

Host OS is vista ultimate

Thinkpad T61"

VMware workstation 6.5.1

VM Infrastructure client 2.5

I installed VM client on vista and i can conect to Esx within vm workstation but when i power on my VM within VN client i got message "You may not power on a virtual machine in a virtual machine" your early response would be great. thanks

ESX3.5 Vmx file contents.

.encoding = "windows-1252"

config.version = "8"

virtualHW.version = "7"

vcpu.hotadd = "TRUE"

maxvcpus = "4"

scsi0.present = "TRUE"

scsi0.virtualDev = "lsilogic"

memsize = "2048"

scsi0:0.present = "TRUE"

scsi0:0.fileName = "Esx 3.5U2.vmdk"

ide1:0.present = "TRUE"

ide1:0.fileName = "D:"

ide1:0.deviceType = "cdrom-raw"

floppy0.startConnected = "FALSE"

floppy0.autodetect = "TRUE"

ethernet0.present = "TRUE"

ethernet0.virtualDev = "e1000"

ethernet0.wakeOnPcktRcv = "FALSE"

usb.present = "FALSE"

ehci.present = "TRUE"

sound.present = "FALSE"

sound.fileName = "-1"

sound.autodetect = "TRUE"

mks.enable3d = "FALSE"

pciBridge0.present = "TRUE"

pciBridge4.present = "TRUE"

pciBridge4.virtualDev = "pcieRootPort"

pciBridge4.functions = "8"

pciBridge5.present = "TRUE"

pciBridge5.virtualDev = "pcieRootPort"

pciBridge5.functions = "8"

pciBridge6.present = "TRUE"

pciBridge6.virtualDev = "pcieRootPort"

pciBridge6.functions = "8"

pciBridge7.present = "TRUE"

pciBridge7.virtualDev = "pcieRootPort"

pciBridge7.functions = "8"

vmci0.present = "TRUE"

roamingVM.exitBehavior = "go"

displayName = "Esx 3.5U2"

guestOS = "rhel4-64"

nvram = "Esx 3.5U2.nvram"

virtualHW.productCompatibility = "hosted"

ft.secondary0.enabled = "TRUE"

tools.upgrade.policy = "useGlobal"

extendedConfigFile = "Esx 3.5U2.vmxf"

floppy0.fileName = "A:"

floppy0.present = "FALSE"

ethernet0.linkStatePropagation.enable = "TRUE"

monitor.virtual_mmu = "software"

monitor.virtual_exec = "hardware"

monitor_control_restrict_backdoor = "true"

ethernet0.addressType = "generated"

uuid.location = "56 4d 6a cf d9 ba 58 16-35 7a c9 c7 6a 6f 4f 01"

uuid.bios = "56 4d 6a cf d9 ba 58 16-35 7a c9 c7 6a 6f 4f 01"

debugStub.linuxOffsets = "0x0,0xffffffff,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0"

scsi0:0.redo = ""

vmotion.checkpointFBSize = "16777216"

pciBridge0.pciSlotNumber = "17"

pciBridge4.pciSlotNumber = "21"

pciBridge5.pciSlotNumber = "22"

pciBridge6.pciSlotNumber = "23"

pciBridge7.pciSlotNumber = "24"

scsi0.pciSlotNumber = "16"

ethernet0.pciSlotNumber = "32"

ehci.pciSlotNumber = "33"

vmci0.pciSlotNumber = "34"

ethernet0.generatedAddress = "00:0c:29:6f:4f:01"

ethernet0.generatedAddressOffset = "0"

vmci0.id = "1785679617"

tools.remindInstall = "TRUE"

0 Kudos
admin
Immortal
Immortal

You have a typo in the following line:

monitor_control_restrict_backdoor = "true"

That should read:

monitor_control.restrict_backdoor = "true"

0 Kudos
Franco11
Contributor
Contributor

I am running ESX 3.5 as a VM on WS 6.5 . I added the suggested entries to my .vmx file:

ethernet0.virtualDev = “e1000″

monitor.virtual_exec = “hardware”

monitor_control.restrict_backdoor = “true”

I am still getting the same error when I try to power a VM in ESX: You may not power on a virtual machine in a virtual machine. I am using a DELL Latitude E4300 with intel duo core, using VT enable, and 4 GB of RAM. ESX starts fine and everything seems to be working except that I can not power any of the VMs I created or imported.

0 Kudos
VMmatty
Virtuoso
Virtuoso

Check the VMX for a typo (though it looks right in your post).

Also, if you edit the properties of the processor of the ESX VM, you can set the Preferred Mode. Try setting that to "Intel VT-x or AMD-V" instead of "Automatic."

Matt | http://www.thelowercasew.com | @mattliebowitz
0 Kudos
Franco11
Contributor
Contributor

I did...Here is my full vmx file:

.encoding = "windows-1252"

config.version = "8"

virtualHW.version = "7"

vcpu.hotadd = "TRUE"

maxvcpus = "4"

scsi0.present = "TRUE"

scsi0.virtualDev = "lsilogic"

memsize = "1268"

scsi0:0.present = "TRUE"

scsi0:0.fileName = "ESX35.vmdk"

ide1:0.present = "TRUE"

ide1:0.fileName = "auto detect"

ide1:0.deviceType = "cdrom-raw"

floppy0.present = "FALSE"

ethernet0.present = "TRUE"

ethernet0.virtualDev = "e1000"

ethernet0.wakeOnPcktRcv = "FALSE"

ethernet0.linkStatePropagation.enable = "TRUE"

mks.enable3d = "TRUE"

pciBridge0.present = "TRUE"

pciBridge4.present = "TRUE"

pciBridge4.virtualDev = "pcieRootPort"

pciBridge4.functions = "8"

pciBridge5.present = "TRUE"

pciBridge5.virtualDev = "pcieRootPort"

pciBridge5.functions = "8"

pciBridge6.present = "TRUE"

pciBridge6.virtualDev = "pcieRootPort"

pciBridge6.functions = "8"

pciBridge7.present = "TRUE"

pciBridge7.virtualDev = "pcieRootPort"

pciBridge7.functions = "8"

vmci0.present = "TRUE"

monitor.virtual_mmu = "software"

monitor.virtual_exec = "hardware"

monitor_control.restrict_backdoor = "true"

roamingVM.exitBehavior = "go"

displayName = "ESX35"

guestOS = "rhel4-64"

nvram = "ESX35.nvram"

virtualHW.productCompatibility = "hosted"

ft.secondary0.enabled = "TRUE"

tools.upgrade.policy = "useGlobal"

extendedConfigFile = "ESX35.vmxf"

ethernet0.addressType = "generated"

uuid.location = "56 4d 25 95 27 70 6c d9-bb b4 e8 b9 4d 31 08 18"

uuid.bios = "56 4d 25 95 27 70 6c d9-bb b4 e8 b9 4d 31 08 18"

scsi0:0.redo = ""

vmotion.checkpointFBSize = "134217728"

pciBridge0.pciSlotNumber = "17"

pciBridge4.pciSlotNumber = "21"

pciBridge5.pciSlotNumber = "22"

pciBridge6.pciSlotNumber = "23"

pciBridge7.pciSlotNumber = "24"

scsi0.pciSlotNumber = "16"

ethernet0.pciSlotNumber = "32"

vmci0.pciSlotNumber = "33"

ethernet0.generatedAddress = "00:0c:29:31:08:18"

ethernet0.generatedAddressOffset = "0"

vmci0.id = "1295058968"

tools.remindInstall = "TRUE"

ide1:0.autodetect = "TRUE"

0 Kudos
admin
Immortal
Immortal

Looks good. Did you change the configuration file while the VM was open in a tab under Workstation? The VM must be closed when editing the configuration file using third-party tools.

0 Kudos
Franco11
Contributor
Contributor

No, I shutdown the VM and WS and edited the file with Notepad.

0 Kudos
admin
Immortal
Immortal

Can you post your vmware.log file?

0 Kudos
Franco11
Contributor
Contributor

I found the problem..:) on the DELL Latitude E4300 intel duo core you need to disable the VT I/O option in BIOS and leave only the Virtualization enbled option. I used the NTOP imported VM and it runs very well and fast.

0 Kudos
stefan82
Enthusiast
Enthusiast

I've just finished setting up an ESX3.5 HA/DRS cluster environment within my VMware workstation 6.5. I've managed to install the Windows 2003 Enterprise Edition within the ESX3.5 environment. Just to let you know what I did and what problems i've had:

  • I've created a normal Workstation 6.5 type custom virtual machine with almost everything default.

  • Operating system type: Linux, specific: Other linux 2.6 kernel 64 bit. (The 64 bit part is mandatory, I kept getting the message: You may not power on a vm in a vm...)

  • Installed using the 3.5 update 3 iso file

  • After installation I've closed the VM in workstation, removed it from my favorites and opened the .vmx file in my editor.

  • I've added the parameters specified in this topic:

    • monitor.virtual_exec = "hardware"

    • monitor_control.restrict_backdoor = "true"

  • The ethernet0.virtualdev parameter was already there cause of the chosen operating system.

I hope this information helps you in any way.

0 Kudos