VMware

This Question is Answered

2 "helpful" answers available (6 pts)
4 Replies Last post: Oct 9, 2008 12:57 PM by MDeanCTS  

Can't start VMWare Server 2.0 and Microsoft Virtual Server 2005 R2 VM at same time? Error message: "VCPU 0 RunVM failed: -2" posted: Oct 9, 2008 9:23 AM

Click to view MDeanCTS's profile Novice 4 posts since
May 15, 2008
I have a VMWare Server 2.0 virtual machine that works just fine on its own and a Microsoft Virtual Server 2005 R2 virtual machine that also works just fine on its own. However, if I have the MS machine up and running I cannot start the VMWare machine or if the VMWare machine is up and running and I start the MS machine it will start up successfully, but the VMWare machine crashes immediately.


The following is the error reported in the VMWare log file right before the crash dump when I attempt to start the VMWare machine with the MS machine already running:

Oct 09 11:01:31.052: vcpu-0| VCPU 0 RunVM failed: -2.
Oct 09 11:01:31.052: vcpu-0| Panic: can't get userlevel lock.
Oct 09 11:01:31.052: vcpu-0| Win32 object usage: GDI 4, USER 5

I am running Vista 64 and I have checked that I have the latest drivers, BIOS, etc. for my machine. I appreciate any help or suggestions that anyone might be able to provide.

Thanks,
Matt

Click to view RDPetruska's profile Guru 15,875 posts since
Jan 11, 2005
You are correct. You cannot run different hypervisors at the same time. You can have both products installed on the same PC, but you cannot run them both (powered on guests) at the same time.
Click to view jmattson's profile Master 1,223 posts since
Mar 29, 2006
Current VMware products comprise two hypervisors: a 32-bit hypervisor for handling legacy 32-bit code and compatibility mode code, and a 64-bit hypervisor for handling 64-bit code. The latter is only relevant for 64-bit VMs. Switching between a 64-bit host OS and the 32-bit hypervisor requires that the processor transition briefly through non-paged mode. (The same also applies for switching between a 32-bit host OS and the 64-bit hypervisor, but that is not relevant to your problem.)

I suspect that you are running on Intel hardware and that MS Virtual Server is configured to use VT. VT introduces a new operating mode, known as "VMX operation," which places some constraints on the processor. In particular, the processor cannot be in non-paged mode while it is in VMX operation. It is likely that MS Virtual Server is leaving the host in VMX operation, which means that VMware Server cannot make the transition from the 64-bit host OS to the 32-bit hypervisor.

To make a long story short, you should be able to run these hypervisors simultaneously if you configure MS Virtual Server not to use VT.

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities