Christopher A. Williams wrote:
On Tue, 2008-06-10 at 15:48 -0500, Kevin Martin wrote:
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,
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...
what does the log have to say?
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...
<snip...>
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?...
What's different on them? KDE vs GNOME? 32 bit vs 64 bit? video devices?
filesystems? which kernel is running? Try to outline the differences no
matter if you think it is relevant or not. Obviously harddrive size
probably won't have an impact so use some judgement.
--
"The force is with you young Skywalker but you are not a Jedi yet."
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
