Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1012928

Summary: QXL RHEl7 guest with GUI can not shutdown (guest-panicked).
Product: Red Hat Enterprise Linux 7 Reporter: Qian Guo <qiguo>
Component: qemu-kvmAssignee: Gerd Hoffmann <kraxel>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: medium    
Version: 7.0CC: acathrow, airlied, hhuang, juzhang, mazhang, michen, mkrcmari, qiguo, rhod, virt-maint
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-27 09:27:04 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:

Comment 2 Gerd Hoffmann 2013-09-30 11:51:49 UTC
Looks like a guest bug on a quick glance.  Hard to tell without more info though.  No luck in reproducing locally so far.

Anything on the guests serial console?

Comment 3 juzhang 2013-10-08 01:21:46 UTC
Hi Qiguo,

Can you reply comment2?

Comment 4 Qian Guo 2013-10-08 03:22:59 UTC
(In reply to Gerd Hoffmann from comment #2)
> Looks like a guest bug on a quick glance.  Hard to tell without more info
> though.  No luck in reproducing locally so far.
> 
> Anything on the guests serial console?

Hi, Gerd

If configured serial-console  in guest kernel line, this issue would disappear, so can not get serial messages.

Thanks

Comment 5 Marian Krcmarik 2013-11-08 19:21:53 UTC
I can reproduce something similar, with qemu-kvm-1.5.3-14.el7 The guest hangs at the edn of shutdown and the process of qemu-kvm is still running, even info status monitor command returns running status. It did crash with older qemu (qemu-kvm-1.5.3-14.el7.x86_64.rpm).
It seems like libvirt did not kill the process but It happens even when running qemu-kvm directly from cli, here is the cli:

/usr/libexec/qemu-kvm -name RHEL7 -machine pc-i440fx-rhel7.0.0,accel=kvm,usb=off -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 61f75cf0-4cba-4b99-999c-46793055935d -no-user-config -nodefaults -rtc base=utc -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x8.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x8 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x8.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x8.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -device usb-ccid,id=ccid0 -chardev spicevmc,id=charsmartcard0,name=smartcard -device ccid-card-passthru,chardev=charsmartcard0,id=smartcard0,bus=ccid0.0 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0 -spice port=5900,addr=127.0.0.1,disable-ticketing,seamless-migration=on -vga qxl -global qxl-vga.ram_size=67108864 -global qxl-vga.vram_size=67108864 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 /home/shadowman/rhel7.img

Comment 6 Marian Krcmarik 2013-11-08 19:26:45 UTC
wrt reproducer, I did not do anything special, installed RHEL7 as all components - client/host/guest from build RHEL-7.0-20131108.n.0.

# rpm -qa | egrep "qemu|seabios|kernel|spice"
libvirt-daemon-driver-qemu-1.1.1-11.el7.x86_64
texlive-l3kernel-svn29409.SVN_4469-27.el7.noarch
qemu-img-1.5.3-17.el7.x86_64
qemu-kvm-1.5.3-17.el7.x86_64
kernel-3.10.0-42.el7.x86_64
abrt-addon-kerneloops-2.1.7-2.el7.x86_64
qemu-guest-agent-1.5.3-17.el7.x86_64
ipxe-roms-qemu-20130517-1.gitc4bce43.el7.noarch
seabios-bin-1.7.2.2-4.el7.noarch
spice-server-0.12.4-3.el7.x86_64
spice-glib-0.20-6.el7.x86_64
spice-vdagent-0.14.0-5.el7.x86_64
qemu-kvm-common-1.5.3-17.el7.x86_64
kernel-3.10.0-44.el7.x86_64
spice-gtk3-0.20-6.el7.x86_64

IT DOES NOT HAPPEN with "-vga std" option

Comment 7 Gerd Hoffmann 2013-12-11 11:20:14 UTC
(In reply to Marian Krcmarik from comment #5)
> I can reproduce something similar, with qemu-kvm-1.5.3-14.el7 The guest
> hangs at the edn of shutdown and the process of qemu-kvm is still running,
> even info status monitor command returns running status. It did crash with
> older qemu (qemu-kvm-1.5.3-14.el7.x86_64.rpm).
> It seems like libvirt did not kill the process but It happens even when
> running qemu-kvm directly from cli, here is the cli:

Hmm, doesn't reproduce either, using exactly the same command line (except for the disk image path).  Using qemu-kvm-1.5.3-20.el7.

Anything special to do in the guest to trigger?  I'm just booting to the login screen, log into gnome, then pick shutdown from the menu.

Comment 8 Gerd Hoffmann 2014-01-16 13:56:12 UTC
forgot to set needinfo, see comment #7