VMWare graphics driver regression

[Daniel Guerrero]

When running under VMWare (tested VMWare player 6.0.2) the display does not resize correctly. Once the screen width reaches 800 pixels wide it starts to show the same contents again.

The attached screenshot shows the problem.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-30-generic 3.13.0-30.55
ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: XFCE
Date: Wed Jul 9 17:39:17 2014
HibernationDevice: RESUME=UUID=d77eb158-ad9b-4e8f-a427-81d60dcb8332
InstallationDate: Installed on 2014-04-22 (78 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
IwConfig:
 eth0 no wireless extensions.

 eth1 no wireless extensions.

 lo no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=95d13c34-3d0a-454c-8815-aa9157e1c38f ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-30-generic N/A
 linux-backports-modules-3.13.0-30-generic N/A
 linux-firmware 1.127.4
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/31/2013
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Daniel Guerrero (dguerrero)]

The regression seems to be caused by this commit: 2a4faabafcd8a1911d1dc7ae5699f2ad1103422e
I have just recompiled the kernel with this commit reverted, and now the screen displays properly again.

This patch was included also in other kernels (Saucy and Precise for sure).

[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.16 kernel[0].

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.16-rc4-utopic/

[Daniel Guerrero (dguerrero)]

The bug exists in mainline too.

[Kamal Mostafa (kamalmostafa)]

I'm unable to reproduce this. With either Unity or XFCE desktop, resizing the VMWare Player window works okay for me. I'm using the same 3.13.0-30.55 kernel (on both host and guest), but my VMware Player is newer: "6.0.3 build-1895310".

Daniel, please update your VMWare Player to that version and check whether the problem persists.

That said, I notice this commit, recently added to mainline, which modifies the patch you identified as the problem (2a4faaba in trusty):

  (mainline) 4e57808 drm/vmwgfx: Fix incorrect write to read-only register v2:
  http://kernel.ubuntu.com/git?p=ubuntu/linux.git;a=commitdiff;h=4e578080

Daniel, can you try applying that (along with the problem 2a4faaba commit)... Does that fix it?

[Daniel Guerrero (dguerrero)]

It happens too with VMWare Player 6.0.3 build-1895310. I have both versions, on different machines, and both exhibit the same behaviour. Both hosts are Windows 7 machines.

The VM was copied from one machine to the other, and was created with VMWare Workstation, not with Player.
My host is a Windows 7 machine.

[Daniel Guerrero (dguerrero)]

Just tried 3.13.0-30.55 with 4e57808 applied and it makes no difference.

[Daniel Guerrero (dguerrero)]

The virtual hardware version of the VM (taken from the .vmx file) is

virtualHW.version = "7"

[Daniel Guerrero (dguerrero)]

According to this: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003746

The latest virtual hardware version is 10, while 7 corresponds to VMWare Workstatio 8.x (the version I used to create the VM).

[Daniel Guerrero (dguerrero)]

Creating a new VM with Player (virtualHW.version = "10") and moving over the old virtual disk makes the problem go away.

Both 3.13.0-30.55 with and without 2a4faabafc reverted work.

[Daniel Guerrero (dguerrero)]

This problem is exactly the same as https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/1328898 and https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1331224

Should it be marked as duplicate?

[Kamal Mostafa (kamalmostafa)]

Thanks for testing all that Daniel. I think we've got the problem identified now: It does revolve around the virtualHW.version specified in the .vmx file (7 versus 10)... I find that if I edit my .vmx and change my virtualHW.version from 10 to 7, then I do see the problem behavior.

Thomas Hellstrom from VMware explains whats happening and provides suggested remedies here:
https://communities.vmware.com/message/2398873#2398873

Daniel, please edit your .vmx and bump up your virtualHW.version from 7 to 10 (that's Thomas's solution "1b"). Does that fix it?

[Daniel Guerrero (dguerrero)]

According to this thread in vmware communities https://communities.vmware.com/thread/481038?start=15&tstart=0 the source of the problem is that there is a clash between the X.org driver and the vmwgfx.

[Joseph Salisbury (jsalisbury)]

This bug was nominated against a series that is no longer supported, ie saucy. The bug task representing the saucy nomination is being closed as Won't Fix.

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

[Rolf Leggewie (r0lf)]

utopic has seen the end of its life and is no longer receiving any updates. Marking the utopic task for this ticket as "Won't Fix".

[Steve Langasek (vorlon)]

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release