Sorry should have mentioned that earlier when doing the research, you MUST have dual core or processor system.
Actually I was told by Petr(?) that there are actually things missing in WS5 code base from the public version that make it impossible to run ESX. VMware engineers had a special build which enabled it.
Try it out though you will probably need these settings:
isolation.tools.setPtrLocation.disable = "TRUE"
isolation.tools.setVersion.disable = "TRUE"
isolation.tools.getVersion.disable = "TRUE"
monitor_control.disable_directexec = "TRUE"
monitor_control.disable_chksimd = "TRUE"
monitor_control.disable_ntreloc = "TRUE"
monitor_control.disable_selfmod = "TRUE"
monitor_control.disable_reloc = "TRUE"
monitor_control.disable_btinout = "TRUE"
monitor_control.disable_btmemspace = "TRUE"
monitor_control.disable_btpriv = "TRUE"
monitor_control.disable_btseg = "TRUE"[/code]
I then moved the installation on my even older
P3-1GHz machine which has 2 CPUs and I use this as a
ESX host for my lab. On this machine the startup of
VI3 went smoothly without any errors but it took 3hrs
to display the console screen and it was not
10 points for persistance!!
As previously stated VT is vital...
Unfortunately, I'm still getting the "You may not power on a virtual machine in a virtual machine" error, even after setting
isolation.tools.getVersion.disable = "TRUE"
I'll now try running the player in a VM.
To start a WS 6 inside a WS 6 I use
monitor_control.restrict_backdoor = "TRUE"
without any isolation.tools parameters
I am getting the same errors that you've been getting Vliegenmepper associated with the "unexpected IRQ trap at vector bf" and the "running vmkernel built on \_Unknown_" error. But, here's the weird part with mine. I have created two ESX instances as VM's inside Workstation. When I boot the first one, it boots just fine with the VMKernel loading just fine. When I boot the second one, I start getting the errors. The same happens if I boot them in reverse order. The first one that gets booted works fine and the second won't work.
Since we're seeing this "unexpected IRQ trap at vector bf" error, is it possible that they're trying to share a resource that they can't? I'm running this on a PowerSpec X300 with an Intel Core Duo E6600, which is one of the newest Intel processors that does support the VT extensions. The spec for this machine is at: http://www.powerspec.com/systems/system_specs.phtml?selection=X300. Does anyone know why I can successfully run one, but not two simultaneous ESX VM's in Workstation? Is anyone else seeing this?
I thought they were after running it on Server which is ~5.5.1 code. However, as you point out you can power on other VMware products inside WS6.
Although I have yet to get this working properly pending getting hold of a suitable machine.
From the experience I have had, it could be that although your CPU supports VT, the motherboard either doesn't or it is currently disabled in the BIOS.
Have a look.
Message was edited by: I just noted that one ESX does run properly that means VT must be enabled.
Are you able to run a VM on the ESX with ease? this would prove VT is working on your machine.
This could be due to the fact the ESX VM requires a minimum of 2 CPU's therefore it cannot start the second ESX VM as you probably only have a single Dual core CPU.
The CPU does support VT and I've made sure that its enabled in the BIOS. The first VM boots fantastically fast (like 30-60 seconds). The second one boots really fast as well, but I'm getting red text that flashes by before I can capture it -- then I get the error messages shown above.
The two-processor possiblity might be going somewhere, but I was under the impression that Workstation should be abstracting those processors so both VM's can use them.
Others on this thread have gotten 2x ESX servers running simultaneously. Are you doing this with 2-CPU machines or 4-CPU machines?
Thanks for any help you can provide with this. I need to get these to work on a single machine for portability reasons (and VMotion... I can't seem to VMotion machines to my laptop -- I'm getting a CPU register error there).
Hi to all. I would also like to share my experiance. My setup is like this:
-IBM T60 with T7200 VT enabled CPU
-VMware Workstation 6
-I installed 2 ESX inside WS6 as instructed (VT enabled and e1000 ethetnet change in .vmx)
-one w2k3 VM for VC and iSCSI (StarWind 3.2.2 SW iSCSI)
-managed to install VM on iSCSI
-VMotion between two virtual ESXs on iSCSI
All of this was instaled in isolated (Host only) network on WS6.
For better performance I instaled ESX1 and ESX2 on external USB HDD, VM for VirtualCenter was instaled on internal laptop HDD.
Will try now also HA and DRS.
For all that are successfully getting multiple instances of ESX to boot on the same host machine, are you using Windows XP as your host machine O/S or Windows Vista?
I'm currently running all of this on Vista 64-bit -- with all UAC features disabled -- and I'm wondering if its still something within Vista that's causing my failures.
I WANT THE DL380... Let me know if it is still being offered!
I am trying to get this to work, but somehow unable to do so. Even though VT is enabled in the BIOS (I have an HP nc6400 with T5600 C2D proc), when I try to start the VM, it gives an error stating - "This CPU is VT-capable, but VT is not enabled. (Check your BIOS/firmware settings.)
Module Monitor power on failed."
The following is my .vmx file -
config.version = "8"
virtualHW.version = "4"
numvcpus = "2"
scsi0.present = "TRUE"
scsi0.virtualDev = "lsilogic"
memsize = "1024"
scsi0:0.present = "TRUE"
scsi0:0.fileName = "ESX001.vmdk"
ide1:0.present = "TRUE"
ide1:0.fileName = "D:"
ide1:0.deviceType = "cdrom-raw"
floppy0.autodetect = "TRUE"
ethernet0.present = "TRUE"
ethernet0.virtualDev = "e1000"
ethernet0.connectionType = "bridged"
ethernet0.addressType = "generated"
ethernet0.wakeOnPcktRcv = "FALSE"
svga.autodetect = "TRUE"
mks.keyboardFilter = "allow"
displayName = "ESX001"
guestOS = "redhat"
nvram = "Red Hat Linux.nvram"
deploymentPlatform = "windows"
virtualHW.productCompatibility = "esx"
tools.upgrade.policy = "useGlobal"
monitor_control.restrict_backdoor = TRUE
monitor_control.vt32 = TRUE
ide1:0.autodetect = "FALSE"
floppy0.fileName = "A:"
isolation.tools.hgfs.disable = "TRUE"
ethernet0.generatedAddress = "00:0c:29:4a:bd:30"
uuid.location = "56 4d 0b 78 7d b7 73 36-43 66 e0 21 e8 4a bd 30"
uuid.bios = "56 4d 0b 78 7d b7 73 36-43 66 e0 21 e8 4a bd 30"
scsi0:0.redo = ""
ethernet0.generatedAddressOffset = "0"
floppy0.startConnected = "FALSE"
ide1:0.startConnected = "FALSE"
Can you please help me figure out what is wrong and how I can get this working?
Thanks in advance!
did you power off after enabling VT?