[maverick] corrupt rendering of glxgears (in kvm guest)

[Dave Gilbert]

Binary package hint: xserver-xorg-video-cirrus

I'm running maverick in a kvm guest under a lucid host (64bit).
If I run glxgears on the guest I get a very corrupt rendering (attached) - note that this is a screenshot taken from within the guest,
so it makes me feel it's more likely (but by no means certain) that it's more likely to be the Xserver guest rather than the qemu-kvm layer. All 2D stuff renders fine, and all 3d stuff is corrupt - since there is no 3d acceleration on the chip it should all be
being done in software on the guest shouldn't it?

The guest is configured with a 'xen' video adapter shows as xen, 9MB ram, Heads: 1 in virt-manager using the local SDL window.

Dave

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-video-cirrus 1:1.3.2-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.34-5.14-generic 2.6.34
Uname: Linux 2.6.34-5-generic x86_64
Architecture: amd64
Date: Sun Jun 13 20:10:36 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: xserver-xorg-video-cirrus

[bugbot (bugbot)]

Hey Dave,

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.