Bug 1017955
Summary: | qemu: display during grub prompt is garbled | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Zbigniew Jędrzejewski-Szmek <zbyszek> |
Component: | spice-gtk | Assignee: | Marc-Andre Lureau <marcandre.lureau> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 20 | CC: | alevy, amit.shah, awilliam, berrange, cfergeau, crobinso, dwmw2, hdegoede, itamar, kraxel, marcandre.lureau, mfabian, pbonzini, rjones, sandmann, scottt.tw, uril, virt-maint, yhalperi, zbyszek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | spice-gtk-0.21-5.fc20 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-11-24 03:26:59 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Attachments: |
Description
Zbigniew Jędrzejewski-Szmek
2013-10-10 20:38:37 UTC
Created attachment 818077 [details] Busted screenshot Here's mine, safe reproducer as Comment #0. The grey in that image is the grey from F20 gdm: not sure if this is qemu, guest, spice, or client issue. Ccing some folks that might be able to answer (In reply to Cole Robinson from comment #1) > Created attachment 818077 [details] > Busted screenshot > > Here's mine, safe reproducer as Comment #0. The grey in that image is the > grey from F20 gdm: not sure if this is qemu, guest, spice, or client issue. > Ccing some folks that might be able to answer Actually CCing Looks pretty much like the video memory wasn't cleared after setting the video mode. I'll bet on a guest bug. Does F19 show this too? How does grub2.conf (of the installed guest) look like? (In reply to Gerd Hoffmann from comment #3) > Looks pretty much like the video memory wasn't cleared after setting the > video mode. I'll bet on a guest bug. Yeah, the question is who should clear it. > Does F19 show this too? Yes, seems to be identical (screenshot attached). > How does grub2.conf (of the installed guest) look like? I didn't do any configuration whatsoever, so this is standard from anaconda. Attached. Created attachment 819196 [details]
garbled boot screen with F19 guest after forced reset
Created attachment 819197 [details]
grub2 configuration from F20 guest
Hmm, grub2 runs in *text mode* by default.(In reply to Zbigniew Jędrzejewski-Szmek from comment #4) > (In reply to Gerd Hoffmann from comment #3) > > Looks pretty much like the video memory wasn't cleared after setting the > > video mode. I'll bet on a guest bug. > Yeah, the question is who should clear it. Hmm, grub2 uses no graphic mode by default (cfg file confirms this), so it is *text mode* looking this way. Strange. And it makes a guest bug rather unlikely. > > Does F19 show this too? > Yes, seems to be identical (screenshot attached). Tried F19 guest, doesn't reproduce for me :-( Havn't a F20 host at hand, compiled qemu 1.6.0 from git. How did you create the snapshot? Using the gnome snapshot utility? Or using virt-manager/guest-window/virtualmachine/take-snapshot? Any change when using vnc instead of spice? Any change when using stdvga instead of qxl? (In reply to Gerd Hoffmann from comment #7) > Hmm, grub2 runs in *text mode* by default.(In reply to Zbigniew > Jędrzejewski-Szmek from comment #4) > > (In reply to Gerd Hoffmann from comment #3) > > > Looks pretty much like the video memory wasn't cleared after setting the > > > video mode. I'll bet on a guest bug. > > Yeah, the question is who should clear it. > > Hmm, grub2 uses no graphic mode by default (cfg file confirms this), > so it is *text mode* looking this way. Strange. And it makes a guest > bug rather unlikely. > > > > Does F19 show this too? > > Yes, seems to be identical (screenshot attached). > > Tried F19 guest, doesn't reproduce for me :-( > Havn't a F20 host at hand, compiled qemu 1.6.0 from git. > > How did you create the snapshot? Using the gnome snapshot utility? Or > using virt-manager/guest-window/virtualmachine/take-snapshot? The first one, using gimp. The second one from guest-window/take-snapshot. > Any change when using vnc instead of spice? With "Display Spice" removed, and "Display VNC" added, I cannot reproduce this (5 or 6 tries). (Before I wrote that reproducibility is 30%, but actually, at least now, it is very close to 100%. In some cases there's just a bit of color noise in one of the corners, but it's clear that there's something random. With VNC, the grub prompt is always clean black.) > Any change when using stdvga instead of qxl? With "Video QXL" changed to "Video VGA, 9MB", and display back at "Display Spice", the corruption seems to be less visible but it's there, often just in the corner, but sometimes full-screen. > > How did you create the snapshot? Using the gnome snapshot utility? Or
> > using virt-manager/guest-window/virtualmachine/take-snapshot?
> The first one, using gimp. The second one from guest-window/take-snapshot.
Cole? How is take-screenshot implemented? Write out window content? Or go through libvirt and ask qemu to write out a screendump that way?
> > Any change when using vnc instead of spice?
> With "Display Spice" removed, and "Display VNC" added, I cannot reproduce
> this (5 or 6 tries).
>
> (Before I wrote that reproducibility is 30%, but actually, at least now, it
> is very close to 100%. In some cases there's just a bit of color noise in
> one of the corners, but it's clear that there's something random. With VNC,
> the grub prompt is always clean black.)
>
> > Any change when using stdvga instead of qxl?
> With "Video QXL" changed to "Video VGA, 9MB", and display back at "Display
> Spice", the corruption seems to be less visible but it's there, often just
> in the corner, but sometimes full-screen.
Thanks. That strongly hints the problem is somewhere in spice.
What happens if you close and re-open the guest window while grub2 is running? Corruption still visible after reopening?
(In reply to Gerd Hoffmann from comment #9) > > > How did you create the snapshot? Using the gnome snapshot utility? Or > > > using virt-manager/guest-window/virtualmachine/take-snapshot? > > The first one, using gimp. The second one from guest-window/take-snapshot. > > Cole? How is take-screenshot implemented? Write out window content? Or go > through libvirt and ask qemu to write out a screendump that way? It's not through qemu, just grabbing the window content from gtk. I can confirm at least that my screenshot matched what I was seeing on the screen at the time. (In reply to Gerd Hoffmann from comment #10) > What happens if you close and re-open the guest window while grub2 is > running? Corruption still visible after reopening? Nope, nice and clean in the reopened window. (In reply to Zbigniew Jędrzejewski-Szmek from comment #12) > (In reply to Gerd Hoffmann from comment #10) > > What happens if you close and re-open the guest window while grub2 is > > running? Corruption still visible after reopening? > Nope, nice and clean in the reopened window. So it is a spice client issue most likely. Reassigning to spice-gtk. this is probably fixed by http://cgit.freedesktop.org/spice/spice-gtk/commit/?id=32b123f44fc79eaad388d6be09f103457f35d734 Could you try the git version? thanks I verified that the issue is fixed using spice-gtk git, thanks Marc-Andre ! *** Bug 1029390 has been marked as a duplicate of this bug. *** *** Bug 1031232 has been marked as a duplicate of this bug. *** spice-gtk-0.21-5.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/spice-gtk-0.21-5.fc20 Package spice-gtk-0.21-5.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing spice-gtk-0.21-5.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-21630/spice-gtk-0.21-5.fc20 then log in and leave karma (feedback). spice-gtk-0.21-5.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. |