☰

Ubuntu 15.10 上的 VMware Player

tag-icon • tag-icon vmware 15.10 vmware-player
Ubuntu 15.10 上的 VMware Player

我刚刚上传到 Ubuntu 15.10，但我的 vmware 播放器不再工作了。

我尝试遵循建议的解决方案这里和这里但这对我来说似乎还不够。

当我运行时，vmplayer我收到很多错误消息，例如

Gtk-Message: Failed to load module "unity-gtk-module": libunity-gtk-module.so: cannot open shared object file: No such file or directory

(vmware-modconfig:9701): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

此时，它要求我编译并加载几个模块到内核中。如果我说，Install它会要求我输入密码，然后给出一些错误，例如

Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory             
Gtk-Message: Failed to load module "overlay-scrollbar"
Gtk-Message: Failed to load module "unity-gtk-module"

Gtk-Message: Failed to load module "canberra-gtk-module"

(vmware-gksu:9701): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.

(vmware-gksu:9701): GLib-GObject-CRITICAL **: g_object_new: assertion 'G_TYPE_IS_OBJECT (object_type)' failed

(vmware-gksu:9701): Pango-WARNING **: Failed to load Pango module '/usr/lib/vmware/libconf/lib/pango/1.6.0/modules/pango-basic-fc.so' for id 'BasicScriptEngineFc'

(vmware-gksu:9701): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.

(vmware-gksu:9701): GLib-GObject-CRITICAL **: g_object_new: assertion 'G_TYPE_IS_OBJECT (object_type)' failed

然后它就退出了。

我该怎么做才能解决这个问题？我是个菜鸟，所以请尽量详细地说明。

更新：如果我尝试运行sudo vmware-modconfig --console --install-all输出是

Stopping VMware services:
VMware Authentication Daemon                                        done
VM communication interface socket family                            done
Virtual machine communication interface                             done
Virtual machine monitor                                             done
Blocking file system                                                done
make: Entering directory '/tmp/modconfig-sQDoPN/vmmon-only'
Using kernel build system.
/usr/bin/make -C /lib/modules/4.2.0-16-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-headers-4.2.0-16-generic'
CC [M]  /tmp/modconfig-sQDoPN/vmmon-only/linux/driver.o
CC [M]  /tmp/modconfig-sQDoPN/vmmon-only/linux/hostif.o
CC [M]  /tmp/modconfig-sQDoPN/vmmon-only/linux/driverLog.o
CC [M]  /tmp/modconfig-sQDoPN/vmmon-only/common/memtrack.o
CC [M]  /tmp/modconfig-sQDoPN/vmmon-only/common/apic.o
CC [M]  /tmp/modconfig-sQDoPN/vmmon-only/common/vmx86.o
CC [M]  /tmp/modconfig-sQDoPN/vmmon-only/common/cpuid.o
/tmp/modconfig-sQDoPN/vmmon-only/linux/driver.c:1332:1: warning: always_inline function might not be inlina
ble [-Wattributes]
LinuxDriverSyncReadTSCs(uint64 *delta) // OUT: TSC max - TSC min
^
CC [M]  /tmp/modconfig-sQDoPN/vmmon-only/common/task.o
/tmp/modconfig-sQDoPN/vmmon-only/linux/driver.c: In function     ‘LinuxDriver_Ioctl’:
/tmp/modconfig-sQDoPN/vmmon-only/linux/driver.c:2054:1: warning: the  frame size of 1184 bytes is larger tha
n 1024 bytes [-Wframe-larger-than=]

}
^
CC [M]  /tmp/modconfig-sQDoPN/vmmon-only/common/comport.o
CC [M]  /tmp/modconfig-sQDoPN/vmmon-only/common/hashFunc.o
CC [M]  /tmp/modconfig-sQDoPN/vmmon-only/common/phystrack.o
CC [M]  /tmp/modconfig-sQDoPN/vmmon-only/vmcore/moduleloop.o
LD [M]  /tmp/modconfig-sQDoPN/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC      /tmp/modconfig-sQDoPN/vmmon-only/vmmon.mod.o
LD [M]  /tmp/modconfig-sQDoPN/vmmon-only/vmmon.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.2.0-16-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-sQDoPN/vmmon-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-sQDoPN/vmmon-only'
make: Entering directory '/tmp/modconfig-sQDoPN/vmnet-only'
Using kernel build system.
/usr/bin/make -C /lib/modules/4.2.0-16-generic/build/include/..     SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-headers-4.2.0-16-generic'
CC [M]  /tmp/modconfig-sQDoPN/vmnet-only/driver.o
CC [M]  /tmp/modconfig-sQDoPN/vmnet-only/hub.o
CC [M]  /tmp/modconfig-sQDoPN/vmnet-only/userif.o
CC [M]  /tmp/modconfig-sQDoPN/vmnet-only/netif.o
In file included from include/linux/pci.h:35:0,
             from /tmp/modconfig-sQDoPN/vmnet-only/compat_netdevice.h:27,
             from /tmp/modconfig-sQDoPN/vmnet-only/netif.c:43:
include/linux/pci_ids.h:2252:0: warning: "PCI_VENDOR_ID_VMWARE" redefined
#define PCI_VENDOR_ID_VMWARE  0x15ad
^
In file included from /tmp/modconfig-sQDoPN/vmnet-only/net.h:38:0,
             from /tmp/modconfig-sQDoPN/vmnet-only/vnetInt.h:26,
             from /tmp/modconfig-sQDoPN/vmnet-only/netif.c:42:
/tmp/modconfig-sQDoPN/vmnet-only/vm_device_version.h:56:0: note: this is the location of the previous definition
#define PCI_VENDOR_ID_VMWARE                    0x15AD
^
CC [M]  /tmp/modconfig-sQDoPN/vmnet-only/bridge.o
CC [M]  /tmp/modconfig-sQDoPN/vmnet-only/procfs.o
CC [M]  /tmp/modconfig-sQDoPN/vmnet-only/smac_compat.o
CC [M]  /tmp/modconfig-sQDoPN/vmnet-only/smac.o
In file included from /tmp/modconfig-sQDoPN/vmnet-only/net.h:38:0,
             from /tmp/modconfig-sQDoPN/vmnet-only/vnetInt.h:26,
             from /tmp/modconfig-sQDoPN/vmnet-only/bridge.c:52:
/tmp/modconfig-sQDoPN/vmnet-only/vm_device_version.h:56:0: warning:   "PCI_VENDOR_ID_VMWARE" redefined
#define PCI_VENDOR_ID_VMWARE                    0x15AD
^
In file included from include/linux/pci.h:35:0,
             from /tmp/modconfig-sQDoPN/vmnet-only/compat_netdevice.h:27,
             from /tmp/modconfig-sQDoPN/vmnet-only/bridge.c:51:
include/linux/pci_ids.h:2252:0: note: this is the location of the previous definition
#define PCI_VENDOR_ID_VMWARE  0x15ad
^
In file included from /tmp/modconfig-sQDoPN/vmnet-only/bridge.c:50:0:
/tmp/modconfig-sQDoPN/vmnet-only/bridge.c: In function ‘VNetBridgeUp’:
/tmp/modconfig-sQDoPN/vmnet-only/vmnetInt.h:81:40: error: too few arguments to function ‘sk_alloc’
#   define compat_sk_alloc(_bri, _pri) sk_alloc(&init_net, \
                                    ^
/tmp/modconfig-sQDoPN/vmnet-only/bridge.c:952:17: note: in expansion of macro ‘compat_sk_alloc’
bridge->sk = compat_sk_alloc(bridge, GFP_ATOMIC);
In file included from /tmp/modconfig-sQDoPN/vmnet-only/compat_sock.h:23:0,
             from /tmp/modconfig-sQDoPN/vmnet-only/bridge.c:35:
include/net/sock.h:1515:14: note: declared here
struct sock *sk_alloc(struct net *net, int family, gfp_t priority,
          ^
scripts/Makefile.build:258: recipe for target '/tmp/modconfig-    sQDoPN/vmnet-only/bridge.o' failed
make[2]: *** [/tmp/modconfig-sQDoPN/vmnet-only/bridge.o] Error 1
make[2]: *** Waiting for unfinished jobs....
Makefile:1398: recipe for target '_module_/tmp/modconfig-sQDoPN/vmnet-only' failed
make[1]: *** [_module_/tmp/modconfig-sQDoPN/vmnet-only] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-4.2.0-16-generic'
Makefile:120: recipe for target 'vmnet.ko' failed
make: *** [vmnet.ko] Error 2
make: Leaving directory '/tmp/modconfig-sQDoPN/vmnet-only'
Unable to install all modules.  See log for details.

答案1

（K）Ubuntu 15.10 带有内核 4.2.0-17 和 VMPlayer 7.1.2：

  1. 打开一个终端，例如 Konsole
  2. cd /usr/lib/vmware/modules/source
  3. sudo tar -xf vmnet.tar
  4. 使用您最喜欢的文本编辑器，例如 joe，来编辑 vmnetInt.h：

sudo joe vmnet-only/vmnetInt.h

  1. 在第 82 行，添加尾随“,1”，就像在第 84 行一样

    老的：PF_NETLINK, _pri, &vmnet_proto)

    新的：PF_NETLINK, _pri, &vmnet_proto, 1)

  2. 保存更改并将其添加回 tar：

sudo tar -uf vmnet.tar vmnet-only/vmnetInt.h

  1. 再次运行 vmplayer，现在应该可以构建了

sudo vmplayer

答案2

这是我所做的并且对我有用：

echo /usr/lib/vmware/lib/libglibmm-2.4.so.1 | sudo tee -a /etc/ld.so.conf.d/LD_LIBRARY_PATH.conf

然后运行：

sudo ldconfig

所以它会坚持下去。

我手动修改了我的文件以使其适合我，但在 VMware 社区论坛中找到了更简单的方法，可以在此处分享：Debian Linux 主机上的 Workstation 12 无法启动，没有 GUI，也没有错误消息。

希望它能有所帮助，因为它帮助了我；-)

此后，您应该仍然可以在 Unity 栏中使用您的图标，或者从终端启动它：

vmware

答案3

我尝试对我的 Ubuntu 15.10 执行以下操作我的规格是：

$ uname -a
Linux Shan-Ubuntu 4.2.0-19-generic #23-Ubuntu SMP Wed Nov 11 11:39:30 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

我首先使用以下命令删除了之前安装的 VMWare Player：

sudo vmware-installer -u vmware-player
sudo vmware-installer -u vmware-player

然后我从网站上重新安装了它VMWare 网站 因为我遇到了一个问题，所以canberra-gtk-module我使用了：

sudo apt-get install libcanberra-gtk*

下载完成后，在终端运行：

vmplayer

使用可以完全忽略的 Gtk-Errors，VMplayer 可以完全启动。

希望这对 Shan 有帮助

答案4

我遇到了同样的问题，建议的方法都无济于事。然后我卸载了 vmware player，下载并安装了 12.0.1 版本，允许它更新到 12.1.0。现在它运行得很好。

相关内容