ESXi3.5 Update 2 Build 110271 (Aug 13) on Workstation 6.5 BETA (build 99530) - problem with powering on VMs "Error You may not power on a virtual machine in a virtual machine"

[pbraren]

As many have already discussed, this xtravirt site:

has a really good walkthru of "VI3.5 in a box", where it is shown how to install ESX 3.5 Update 2 Build 103909 (late July with license bug). Possibly a nice way to close-out this nearly 1 year old thread I had started after VMworld 2007:

entitled "some early experiences with 3i (on Kingston USB key from VMWORLD)"

I went ahead and tried the "VI3.5 in a box" procedure today, on ESXi3.5 Update 2 Build 110271 (Aug 13) on Workstation 6.5 BETA (build 99530), and had a problem with powering on VMs. An error dialogue comes up, stating "Error You may not power on a virtual machine in a virtual machine", see jpg attached.

I will go thru the same steps with ESX3.5 Update 2 Build 110217 (Aug 13) on Workstation 6.5 BETA (build 99530), and see if the same issue comes up when trying to power on VMs. I don't currently have access to downloading ESX 3.5 Update 2 Build 110217 to find out though.

Meanwhile, I did record a video with narration, of the entire ESXi installation/configuration process (inside VMware Workstation), it's 48 minutes, but easily fast-forwardable, view it here:

It would appear that the difference between these exact versions of ESXi 3.5 and ESX 3.5 could be enough to break the ability boot VMs within a VM, or the move from build 103909 to 110217 broke something, or I made a mistake, just not sure yet...

[pbraren]

Unfortunately, same error as ESXi (see original post): ESX3.5 Update 2 Build 110217 (Aug 13) on Workstation 6.5 BETA (build 99530) also gives me the "Error You may not power on a virtual machine in a virtual machine"

See attachment for screenshot. Built the ESX host EXACTLY according to xtravirt instructions, and still no joy.

Now I need to step back and try the late August build 103909 instead and see if it works...

[pbraren]

Unfortunately, same error as ESXi (see original post): ESX3.5 Update 2 Build 110217 (Aug 13) on Workstation 6.5.0 Release Candidate (build 110068) also gives me the "Error You may not power on a virtual machine in a virtual machine"

[Virtually]

Howdy,

I just started another thread about this same problem.

Apparently, the extravirt cookbook describes only a single line to manually add to the VMX file

monitor_control.restrict_backdoor = "TRUE"

If you didn't overlook adding this command, you should have seen an error message booting ESXi saying the boolean value for this configuration doesn't exist, so as the bootup resumes the value would be set to "FALSE"

This is a real problem because according to some other posts I've reviewed, it's just this confg line that permists runnig a VM within a VM.

I've also tried adding the other usual lines with no effect or determined to be invalid in a 6.5 compatible VM

monitor.virtual_mmu = "software"

monitor.virtual_exec = "hardware"

Hopefully someone who actually knows how these configs work and particularly any prerequisites for monitor_control.restrict_backdoor = "TRUE" will post.

[oreeh]

The following VMX works fine for me (including powering on a VM inside the ESXi VM)

config.version = "8"
virtualHW.version = "7"
scsi0.present = "TRUE"
scsi0.virtualDev = "lsilogic"
memsize = "1024"
scsi0:0.present = "TRUE"
scsi0:0.fileName = "ESXi.vmdk"
ide1:0.present = "TRUE"
ide1:0.autodetect = "FALSE"
ide1:0.deviceType = "cdrom-raw"
floppy0.present = "FALSE"
floppy0.startConnected = "FALSE"
floppy0.autodetect = "TRUE"
floppy0.fileName = "A:"
ethernet0.present = "TRUE"
ethernet0.connectionType = "hostonly"
ethernet0.virtualDev = "e1000"
ethernet0.wakeOnPcktRcv = "FALSE"
ethernet1.present = "TRUE"
ethernet1.virtualdev = "e1000"
sound.present = "FALSE"
vmci0.present = "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"
displayName = "ESXi"
guestOS = "other-64"
nvram = "ESXi.nvram"
virtualHW.productCompatibility = "hosted"
ft.secondary0.enabled = "TRUE"
tools.upgrade.policy = "manual"
extendedConfigFile = "ESXi.vmxf"
monitor.virtual_exec = "hardware"
monitor_control.restrict_backdoor = "true"
isolation.tools.hgfs.disable = "TRUE"
isolation.tools.dnd.disable = "TRUE"
isolation.tools.copy.disable = "TRUE"
isolation.tools.paste.disable = "TRUE"
unity.showBorders = "FALSE"
unity.showBadges = "FALSE"
unity.enableLaunchMenu = "FALSE"
ide1:0.fileName = "E:"
ide1:0.startConnected = "FALSE"
ethernet0.addressType = "generated"
ethernet1.addressType = "generated"
tools.syncTime = "FALSE"
scsi0:0.redo = ""
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
scsi0.pciSlotNumber = "16"
ethernet0.pciSlotNumber = "32"
ethernet1.pciSlotNumber = "33"
ethernet0.generatedAddress = "00:0c:29:4e:b9:99"
ethernet0.generatedAddressOffset = "0"
ethernet1.generatedAddress = "00:0c:29:4e:b9:a3"
ethernet1.generatedAddressOffset = "10"
ethernet1.connectionType = "nat"

[Virtually]

I think I saw you post this same VMX in another thread but for some reason didn't work then...

I just tried again and this time it works... At the moment I'm booting up a SuSE GuestOS in ESXi in WS 6.5.

Will have to take a closer look to see what the diff is between your VMX file and the file generated by the Extravirt instructions. Skimming the VM settings, the most obvious diff is that the CPU value is "Custom" rather than the value pointing to CPU virtualization extensions without EPT/nested pages memory.

tet me see if I can repost the VMX file with the proper formatting to save people work...Note that I've removed the PCIbridge declarations because they caused errors although I left the lines configuring the PCIbridge objects. You can comment them out using a # instead but this forum software interprets that sign as enumeration instead of commenting out so I've had to post this way.

I also only have physical NIC in my setup so I removed your NIC attached to the HostOnly network (NAT should do just fine).

To make this config work,

1. Replaced existing VMX with this working VMX

2. Created a new hard disk. I created a 2gb disk using the lsilogic SCSI interface for the ESXi install and a second disk of 48gb to store GuestVMs. Note that the existing VMX file points to ESXi.vmdk so when you did step 1 without an existing disk of that name you may already have encountered an error pointing to a non-existent disk.

3. Verify RAM setting, 1024mb should be the minimum. Don't touch the CPU setting.

4. Point the CDROM to your media (likely your ISO file)

5. Power up and install.

config.version = "8"

virtualHW.version = "7"

scsi0.present = "TRUE"

scsi0.virtualDev = "lsilogic"

memsize = "1024"

scsi0:0.present = "TRUE"

scsi0:0.fileName = "ESXi.vmdk"

ide1:0.present = "TRUE"

ide1:0.autodetect = "FALSE"

ide1:0.deviceType = "cdrom-raw"

floppy0.present = "FALSE"

floppy0.startConnected = "FALSE"

floppy0.autodetect = "TRUE"

floppy0.fileName = "A:"

ethernet0.present = "TRUE"

ethernet0.connectionType = "hostonly"

ethernet0.virtualDev = "e1000"

ethernet0.wakeOnPcktRcv = "FALSE"

ethernet1.present = "TRUE"

ethernet1.virtualdev = "e1000"

sound.present = "FALSE"

vmci0.present = "FALSE"

displayName = "ESXi"

guestOS = "other-64"

nvram ="ESXi.nvram"

virtualHW.productCompatibility = "hosted"

ft.secondary0.enabled = "TRUE"

tools.upgrade.policy = "manual"

extendedConfigFile = "ESXi.vmxf"

monitor.virtual_exec = "hardware"

monitor_control.restrict_backdoor = "true"

isolation.tools.hgfs.disable = "TRUE"

isolation.tools.dnd.disable = "TRUE"

isolation.tools.copy.disable = "TRUE"

isolation.tools.paste.disable = "TRUE"

unity.showBorders = "FALSE"

unity.showBadges = "FALSE"

unity.enableLaunchMenu = "FALSE"

ide1:0.fileName = "E:"

ide1:0.startConnected = "FALSE"

ethernet0.addressType = "generated"

ethernet1.addressType = "generated"

tools.syncTime = "FALSE"

scsi0:0.redo = ""

pciBridge0.pciSlotNumber = "17"

pciBridge4.pciSlotNumber = "21"

pciBridge5.pciSlotNumber = "22"

pciBridge6.pciSlotNumber = "23"

pciBridge7.pciSlotNumber = "24"

scsi0.pciSlotNumber = "16"

ethernet0.pciSlotNumber = "32"

ethernet1.pciSlotNumber = "33"

ethernet0.generatedAddress = "00:0c:29:4e:b9:99"

ethernet0.generatedAddressOffset = "0"

ethernet1.generatedAddress = "00:0c:29:4e:b9:a3"

ethernet1.generatedAddressOffset = "10"

ethernet1.connectionType = "nat"

[oreeh]

I think I saw you post this same VMX in another thread but for some reason didn't work then...

The other one was ESX 3.5 with a WS6 compatible VM in WS 6.5

[pbraren]

Dear "Virtually"

Thank you! It works! I just ran Nostalgia just fine, from within a VM (didn't bother adding scsi drive, used nfs on nas device instead)!

I am now successfully using ESX3.5 Update 2 Build 110268 (Aug 13) in Workstation 6.5 Release Candidate (build 110068) this time around, see also my post here (where I'm pointing folks to this post):

http://communities.vmware.com/thread/163209

I did the following:

1) I cut and pasted your entire vmx file contents, overwriting everyting in mine

2) I then changed just one line:

yours said:

scsi0:0.fileName = "ESXi.vmdk"

mine now says (to reflect the vmdk file name I use instead):

scsi0:0.fileName = "ESX35U2110268VM.vmdk"

Upon first boot, there were some errors that triggered a hasty automatic reboot, then on the 2nd boot, all was well, it works fine, speed seems reasonable too.

I then went back to one NIC bridged, no problems there either, network change was seamless and didn't require any changes to ESXi on my part.

Next stop, a bit of speed testing, then trying out ESXi3.5 Update 2 Build 110271 in Workstation 6.5 Release Candidate (build 110068) with this new vmx to see if I have the same success.

Thank you, my 11 month old question/thread is now truly answered, for ESX anyhow (and probably for ESXi too)!

(see VMX file conveniently attached, use it, or the below cut-and-paste of it, for steps 1 and 2 above, so others can have success now too).

Here's a cut-and-paste of my vmx file:

.encoding = "windows-1252"

config.version = "8"

virtualHW.version = "7"

scsi0.present = "TRUE"

scsi0.virtualDev = "lsilogic"

memsize = "1024"

scsi0:0.present = "TRUE"

scsi0:0.fileName = "ESX35U2110268VM.vmdk"

ide1:0.present = "TRUE"

ide1:0.autodetect = "FALSE"

ide1:0.deviceType = "cdrom-raw"

floppy0.present = "FALSE"

floppy0.startConnected = "FALSE"

floppy0.autodetect = "TRUE"

floppy0.fileName = "A:"

ethernet0.present = "TRUE"

ethernet0.connectionType = "bridged"

ethernet0.virtualDev = "e1000"

ethernet0.wakeOnPcktRcv = "FALSE"

ethernet1.present = "FALSE"

ethernet1.virtualdev = "e1000"

sound.present = "FALSE"

vmci0.present = "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"

displayName = "ESXi"

guestOS = "other-64"

nvram = "ESXi.nvram"

virtualHW.productCompatibility = "hosted"

ft.secondary0.enabled = "TRUE"

tools.upgrade.policy = "manual"

extendedConfigFile = "ESXi.vmxf"

monitor.virtual_exec = "hardware"

monitor_control.restrict_backdoor = "true"

isolation.tools.hgfs.disable = "TRUE"

isolation.tools.dnd.disable = "TRUE"

isolation.tools.copy.disable = "TRUE"

isolation.tools.paste.disable = "TRUE"

unity.showBorders = "FALSE"

unity.showBadges = "FALSE"

unity.enableLaunchMenu = "FALSE"

ide1:0.fileName = "E:"

ide1:0.startConnected = "FALSE"

ethernet0.addressType = "generated"

ethernet1.addressType = "generated"

tools.syncTime = "FALSE"

scsi0:0.redo = ""

pciBridge0.pciSlotNumber = "17"

pciBridge4.pciSlotNumber = "21"

pciBridge5.pciSlotNumber = "22"

pciBridge6.pciSlotNumber = "23"

pciBridge7.pciSlotNumber = "24"

scsi0.pciSlotNumber = "16"

ethernet0.pciSlotNumber = "32"

ethernet1.pciSlotNumber = "-1"

ethernet0.generatedAddress = "00:0c:29:10:92:21"

ethernet0.generatedAddressOffset = "0"

ethernet1.generatedAddress = "00:0c:29:10:92:2b"

ethernet1.generatedAddressOffset = "10"

ethernet1.connectionType = "nat"

uuid.location = "56 4d 00 3e 25 0e f1 8a-10 d7 c3 b1 97 10 92 21"

uuid.bios = "56 4d 00 3e 25 0e f1 8a-10 d7 c3 b1 97 10 92 21"

vmotion.checkpointFBSize = "22675456"

ethernet0.linkStatePropagation.enable = "TRUE"

[pbraren]

Good news, read next posts...

[pbraren]

oreeh,

had trouble with your formatting, perhaps it's the same idea as "Virtually"'s post, not sure.

[Virtually]

Hi all,

Full credit should granted to oreeh.

Without his VMX file, it wouldn't have been possible to solve this problem although I'd also like to see somewhere some documentation about exactly <why> it works and where it differs from other typical cookbooks like extravirt which are currently lacking.

The reason why I reposted orreh's VMX file is because the formatting is critically important to deploy without problems (I found his post encapsulated in <CODE> tags which apparently isn't supported by this forum so destroyed all formatting), then I documented a few modifications I made to make the file more generic and steps to make it a little easier for the newbie to apply.

[pbraren]

Thank you Virtually and Oreeh! Yeah, also interested in what Oreeh did and how it works. And if I has thought to post this thread to the forum as a question, I would be saying Oreeh deserves to be flagged as the correct answer.

I've now tested both ESX and ESXi 3.5 Update 2 inside VMware Workstation release candidate, and both function fine, VMs are able to boot, using same my same previously posted VMX file for both. I recorded a video of the whole setup, following along with VI3 in a box Xtravirt guide. This hi-res movie could later be turned into screenshot for screenshot documentation FYI, I just don't have the patience tonight. I also did about 20 minutes of basic speed tests at the end. VMs that took about 25 seconds to boot on physical 4GB host took about 150 seconds to boot in 1GB ESX/ESXi VMs inside VMware Workstation, yes slower, but quite usable nonetheless.

I have created a full (100 minute) video with audio, with easy fast-forward/rewind/pause functions, to screencast here:

[oreeh]

To be honest I never read the xtravirt papers so I can't comment on the differences.

I simply read the appropriate notes from the VMware engineers in the different threads. Credits go to them not me!

[afshin_blue]

thank you pbraren and Virtually and Oreeh for vmx file

and thank you pbraren for the video but it is a little heavy about 484 MB

i also put a video for other that have slow conection

ESX on workstation beta