VMware Player cannot compile to use new kernel

Bug #829842 reported by David Clayton
2
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

When -34-generic kernel is installed, VMware Player requires recompilation to use new kernel and process stalls at initial "Shutting down services" step.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-34-generic 2.6.32-34.74
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-33.72-generic 2.6.32.41+drm33.18
Uname: Linux 2.6.32-33-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: dc 3293 F.... pulseaudio
 /dev/snd/pcmC1D3p: dc 3293 F...m pulseaudio
 /dev/snd/controlC0: dc 3293 F.... pulseaudio
 /dev/snd/pcmC0D0p: dc 3293 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16'
   Mixer name : 'Realtek ALC889A'
   Components : 'HDA:10ec0885,1458a002,00100101'
   Controls : 40
   Simple ctrls : 22
Card1.Amixer.info:
 Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfdffc000 irq 19'
   Mixer name : 'ATI RS690/780 HDMI'
   Components : 'HDA:1002791a,00791a00,00100000'
   Controls : 4
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
CheckboxSubmission: 212f016c580cd6ab8528ceeed43cfd4f
CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2
Date: Sat Aug 20 10:16:55 2011
HibernationDevice: RESUME=UUID=70cbc844-7c52-4ab4-a316-65a5c80d9eb5
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100308)
MachineType: Gigabyte Technology Co., Ltd. GA-MA78GM-S2HP
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-33-generic root=UUID=adaf9c80-1d4e-40d8-a7f6-171f6523c8e1 ro quiet splash nomodeset video=uvesafb:mode_option=1400x1050-24,mtrr=3,scroll=ywrap
ProcEnviron:
 LANGUAGE=en_AU:en
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.10
RfKill:

SourcePackage: linux
dmi.bios.date: 07/14/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F6d
dmi.board.name: GA-MA78GM-S2HP
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6d:bd07/14/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA78GM-S2HP:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA78GM-S2HP:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA78GM-S2HP
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
David Clayton (dcstar) wrote :
Revision history for this message
David Clayton (dcstar) wrote :

As you can see from the collected data, I had to boot from my -33 kernel to get a reliable system to use. The initial -34 kernel even stopped my System Monitor from functioning, the recent update to the -34 kernel that I just installed fixed that issue but the VMware Player issue remains.

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
David Clayton (dcstar) wrote :
Download full text (5.0 KiB)

Still not fixed on version -34.76 installed today.

Running manual VMware update command in root shell provides the following:
------------
'/usr/bin/vmware-modconfig' --icon='vmware-player' --appname='VMware' --gcc='/usr/bin/gcc' --headers='/lib/modules/2.6.32-34-generic/build/include' --gcc-ignore-minor
Logging to /tmp/vmware-root/setup-5166.log
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
Stopping VMware services:
   VMware USB Arbitrator done
---------
Then it hangs with the usual VMware upgrade pop-up at "Stopping Services". The log file shows this after I Ctrl/C the job:

Sep 01 08:59:46.012: app-139981493757696| Log for VMware Workstation pid=5166 version=7.1.4 build=build-385536 option=Release
Sep 01 08:59:46.012: app-139981493757696| The process is 64-bit.
Sep 01 08:59:46.012: app-139981493757696| Host codepage=UTF-8 encoding=UTF-8
Sep 01 08:59:46.012: app-139981493757696| Logging to /tmp/vmware-root/setup-5166.log
Sep 01 08:59:46.114: app-139981493757696| modconf query interface initialized
Sep 01 08:59:46.115: app-139981493757696| modconf library initialized
Sep 01 08:59:46.195: app-139981493757696| Your GCC version: 4.4
Sep 01 08:59:46.212: app-139981493757696| Your GCC version: 4.4
Sep 01 08:59:46.249: app-139981493757696| Your GCC version: 4.4
Sep 01 08:59:46.294: app-139981493757696| Your GCC version: 4.4
Sep 01 08:59:46.345: app-139981493757696| Your GCC version: 4.4
Sep 01 08:59:46.457: app-139981493757696| Trying to find a suitable PBM set for kernel 2.6.32-34-generic.
Sep 01 08:59:46.460: app-139981493757696| Trying to find a suitable PBM set for kernel 2.6.32-34-generic.
Sep 01 08:59:46.463: app-139981493757696| Trying to find a suitable PBM set for kernel 2.6.32-34-generic.
Sep 01 08:59:46.464: app-139981493757696| Trying to find a suitable PBM set for kernel 2.6.32-34-generic.
Sep 01 08:59:46.466: app-139981493757696| ...

Read more...

Revision history for this message
David Clayton (dcstar) wrote :

Still not fixed on version 2.6.32-34.77 installed today.

Revision history for this message
David Clayton (dcstar) wrote :

Ok, some more info.

I found that I could not uninstall VMWare Player in my old 32-33 kernel today (I was installing Workstation 8 so I could also get Player 4). I also could not unload the running modules in this kernel which leads me to believe that the bug was introduced before the -34 kernel.

I was able to manually remove the relevant VMWare files and then successfully install Workstation 8/Player 4 and Player 4 runs ok with the -34 kernel.

I will have to wait for a new kernel release to see if Player 4 will compile with the new headers, but I'm not sure that this bug is now attached to the right kernel version.

Revision history for this message
David Clayton (dcstar) wrote :

I have now done a fresh install of Ubuntu 10.04.3 64-bit desktop and the VMWare stuff works as normal.

Something has changed in the environment of my original system - either through updates from the time of the original install - or in its configuration that prevents VMWare services from being stopped but it is not down to this kernel release.

Since this seems to affect another user then it seems that it is not related to just me, but it may be very difficult to find out what is the root cause.

This bug report should be closed with the appropriate reason.

Revision history for this message
David Clayton (dcstar) wrote :

Ok, found the problem - it is the cgroup-bin & libcgroup1 components. Uninstalling them resolves it:

https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/858102

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.