Well, after going through the steps described in my last post, I had a successful run of vmware-config.pl and was *finally* able to run the VMware Admin Console.
However, whenever I tried to Power On a VM, I would get a general error message. I turned on logging for one of the VMs and got the following:
Unable to change virtual machine power state: The process exited with an error:
vmxvmdb: Index name being generated from config file
POST(no connection): Version mismatch with vmmon module: expecting 138.0, got 208.0.
You have an incorrect version of the `vmmon' kernel module.
Try reinstalling VMware Server.
I'm pretty sure this is because of using the patch that modified the VM module source.
So, I'm stepping back and going through the painful process of running a patch against the Linux kernel source and recompiling the kernel, to get past the init_mm issue.
Recompiling the kernel takes forever, and something went wrong on my first attempt, so I am re-recompiling now...
Subscribe to:
Post Comments (Atom)
What was the kernel patch you ran? I've been fighting here to get F11 x64 running with VMware Server and it's making me crazy. VMWware Workstation 6.5.2 works on my 32 bit F11 box at work but I need to use Server 1.x here at home.
ReplyDeleteKhaytsus,
ReplyDeleteI downloaded this patch:
http://www.insecure.ws/warehouse/vmware-update-2.6.29-5.5.9-3.tar.bz2
It is described in the thread here:
http://communities.vmware.com/thread/205686
Keep in mind that this matched my kernel ... as you know, VMware Server is really particular.
I'm assuming since you say you have FC11, that you have Kernel 2.6.29.x.
Even after using this patch, I went through a TON of steps, including recompiling the kernel. All steps are described in my subsequent blog posts.
I really wish you the best with this ... VMware Server is really frustrating and painful to set up.
Philip