vmwgfx does not work with kvm vmware vga

[Michal Suchanek]

vmwgfx driver fails to initialize inside kvm.

tried: kvm -m 2048 -vga vmware -cdrom RebeccaBlackLinux.iso (Ubuntu based, any Ubuntu live CD would do)

Apport data collected with qantal alpha live CD (somewhat older kernel).

The error is shjown in CurrentDmesg.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1037606/+attachment/3265235/+files/CurrentDmesg.txt

---
ApportVersion: 2.4-0ubuntu8
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
CasperVersion: 1.320
DistroRelease: Ubuntu 12.10
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
MachineType: Bochs Bochs
Package: linux (not installed)
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-6-generic N/A
 linux-backports-modules-3.5.0-6-generic N/A
 linux-firmware 1.85
RfKill:

Tags: quantal
Uname: Linux 3.5.0-6-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 01/01/2007
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs
---
ApportVersion: 2.0.1-0ubuntu12
Architecture: i386
DistroRelease: Ubuntu 12.04
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Tags: precise running-unity
Uname: Linux 3.6.0-030600rc3-generic i686
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: Upgraded to precise on 2012-08-30 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1037606

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Michal Suchanek (hramrach)]

There is screenshot of the error message.

The message reads

*ERROR* Hardware has no pichlock

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1037606

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Michal Suchanek (hramrach)]

Since the error prevents graphical environment from starting and apport-collect requires a graphical browser to post the data it collects it is not useful to run.

[Michal Suchanek (hramrach)]

apport information

[Michal Suchanek (hramrach)]

apport information

[Michal Suchanek (hramrach)]

apport information

[Michal Suchanek (hramrach)]

apport information

[Michal Suchanek (hramrach)]

apport information

[Michal Suchanek (hramrach)]

apport information

[Michal Suchanek (hramrach)]

apport information

[Michal Suchanek (hramrach)]

apport information

[Michal Suchanek (hramrach)]

apport information

[Michal Suchanek (hramrach)]

apport information

[Michal Suchanek (hramrach)]

apport information

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.6 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. Please only remove that one tag and leave the other tags. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-rc3-quantal/

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[Andrew Engelbrecht (leaf-node)]

i am also having this problem on amd64 debian sid, using:

    qemu 1.7.0+dfsg-5

on the guest system, i'm also running sid:

    linux-image-amd64 3.13+56
    xserver-xorg-video-vmware 1:13.0.1-3+b1

i added vmwgfx to /etc/modules, trying to follow the directions here (aside from using VMware Play, etc.):

    http://www.x.org/wiki/vmware/vmware3D/

however, that only gives me the bug sooner than Michael.

[ 1.590515] [drm] Initialized drm 1.1.0 20060810
[ 1.598096] [drm] DMA map mode: Using physical TTM page addresses.
[ 1.598131] [drm] Capabilities:
[ 1.598132] [drm] Rect copy.
[ 1.598133] [drm] Cursor.
[ 1.598133] [drm] Cursor bypass.
[ 1.598134] [drm] Cursor bypass 2.
[ 1.598135] [drm] VRAM at 0xfd000000 size is 16384 kiB
[ 1.598136] [drm] MMIO at 0xfe000000 size is 64 kiB
[ 1.598138] [drm] global init.
[ 1.601643] [TTM] Zone kernel: Available graphics memory: 512610 kiB
[ 1.601646] [TTM] Initializing pool allocator
[ 1.601649] [TTM] Initializing DMA pool allocator
[ 1.601657] [drm] No GMR memory available. Graphics memory resources are very limited.
[ 1.601718] [drm:vmw_driver_load] *ERROR* Hardware has no pitchlock
[ 1.601971] [TTM] Finalizing pool allocator
[ 1.601975] [TTM] Finalizing DMA pool allocator
[ 1.602006] [TTM] Zone kernel: Used memory at exit: 0 kiB
[ 1.602724] vmwgfx: probe of 0000:00:02.0 failed with error -38

[Andrew Engelbrecht (leaf-node)]

the bug on the kernel bug tracker is marked as "resolved obsolete", not "confirmed".

[Thomas Huth (th-huth)]

https://bugzilla.kernel.org/show_bug.cgi?id=46711 is marked as WILLNOTFIX, so I'm closing the QEMU bug here, too.

[Michal Suchanek (hramrach)]

The kernel bugzilla response is:

The vmwgfx kernel module does not support devices without the pitchlock capability. Sorry. In that case you need to use the xf86-video-vmware driver standalone without kernel modesetting.

So presumably this is some capability to be added to the qemu device

[Michal Suchanek (hramrach)]

Also http://airlied.livejournal.com/69291.html

[Thomas Huth (th-huth)]

OK, got your point ... but AFAIK the vmware display device in QEMU is pretty much unmaintened anyway, so unless someone steps up and takes care of this device, I think the WONT-FIX status is appropriate for this bug.