graphic: 0.238
semantic: 0.223
other: 0.163
device: 0.092
files: 0.088
vnc: 0.044
PID: 0.042
performance: 0.024
permissions: 0.023
debug: 0.019
socket: 0.014
network: 0.013
boot: 0.011
KVM: 0.007
debug: 0.195
graphic: 0.143
other: 0.118
files: 0.111
vnc: 0.084
device: 0.059
performance: 0.055
semantic: 0.050
PID: 0.046
network: 0.044
socket: 0.041
KVM: 0.019
boot: 0.019
permissions: 0.016

Desktop background messed up when running Raring in a QEMU-based virtual machine

Screenshot attached.

Problem occurs only when choosing the default cirrus graphics card. The other graphics cards do not show this problem but are very unstable.

The screenshot is of the whole desktop with a Virtual Machine Manager window containing the desktop of the VM. You see that its actual background is messed up and also the background images which you can choose when right-clicking the background and choosing "Change Desktop Background".



It does not matter whether the host machine is Quantal or Raring, currently my host machine is Raring, so I can easily test Raring packages for the fix of this bug.

Thanks I'll try to reproduce later tonight.

For additional info see the files attached to bug 1157066, they are for the same virtual machine.

I see this behavior over vnc as well.  The desktop is rendered correctly using spice.  You can use that by adding eg

   -vga qxl -spice port=5990,disable-ticketing

and connect using

   spicy -h localhost -p 5990

I also don't get this with the vmware vga driver.  The background is fine for that with both sdl and vnc.

(lowering priority since there are more than one workarounds)

Sorry, I had misread the original description and thought you said the other graphics cards *also* showed this problem :)

Thanks again for submitting this bug.  I'll test against upstream qemu to see if we can report this there.

Also reproduced with git://git.qemu.org/qemu.git (using vga -cirrus)

Triaging old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?

This did never occur again for me. So this can get closed.