| Summary: | RHEL7.0 guest can not shutdown via system_powerdown in qmp monitor | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | zhonglinzhang <zhzhang> |
| Component: | qemu-kvm | Assignee: | Hai Huang <hhuang> |
| Status: | CLOSED DUPLICATE | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.0 | CC: | acathrow, bdas, chayang, hhuang, juzhang, michen, sluo, virt-maint, xfu |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-05-14 13:24:07 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: | |
|
Description
zhonglinzhang
2013-12-04 06:31:15 UTC
What is the device being assigned? Does the shutdown problem only happen with that VF or is it reproducible with other VFs (82576/82599)? Does this problem only happen on q35 guests? Q35: Retest this issue with 3.10.0-54.el7.x86_64 kernel guest, After I finished to install the guest without PF assigned, First Inside guest with power can succeed to shutdown the guest. But second in qmp monitor，After system_powerdown command, the guest stop at login screen, Inside guest with poweroff, failed to shutdown the guest. Maybe regardless of PF device assigned. the command line: /usr/libexec/qemu-kvm -M q35 -cpu SandyBridge -enable-kvm -m 4G \ -smp 1,sockets=1,cores=2,threads=1 -name test -rtc base=utc,clock=host,driftfix=slew -k en-us -boot menu=on -vga qxl \ -spice disable-ticketing,port=5931 -monitor stdio -qmp tcp:0:4444,server,nowait -device ioh3420,bus=pcie.0,id=root.0 \ -device x3130-upstream,bus=root.0,id=upstream -device xio3130-downstream,bus=upstream,id=downstream0,chassis=1 -drive file=/home/RHEL7.0-64.raw,if=none,id=drive-system-disk,media=disk,format=raw,aio=native,werror=stop,rerror=stop \ -device virtio-blk-pci,bus=downstream0,drive=drive-system-disk,id=system-disk,bootindex=1 -device xio3130-downstream,bus=upstream,id=downstream2,chassis=2 \ -device virtio-net-pci,netdev=hostnet0,id=net0,bus=downstream2,mac=52:54:00:13:10:20 -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup \ -serial unix:/tmp/ttyS0,server,nowait Actual Result: Hang at this stage: [root@unused ~]# [ 165.847127] pciehp 0000:00:02.0:pcie04: Device 0000:01:00.0 already exists at 0000:01:00, cannot hot-add [ 165.847129] pciehp 0000:00:02.0:pcie04: Cannot add device at 0000:01:00 [ 170.949180] pciehp 0000:02:00.0:pcie24: Device 0000:03:00.0 already exists at 0000:03:00, cannot hot-add [ 170.949182] pciehp 0000:02:00.0:pcie24: Cannot add device at 0000:03:00 [ 170.949226] pciehp 0000:02:01.0:pcie24: Device 0000:04:00.0 already exists at 0000:04:00, cannot hot-add [ 170.949227] pciehp 0000:02:01.0:pcie24: Cannot add device at 0000:04:00 [ OK ] Stopped LSB: Start the ipr init daemon. ................................. Cannot finalize remaining file systems and devices, giving up. dracut Warning: Killing all remaining processes Powering off. [ 208.919331] Power down. pc-i440fx-rhel7.0.0: Hit the same result, but hang without any information in nc command monitor. (In reply to Alex Williamson from comment #2) > What is the device being assigned? > > Does the shutdown problem only happen with that VF or is it reproducible > with other VFs (82576/82599)? without VF can not shutdown the guest. (In reply to zhonglinzhang from comment #5) > without VF can not shutdown the guest. Are you saying this happens even without device assignment of any kind? (In reply to Alex Williamson from comment #6) > (In reply to zhonglinzhang from comment #5) > > without VF can not shutdown the guest. > > Are you saying this happens even without device assignment of any kind? Yes, system_powerdown in qmp monitor, stop at login screen. Inside guest power off after login in guest, then hang. Changing title and re-assigning back to default assignee since this has nothing to do with device assignment. (In reply to Alex Williamson from comment #8) > Changing title and re-assigning back to default assignee since this has > nothing to do with device assignment. This bug maybe duplicate to bug 1040307 - Qemu monitor "system_powerdown" command fail to power down guest Best Regards, sluo Hi Sluo, Can you do some investigation and test and update comment13? Best Regards, Junyi (In reply to juzhang from comment #14) > Hi Sluo, > > Can you do some investigation and test and update comment13? > > Best Regards, > Junyi Retried this issue with the same command as comment #0 and comment #3 which just same results with bug 1040307. I think we can close it duplicate to bug 1040307. host info: # uname -r && rpm -q qemu-kvm 3.10.0-123.el7.x86_64 qemu-kvm-1.5.3-60.el7.x86_64 guest info: # uname -r 3.10.0-123.el7.x86_64 Best Regards, sluo *** This bug has been marked as a duplicate of bug 1040307 *** |