Actually, i just went and read the whitepaper here: http://www.xtravirt.com/index.php?option=com_remository&Itemid=75&func=select&id=3

It suggests the entries you mention, plus a few more. Upon doing this, i reinstalled ESX 3.5 and boom, it booted up almost instantly.. lol.

Yes, Chris, you obviously missed a step. Reread the whitepaper.

I had the same experience earlier with 3.0.2 working with the vlance NIC but not 3.5. The final build of 3.5 was released tonight (64607) so if you downloaded 3.5 last week you'll want to get the final release.

I had ESX3.02 running under WS6 with no problems after following the xtravirt whitepaper, done the same with ESX3.5 but get the following error in WS6 when starting a VM guest under ESX.
This causes VM6 to turn of the ESX host that is trying to start the VM.

MONITOR PANIC: vcpu-0:ASSERT vmcore/private/physMem_shared.h:38 bugNr=131897

Any ideas?

I have the same problem, the VM will start-up to 100% and then WS6 crashes. I attached the coredump.

• VMware Workstation internal monitor error ***

vcpu-0:ASSERT vmcore/private/physMem_shared.h:38 bugNr=131897
Please report this problem by selecting menu item Help > VMware on the Web > Request Support, or by going to the Web page "http://www.vmware.com/info?id=8&logFile=C%3a%5cVirtual%20Machines%5cESX35%5cvmware%2elog&coreLocation=C%3a%5cVirtual%20Machines%5cESX35%5cvmware%2dcore%5b0%2d1%5d%2egz". Please provide us with the log file (C:\Virtual Machines\ESX35\vmware.log) and the core file (C:\Virtual Machines\ESX35\vmware-core0-1.gz).
If the problem is repeatable, please select 'Run with debugging information' in the Options panel of Virtual Machine Settings. Then reproduce the incident and file it according to the instructions.
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 will respond on the basis of your support entitlement.
We appreciate your feedback,

• the VMware Workstation team.

Dec 10 20:30:10.944: vcpu-1| SEG_SS 1254 count=119999
Dec 10 20:30:27.881: vcpu-0| SEG_SS 1254 count=79999
Dec 10 20:30:30.923: vcpu-1| SEG_SS 1254 count=129999
Dec 10 20:30:47.946: vcpu-0| SEG_SS 1254 count=89999
Dec 10 20:30:50.979: vcpu-1| SEG_SS 1254 count=139999
Dec 10 20:31:07.983: vcpu-0| SEG_SS 1254 count=99999
Dec 10 20:31:11.021: vcpu-1| SEG_SS 1254 count=149999
Dec 10 20:31:24.898: vcpu-1| SEG_SS 1254 count=159999
Dec 10 20:31:28.527: vcpu-0| SEG_SS 1254 count=109999
Dec 10 20:31:30.361: vcpu-1| MONITOR PANIC: vcpu-1:ASSERT vmcore/private/physMem_shared.h:38 bugNr=131897
Dec 10 20:31:30.361: vcpu-1| Core dump with build build-59824
Dec 10 20:31:30.361: vcpu-1| Writing monitor corefile "C:\Virtual Machines\ESX35\vmware-core0.gz"
Dec 10 20:31:30.406: vcpu-1| Beginning monitor coredump
Dec 10 20:31:30.597: vcpu-1| End monitor coredump
Dec 10 20:31:30.597: vcpu-1| Beginning extended monitor coredump
Dec 10 20:31:30.597: vcpu-1| Writing anonymous pages at pos: 401000
Dec 10 20:31:31.535: vcpu-1| Writing monitor corefile "C:\Virtual Machines\ESX35\vmware-core1.gz"
Dec 10 20:31:31.548: vcpu-1| Beginning monitor coredump
Dec 10 20:31:31.682: vcpu-1| End monitor coredump
Dec 10 20:31:31.682: vcpu-1| Beginning extended monitor coredump
Dec 10 20:31:31.682: vcpu-1| Writing anonymous pages at pos: 401000
Dec 10 20:31:32.636: vcpu-1| Msg_Post: Error
Dec 10 20:31:32.636: vcpu-1| http://msg.log.monpanic *** VMware Workstation internal monitor error ***
Dec 10 20:31:32.636: vcpu-1| vcpu-1:ASSERT vmcore/private/physMem_shared.h:38 bugNr=131897
Dec 10 20:31:32.636: vcpu-1| http://msg.log.monpanic.report Please report this problem by selecting menu item Help > VMware on the Web > Request Support, or by going to the Web page "http://www.vmware.com/info?id=8&logFile=C%3a%5cVirtual%20Machines%5cESX35%5cvmware%2elog&coreLocation=C%3a%5cVirtual%20Machines%5cESX35%5cvmware%2dcore%5b0%2d1%5d%2egz". Please provide us with the log file (C:\Virtual Machines\ESX35\vmware.log) and the core file (C:\Virtual Machines\ESX35\vmware-core0-1.gz).
Dec 10 20:31:32.636: vcpu-1| http://msg.log.monpanic.win32debug If the problem is repeatable, please select 'Run with debugging information' in the Options panel of Virtual Machine Settings. Then reproduce the incident and file it according to the instructions.
Dec 10 20:31:32.636: vcpu-1| http://msg.log.monpanic.vmSupport.windowsOrLinux 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.
Dec 10 20:31:32.636: vcpu-1| http://msg.log.monpanic.entitlement We will respond on the basis of your support entitlement.
Dec 10 20:31:32.636: vcpu-1| http://msg.log.monpanic.finish We appreciate your feedback,
Dec 10 20:31:32.636: vcpu-1| -- the VMware Workstation team.
Dec 10 20:31:32.636: vcpu-1|

---

Dec 10 20:31:53.186: vcpu-1| Ignoring broadcast request
Dec 10 20:31:53.186: vcpu-1| Exiting vcpu-1
Dec 10 20:31:53.187: vcpu-0| Writing monitor corefile "C:\Virtual Machines\ESX35\vmware-core0.gz"
Dec 10 20:31:53.226: vcpu-0| Beginning monitor coredump
Dec 10 20:31:53.485: vcpu-0| End monitor coredump
Dec 10 20:31:53.485: vcpu-0| Beginning extended monitor coredump
Dec 10 20:31:53.485: vcpu-0| Writing anonymous pages at pos: 401000
Dec 10 20:31:53.634: vmx| VTHREAD watched thread 5 "vcpu-1" died
Dec 10 20:31:53.649: mks| VTHREAD watched thread 0 "vmx" died
Dec 10 20:31:54.199: kbh| VTHREAD watched thread 0 "vmx" died
Dec 10 20:31:54.426: vcpu-0| Exiting vcpu-0

I also had this problem

Has anyone been successful in starting a guest VM in VI3.5 on WS6?

I have also had the same problem myself with WS6. I have tried to start the VM up via the VC & directly connected to the ESX server with Inf client and error shown appears.

Once I click OK on the error box the ESX server crashes. I am using a dual core CPU with VT turned on in bios with 2GB memory and setup using Xtravirt guide & I am using Openfiler as my ISCSI storage.

• VMware Workstation internal monitor error ***

vcpu-1:ASSERT vmcore/private/physMem_shared.h:38 bugNr=131897
Please report this problem by selecting menu item Help > VMware on the Web > Request Support, or by going to the Web page "http://www.vmware.com/info?id=8&logFile=C%3a%5cDocuments%20and%20Settings%username%2eENTERPRISE%5cMy%20Documents%5cMy%20Virtual%20Machines%5cLapESX02%5cvmware%2elog&coreLocation=C%3a%5cDocuments%20and%20Settings%username%5cMy%20Documents%5cMy%20Virtual%20Machines%5cLapESX02%5cvmware%2dcore%5b0%2d1%5d%2egz". Please provide us with the log file (C:\Documents and Settings\username\My Documents\My Virtual Machines\LapESX02\vmware.log) and the core file (C:\Documents and Settings\username\My Documents\My Virtual Machines\vmware-core0-1.gz).
If the problem is repeatable, please select 'Run with debugging information' in the Options panel of Virtual Machine Settings. Then reproduce the incident and file it according to the instructions.
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 will respond on the basis of your support entitlement.
We appreciate your feedback,

• the VMware Workstation team.

If anyone has any tips or suggestions on getting this running let me know.

Many Thanks

Paul