diff options
Diffstat (limited to 'results/classifier/118/virtual/1157368')
| -rw-r--r-- | results/classifier/118/virtual/1157368 | 68 |
1 files changed, 68 insertions, 0 deletions
diff --git a/results/classifier/118/virtual/1157368 b/results/classifier/118/virtual/1157368 new file mode 100644 index 000000000..7740f96b0 --- /dev/null +++ b/results/classifier/118/virtual/1157368 @@ -0,0 +1,68 @@ +virtual: 0.903 +graphic: 0.651 +semantic: 0.221 +mistranslation: 0.186 +VMM: 0.159 +device: 0.127 +user-level: 0.100 +files: 0.088 +hypervisor: 0.057 +risc-v: 0.055 +peripherals: 0.045 +x86: 0.030 +performance: 0.028 +architecture: 0.025 +vnc: 0.024 +PID: 0.023 +i386: 0.022 +ppc: 0.017 +permissions: 0.011 +debug: 0.011 +register: 0.006 +boot: 0.006 +network: 0.005 +socket: 0.005 +arm: 0.005 +assembly: 0.003 +TCG: 0.002 +kernel: 0.001 +KVM: 0.001 + +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. + |