VMTN

I did install fusion 1.1.1 which has the fix according to this thread: On the end of this thread http://communities.vmware.com/thread/110191 , a fix is reportedly included in VMWare Fusion 1.1.1 (http://www.vmware.com/download/fusion/).

A quick look at process mon showed this:

93      vmnet-bridge     root     0.0     1     380.00 KB     586.70 MB     Intel     

91      vmnet-dhcpd     root     0.0     1     208.00 KB     585.93 MB     Intel     

82      vmnet-dhcpd     root     0.0     1     344.00 KB     585.93 MB     Intel     

76      vmnet-natd     root     0.0     1     368.00 KB     586.21 MB     Intel     

88      vmnet-netifup     root     0.0     1     152.00 KB     586.64 MB     Intel     

85      vmnet-netifup     root     0.0     1     152.00 KB     586.64 MB     Intel     

139      VMware Fusion     ihsurf     0.6     6     57.91 MB     899.39 MB     Intel     

155      vmware-vmx     root     10.9     31     576.61 MB     1.37 GB     Intel     

161      vmware-vmx     root     7.7     9     302.80 MB     1.05 GB     Intel     

So it looks like everything runs as root already....

I guess I need to see the fix actually work... I have not tested yet with fusion 1.1.1.

I will let you know.

Don't waste your time - ESX 3.5 doesn't run with

monitor_control.vt32 = TRUE on Intel Dual Core.

That vmx you posted looks like it would work with ESX 3.0.2 and your CPU.

85      vmnet-netifup     root     0.0     1     152.00 KB     586.64 MB     Intel

139      VMware Fusion     ihsurf     0.6     6     57.91 MB     899.39 MB     Intel

155      vmware-vmx     root     10.9     31     576.61 MB     1.37 GB     Intel

http://..

 

So it looks like everything runs as root already....

Not quite - the VMware Fusion process appears to be running as the 'ihsurf' user.

Let me know how you go with your testing.

Hi 

How did you fix the "unexpected IRQ trap at vector bf" error?  If your the gshields from cbt you didn't do it through reduced memory or single cpu.. 

I think there are a few of us with this issue

thanks in advance   

I am having the same problem too.  I followed documentation to the "T" and still have an issue where I can only run one ESX server at a time.  The moment I launch a second VM ESX server I receive the same error regarding the IRQ.  But as soon as I power both VMs up and bring the second ESX server online first it boots up with no issues.  I have an Intel Core 2 Duo T7800 with 4GB RAM running on a Dell Latitude D630.  The VM ESX servers are configured with 3 network adapters (1-COS, 1-VMs and 1-iSCSI) all are configured for e1000.  Any one have an idea of what is going on?

Hi

No idea why this is happening, other that the issues previously mentioned by gshields. I used the workaround and reconfigured each esx with ONE cpu, after this everything worked fine, cpu workload is high, but you have a higher spec machine than I do, so it should work even better. ( I have a dell vostro with Intel Core 2 Duo T7250 with 3GB RAM, vista business, with all areo features turned off )

Using workstation 6.0.259824

- two esx 3.0.1-32039 vms ( 1 cpu each, 1024mb ram each), openfiler 2-2-x86 (1 cpu, 512 ram), and one w2k3 R2 standard (1 cpu 512 ram)  (DNS, domain controller and  VC 2.5 with msde)

- -   Inside this I can run two w2k3 machines (256 ram) - VMotion is slow, 3-5 min with a 90 sec service interupt, Here is were the single cpu thrashes, also can run additional NT4 server (128 mb ram), can clone, migrate, etc, does everything I ask, but slowly

However in the cbt videos a certain G Shields does everything above with 2 cpus per esx, he posted his machine spec and it is an Intel Core 2 Duo  E6600 with Windows Vista Home Premium, I would like to know how it did it, no further explanation is given in the videos other than the basic hack of   vmx file ( vt extensions, backdoor and network card)

G Shields your videos are great, excellent instruction - how did you fix the issue  ???

Any other users on this thread using the Intel Core 2 Duo - Santa Rosa - that have any success stories to tell running 2 or more ESX VMs with 2 vCPUs? I am interested in learning how one has been successful with this configuration as I keep falling on my face with this one. I have tried disabling Intel Dynamic Acceleration thinking that it may be the cause but I cannot for the life of me get 2 ESX VMs to power on at the same time without one of them failing to launch.

I have tried another Dell Latitude D630 with an Intel Core 2 Duo T7700 - Santa Rosa - and ran into the same issue with the 2xESX VMs with 2 vCPUs not being able to launch both without the second one having the IRQ error.  I think that this problem maybe isolated to the Intel Core 2 Duo Santa Rosa line of processors...anyone else out there have any evidence suggesting otherwise?

ESX 302 from LiveDVD

basically its possible - Screenshot shows LiveDVD after boot on a diskless host.

Explorer window listing E:\ shows content of a DVD mounted to E:

a 1700 MB ESX-vmdk + 1 MB  snapshot

After boot of the LiveCD you copy the snapshot to ramdisk and start the VM from there.

Of course you could also start it on a box with local VMFS - then you need to add the physical scsi-disks as rawdisks to the ESX 302 VM

I have exactly the same issue with a T7300 santa rosa, in my HP 6910p.

I can start the first vm running ESX, but on booting the second it fails to load the vmkernel.

a royal pain in the ar$e

any word on a fix ?

Are you also overcommitting the CPUs? What if the ESX VMs are configured for one vCPU each?

Hello.  I got my ESX server to install on Workstation 6.5 beta.  My Ubuntu guest running off the ESX server is very slow (20-30 min to load to the login screen).  Any sugguestions to speed it up? Below is my ESX configuration.  I gave the Ubuntu server 2 cpus and 2GB of RAM but it didn't appear to help much. My system is a Windows Vista 64bit, 8GB of RAM, and a Q6600 CPU on a Nvidia Mobo with VT enabled.  Thanks for any tips!

.encoding = "windows-1252"

config.version = "8"

virtualHW.version = "7"

vcpu.hotadd = "TRUE"

maxvcpus = "4"

scsi0.present = "TRUE"

scsi0.virtualDev = "lsilogic"

memsize = "4000"

scsi0:0.present = "TRUE"

scsi0:0.fileName = "Red Hat Enterprise Linux 4 64-bit.vmdk"

ide1:0.present = "TRUE"

ide1:0.autodetect = "TRUE"

ide1:0.deviceType = "cdrom-image"

floppy0.present = "FALSE"

ethernet0.present = "TRUE"

ethernet0.virtualDev = "e1000"

ethernet0.wakeOnPcktRcv = "FALSE"

ethernet0.linkStatePropagation.enable = "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 = "Red Hat Enterprise Linux 4 64-bit"

guestOS = "rhel4-64"

nvram = "Red Hat Enterprise Linux 4 64-bit.nvram"

virtualHW.productCompatibility = "hosted"

ft.secondary0.enabled = "TRUE"

tools.upgrade.policy = "useGlobal"

extendedConfigFile = "Red Hat Enterprise Linux 4 64-bit.vmxf"

ide1:0.fileName = "D:\Stuff\ISOs\VMware-VMvisor-InstallerCD-3.5.0_Update_2-110271.i386.iso"

ethernet0.addressType = "generated"

uuid.location = "56 4d 1f 0c dc 10 c2 d7-34 fd 53 38 47 57 ef 89"

uuid.bios = "56 4d 1f 0c dc 10 c2 d7-34 fd 53 38 47 57 ef 89"

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"

vmci0.pciSlotNumber = "33"

ethernet0.generatedAddress = "00:0c:29:57:ef:89"

ethernet0.generatedAddressOffset = "0"

vmci0.id = "1196945289"

tools.remindInstall = "TRUE"

numvcpus = "2"

> I gave the Ubuntu server 2 cpus and 2GB of RAM but it didn't appear to help much.

That settings sure are contra-productive. Don't use 2 cpus for the nested VM - assign as little RAM as possible for the nested VMs

Also try if you get better performance when assigning only 1 cpu for the ESX itself.

Why do you use guestOS = "rhel4-64" ???

What is this good for ?

vcpu.hotadd = "TRUE"

maxvcpus = "4"

___________________________________

description of vmx-parameters: http://sanbarrow.com/vmx.html

VMware-liveCD: http://sanbarrow.com/moa.html

I have problem related you problem might be you have any solution on this.

I have WC 6.5.1 and ESX 3.5 update 3 its working fine very smoothly but when i start guest VM (nested vm) its starting without error. but when i am going to start console of vm to see what going on, it was just blank and after few min i got mesg on black window connection failed because of slow respond. any solution on this ?