Last night I received an anonymous tip from someone deep inside the VMware Workstation development team. The tip I received was all about running ESX 3.5 inside Workstation 6.5 and the possibility to power on a VM.
Try the latest Workstation 6.5 Beta 1 Refresh and you are in for a surprise...
This afternoon I downloaded the latest build of the Workstation 6.5 Beta and tried to run ESX 3.5 inside it.
Download VMware Workstation 6.5 Beta VMware Workstation 6.5 Beta
Latest Version: Beta | 5/12/08 | Build 91182
I created a standard (other Linux) VM with two CPU's, 1024 Gb mem and a 20 GB SCSI disk. I also added the following tree lines to the VMX file.
ethernet0.virtualDev = "e1000"
monitor.virtual_exec = "hardware"
monitor_control.restrict_backdoor = "true"
This time running ESX 3.5 inside WS 6.5 worked, no slow booting anymore. The test lab is online again. After installing ESX 3.5 update 1 the following screenshot showed up within minutes.
I contacted Keith Adams, he’s one of the WS 6.5 engineers and asked him if he could confirm that we can use ESX 3.5 in the latest build of VMware Workstation 6.5, he confirmed :
Indeed, we've changed the nomenclature around. It's now:
monitor.virtual_exec="hardware"|"software"|"auto"
(Note: monitor, not monitor_control.)
For all guest os types:
hardware = VT on Intel, SVM on AMD
software = BT for all 32-bit guests, and on BT-capable 64-bit AMD hardware for 64-bit guests as well
auto = Let us guess what to do (the default).
I also contacted Ulli over at sanbarrow.com, he’s the king of VMX tweaks and he responded directly with :
Hi Eric
use
guestOS = "other"
ethernet0.virtualDev = "e1000"
scsi0.virtualDev = "lsilogic"
monitor.virtual_exec = "hardware"
monitor_control.restrict_backdoor = "true"
I'd also recommend to install the ESX itself to IDE and use the LSI-logic disks for VMFS Use 2 virtual CPUs only when you have a quadcore system - otherwise use one CPU
Ulli
There's still an issue with powering on a VM.
*** VMware Workstation internal monitor error ***
vcpu-1:ASSERT vmcore/private/a20_shared.h:67
There is a problem in this version of VMware Workstation.
We rely on your feedback to improve the quality of our product. Please submit a support request that describes the problem at our Web page "http://www.vmware.com/info?id=8". Do not forget to attach the log file (C:\Virtual Machines\ESX 3.5\vmware.log) and the core file(s) (C:\Virtual Machines\ESX 3.5\vmware-core[0-1].gz, C:\Virtual Machines\ESX 3.5\vmware64-core[0-1].gz, C:\Users\Eric Sloof\AppData\Roaming\VMware\vmware-vmx-debug-4064.dmp).
To collect data to submit to VMware support, select Help > About and click "Collect Support Data". You can also run the "vm-support" script in the Workstation folder directly.
We appreciate your feedback,
-- the VMware Workstation team.
this vmx works for me.
From first sight I would say that ESX 3.5 in WS 6.5 is much slower than ESX 3.0.2 in WS 6.0.*
Ulli
checkpoint.vmState = ""
checkpointFBSize = "134217728"
config.version = "8"
deploymentPlatform = "windows"
displayName = "esx305"
ethernet0.addressType = "generated"
ethernet0.generatedAddress = "00:0c:29:a4:31:7f"
ethernet0.generatedAddressOffset = "0"
ethernet0.pciSlotNumber = "32"
ethernet0.present = "TRUE"
ethernet0.virtualdev = "e1000"
ethernet0.wakeOnPcktRcv = "FALSE"
ethernet1.addressType = "generated"
ethernet1.connectionType = "nat"
ethernet1.generatedAddress = "00:0c:29:a4:31:89"
ethernet1.generatedAddressOffset = "10"
ethernet1.pciSlotNumber = "33"
ethernet1.present = "TRUE"
ethernet1.virtualdev = "e1000"
ethernet1.wakeOnPcktRcv = "FALSE"
ethernet2.addressType = "generated"
ethernet2.connectionType = "custom"
ethernet2.generatedAddress = "00:0c:29:a4:31:93"
ethernet2.generatedAddressOffset = "20"
ethernet2.pciSlotNumber = "34"
ethernet2.present = "TRUE"
ethernet2.virtualdev = "e1000"
ethernet2.vnet = "VMNet4"
ethernet2.wakeOnPcktRcv = "FALSE"
floppy0.autodetect = "TRUE"
floppy0.fileName = "A:"
floppy0.present = "FALSE"
guestOS = "other"
ide0:0.fileName = "esx302system.vmdk"
ide0:0.present = "TRUE"
ide0:0.redo = ""
ide1:0.autodetect = "TRUE"
ide1:0.deviceType = "cdrom-image"
ide1:0.fileName = "G:\esx35\esx-3.5.0-64607.iso"
ide1:0.present = "TRUE"
isolation.tools.hgfs.disable = "TRUE"
memsize = "1024"
mks.enable3d = "TRUE"
mks.keyboardFilter = "allow"
monitor.virtual_exec = "hardware"
monitor_control.restrict_backdoor = "true"
monitor_control.vt32 = "true"
numvcpus = "1"
nvram = "Other.nvram"
pciBridge0.pciSlotNumber = "17"
pciBridge0.present = "TRUE"
pciBridge4.functions = "8"
pciBridge4.pciSlotNumber = "18"
pciBridge4.present = "TRUE"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge5.functions = "8"
pciBridge5.pciSlotNumber = "19"
pciBridge5.present = "TRUE"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge6.functions = "8"
pciBridge6.pciSlotNumber = "20"
pciBridge6.present = "TRUE"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge7.functions = "8"
pciBridge7.pciSlotNumber = "36"
pciBridge7.present = "TRUE"
pciBridge7.virtualDev = "pcieRootPort"
scsi0.pciSlotNumber = "16"
scsi0.present = "TRUE"
scsi0.virtualDev = "lsilogic"
scsi0:0.fileName = "vmfs_esx305.vmdk"
scsi0:0.present = "TRUE"
scsi0:0.redo = ""
sound.autodetect = "TRUE"
sound.fileName = "-1"
sound.present = "FALSE"
svga.autodetect = "TRUE"
tools.remindInstall = "TRUE"
tools.upgrade.policy = "useGlobal"
uuid.bios = "56 4d 8c 86 58 c4 80 c9-d4 72 30 48 cf a4 31 7f"
uuid.location = "56 4d 8c 86 58 c4 80 c9-d4 72 30 48 cf a4 31 7f"
virtualHW.productCompatibility = "hosted"
virtualHW.version = "6"
vmci0.id = "-811323009"
vmci0.pciSlotNumber = "35"
vmci0.present = "TRUE"
Add Comment
Can you confirm that you can actaully start the ESX 3.5 VM within Workstation 6.5 ?
Any additonal information on your confifguration would help.
Thanks in advance,
Michael K.
I am trying to run vmware 3.5 (ESX_3.5.0_Update_3_123630.iso) on Workstation 6.5 build 118166
I've allocated 1024MB of RAM and followed white paper on.
http://knowledge.xtravirt.com/white-papers/esx-3x.html
I have an issue of slow boot up. What is a "typical" bootup time?
Regards,
vitaly
-Tarry
Any ideas?
I contacted the WS development team and they told me it’s a bug and I should file a support request so I did. Let’s wait and see.
Eric Sloof
Yes - I can confirm that I was able to start VMs in the ESX-VM
If it fails for you - check your vmware.log.
If Workstation changes the vmx-entry
monitor.virtual_exec = "hardware"
to
monitor.virtual_exec = "software"
then your CPU doesn't qualify. Check your BIOS if you have enabled VT or SVM properly.
By the way - I use a HP notebook with Dualcore T5600 CPUs
Ulli
I'm also having problem with slow booting up the VM running ESX 3.5.0. It also used 100% CPU during boot up. Please advise. here is my vmx file:
.encoding = "windows-1252"
config.version = "8"
virtualHW.version = "4"
numvcpus = "2"
scsi0.present = "TRUE"
scsi0.virtualDev = "lsilogic"
memsize = "1024"
scsi0:0.present = "TRUE"
scsi0:0.fileName = "hostesx1.vmdk"
ide1:0.present = "TRUE"
ide1:0.fileName = "E:\VMware\Software\esx-3.5.0_Update_3-123630.iso"
ide1:0.deviceType = "cdrom-image"
ethernet0.present = "TRUE"
ethernet0.wakeOnPcktRcv = "FALSE"
ethernet1.present = "TRUE"
ethernet1.virtualdev = "e1000"
ethernet1.connectionType = "bridged"
ethernet1.addressType = "generated"
monitor_control.restrict_backdoor = "TRUE"
monitor.virtual_exec = "automatic"
roamingVM.exitBehavior = "go"
displayName = "hostesx1"
guestOS = "other"
nvram = "hostesx1.nvram"
virtualHW.productCompatibility = "esx"
ft.secondary0.enabled = "TRUE"
tools.upgrade.policy = "useGlobal"
extendedConfigFile = "hostesx1.vmxf"
floppy0.fileName = "A:"
ethernet0.addressType = "generated"
ethernet1.generatedAddress = "00:0c:29:1f:f2:d7"
uuid.location = "56 4d 94 6a a5 37 8b 12-68 45 91 d5 1a 1f f2 cd"
uuid.bios = "56 4d 94 6a a5 37 8b 12-68 45 91 d5 1a 1f f2 cd"
scsi0:0.redo = ""
vmotion.checkpointFBSize = "16777216"
ethernet0.generatedAddress = "00:0c:29:1f:f2:cd"
ethernet0.generatedAddressOffset = "0"
ethernet1.generatedAddressOffset = "10"
tools.remindInstall = "FALSE"
3.5i build 82664 works for me too - i can start VMs ...
essential entries I used for 3.5.i :
config.version = "8"
deploymentPlatform = "windows"
displayName = "esx35i"
ethernet0.present = "TRUE"
ethernet0.virtualdev = "e1000"
floppy0.present = "FALSE"
guestOS = "other"
ide1:0.autodetect = "TRUE"
ide1:0.deviceType = "cdrom-image"
ide1:0.fileName = "G:\esx35\esx-3.5.0-64607.iso"
ide1:0.present = "TRUE"
memsize = "1024"
monitor.virtual_exec = "hardware"
monitor_control.restrict_backdoor = "true"
numvcpus = "1"
scsi0.present = "TRUE"
scsi0.virtualDev = "lsilogic"
scsi0:0.fileName = "esx35i-system.vmdk"
scsi0:0.present = "TRUE"
sound.present = "FALSE"
virtualHW.version = "6"
Can we run ESX or ESXi on ESXi as VM?
I tried to use similar entries, but it didn't boot.
Thanks
I officially use VMWare Workstation 6.5 and also VMWare ESXi and 4 licenses of VMWare Infrastructure 3.5 upd3.
I tried to install (only for testing purpose) an instance of ESX (or ESXi) inside of Workstation 6.5 following the procedure described... without success. I use a NEC Powermate ML470 with 6Gb RAM, Intel Core 2 Duo (2,4Ghz). I believe that I've some issues with the Intel VT. Without enabling it, it's very very slow (unusable), and when enabling it, I get PSOD. In fact, the Intel VT is VT-D and not VT-X. It's just like if the VT wasn't discovered by Workstation. Some good idea would be helpfull.
Thanks in advance.
See the following - http://communities.vmware.com/docs/DOC-8978
After following the procedure it went from 2+ hours boot and constant 100% CPU usage, to
I had the same exact error and after lot of frustrating moments, I finally upgraded to VMware Workstation 6.5.2 and now everything is okie dokie. Hope this helps. Bye,
Well for slower boot issues, please enable Intel-VT or AMD-V. Else it will take ages to boot.
Regards,
Biju