Re: VMware Workstation Weirdness - Can't Launch VM
- From: "Christopher A. Williams" <chriswfedora@xxxxxxxxxx>
- Date: Tue, 10 Jun 2008 15:26:46 -0600
On Tue, 2008-06-10 at 15:48 -0500, Kevin Martin wrote:
<snip...>
Christopher A. Williams wrote:
On Tue, 2008-06-10 at 15:01 -0400, max bianco wrote:
On Mon, Jun 9, 2008 at 10:58 PM, Christopher A. Williams
<chriswfedora@xxxxxxxxxx> wrote:
I've been scouring the VMware communities and forums for this as well,what does the log have to say?
but I thought I would also ask here.
Has anyone else seen the following error on VMware Workstation 6.5b
(build 91182) when trying to launch a virtual machine?
================================================
VMware Workstation unrecoverable error: (vcpu-0)
VCPU 0 RunVM failed: Operation not permitted.
A log file is available in "/opt/Virtual Machines/Windows XP
Professional Test/vmware.log". A core file is available in "/<path to
virtual machine>/core.#####". Please request support and include the
contents of the log file and core file.
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.
Unable to change virtual machine power state: Cannot find a valid peer
process to connect to.
================================================
Not sure what the problem is. Running on a Quad-core Intel with 4GB RAM,
plus the latest F9 kernel and patches. Ideas welcome...
It's pretty long, and very routine.
Here's what appears to be the key message though:
Jun 10 14:38:26.427: vcpu-0| VCPU 0 RunVM failed: Operation not
permitted.
Jun 10 14:38:26.427: vcpu-0| Panic: can't get userlevel lock.
After that, there are no other errors in the log.
I'll do the VM Support Script and see what happens there as well...
What are the permissions/ownerships on the VM directories/files? Are
they adequate to run as the user you are trying to start the VM as?
At one time there was a need to setuid the vmware executable also.
Are you trying to run the virtual machine as root? If not, will it
start if you do?
...Well - I found the cause of _this_ problem after some digging
through /var/log/messages. But it still doesn't make sense to me.
What I found was that /var/log/messages reported that VMware couldn't
get a lock on VT because it was already in use by something else...
Solution: Uninstall all other things virtualization on the box. I still
had some KVM/QEMU components lying around.
That said, it doesn't make sense to me because I have a full KVM/QEMU
installation running on my laptop with the same F9 setup. Workstation
works there with no issues.
...So now the question is why will VMware Workstation and KVM live
together happily on one system but not the other?...
I'll keep digging.
Cheers,
Chris
--
==================================
By all means marry;
If you get a good wife, you'll be happy.
If you get a bad one, you'll become a philosopher.
--Socrates
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
- Follow-Ups:
- References:
- VMware Workstation Weirdness - Can't Launch VM
- From: Christopher A. Williams
- Re: VMware Workstation Weirdness - Can't Launch VM
- From: max bianco
- Re: VMware Workstation Weirdness - Can't Launch VM
- From: Christopher A. Williams
- Re: VMware Workstation Weirdness - Can't Launch VM
- From: Kevin Martin
- VMware Workstation Weirdness - Can't Launch VM
- Prev by Date: Re: F9: Canon LBP2900 no go: "usblp1: error -32 reading printer status"
- Next by Date: RE: Can I rename a user??
- Previous by thread: Re: VMware Workstation Weirdness - Can't Launch VM
- Next by thread: Re: VMware Workstation Weirdness - Can't Launch VM
- Index(es):
Relevant Pages
|
