I found a partial solution: I downloaded the source code for the 2.6.36 kernel and reinstalled VMware Player after rebooting in to the 2.6 kernel.
Just in case someone wants to know how to uninstall VMware Player, this is what I did:
- Code: Select all
sabayon jonquil # cd /usr/sbin
sabayon sbin # vmware-installer -u vmware-player 4.0.3.703057
Just replace the VMware version with the version you're using.
Unfortunately I'm still getting errors when I try to actually run a virtual machine.
"Failed to open device /dev/vmci"
And this is what I get in terminal:
- Code: Select all
sabayon jonquil # vmplayer
Logging to /tmp/vmware-root/modconfig-15720.log
filename: /lib/modules/2.6.36-sabayon/misc/vmmon.ko
supported: external
license: GPL v2
description: VMware Virtual Machine Monitor.
author: VMware, Inc.
depends:
vermagic: 2.6.36-sabayon SMP mod_unload modversions 586
filename: /lib/modules/2.6.36-sabayon/misc/vmnet.ko
supported: external
license: GPL v2
description: VMware Virtual Networking Driver.
author: VMware, Inc.
depends:
vermagic: 2.6.36-sabayon SMP mod_unload modversions 586
filename: /lib/modules/2.6.36-sabayon/misc/vmblock.ko
supported: external
version: 1.1.2.0
license: GPL v2
description: VMware Blocking File System
author: VMware, Inc.
srcversion: 84194DF903CB632D6BBB097
depends:
vermagic: 2.6.36-sabayon SMP mod_unload modversions 586
parm: root:The directory the file system redirects to. (charp)
filename: /lib/modules/2.6.36-sabayon/misc/vmci.ko
supported: external
license: GPL v2
version: 9.1.18.0
description: VMware Virtual Machine Communication Interface (VMCI).
author: VMware, Inc.
srcversion: 10020281868E6D4867D9260
alias: pci:v000015ADd00000740sv*sd*bc*sc*i*
depends:
vermagic: 2.6.36-sabayon SMP mod_unload modversions 586
parm: disable_host:Disable driver host personality - (default=0) (bool)
parm: disable_guest:Disable driver guest personality - (default=0) (bool)
parm: disable_msi:Disable MSI use in driver - (default=0) (bool)
parm: disable_msix:Disable MSI-X use in driver - (default=0) (bool)
filename: /lib/modules/2.6.36-sabayon/misc/vsock.ko
supported: external
alias: vmware_vsock
license: GPL v2
version: 9.1.1.0
description: VMware Virtual Socket Family
author: VMware, Inc.
srcversion: 63D4F9452B12D9EA15160C1
depends: vmci
vermagic: 2.6.36-sabayon SMP mod_unload modversions 586
filename: /lib/modules/2.6.36-sabayon/misc/vmmon.ko
supported: external
license: GPL v2
description: VMware Virtual Machine Monitor.
author: VMware, Inc.
depends:
vermagic: 2.6.36-sabayon SMP mod_unload modversions 586
(gconftool-2:15990): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to get value for `/system/http_proxy/use_http_proxy': No D-BUS daemon running
(gconftool-2:15991): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to get value for `/system/proxy/mode': No D-BUS daemon running
(gconftool-2:15992): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to get value for `/system/http_proxy/use_http_proxy': No D-BUS daemon running
(gconftool-2:15993): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to get value for `/system/proxy/mode': No D-BUS daemon running
(gconftool-2:15994): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to get value for `/system/http_proxy/use_http_proxy': No D-BUS daemon running
(gconftool-2:15995): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to get value for `/system/proxy/mode': No D-BUS daemon running
I tried modprobe vmci. It didn't return any errors, but VMware is still returning the same error about vmci being missing.
I'm going to keep working at this. I really wish someone here knew how to help though.