Bug 645279
Summary: | keyboard lost after loadvm then reboot guest | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Shirley Zhou <szhou> |
Component: | kvm | Assignee: | Markus Armbruster <armbru> |
Status: | CLOSED WORKSFORME | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.6 | CC: | ehabkost, gcosta, juzhang, mkenneth, mshao, virt-maint, xfu |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-08-10 12:29:39 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 580946 |
Description
Shirley Zhou
2010-10-21 08:14:02 UTC
This bug can also be reproduced on latest kvm version: kvm-83-224.el5, add qa-ack. Can this bug still be reproduced? Does it bite RHEL-6 as well? This bug can not be reproduced on qemu-kvm-0.12.1.2-2.177.el6.x86_64 and kvm-83-205.el5 host info: # uname -r 2.6.32-178.el6.x86_64(intel platform) # rpm -qa|grep kvm qemu-kvm-0.12.1.2-2.177.el6.x86_64 guest info: rhel5.6(x86_64) tested steps on qemu-kvm-0.12.1.2-2.177.el6.x86_64: 1./usr/libexec/qemu-kvm -m 4G -smp 4 -uuid 7c73a852-c316-4d61-b913-9dde17367a30 -drive file=rhel56.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,drive=drive-virtio-disk0,id=virtio-blk-pci0 -boot c -monitor stdio -spice disable-ticketing,port=5912 -vga qxl 2.(qemu) savevm sn1 3.(qemu) loadvm sn1 4.(qemu) system_reset actual result: keyboard and mouse work well host info: # uname -r 2.6.18-227.el5(AMD platform) # rpm -qa|grep kvm kvm-83-205.el5 guest info: rhel5.6(x86_64) tested steps on kvm-83-205.el5 1.# /usr/libexec/qemu-kvm -M rhel5.6.0 -m 4G -smp 4 -name test-qcow2 -uuid 39a565d2-2032-848d-bda0-de7adb149048 -monitor stdio -boot c -drive file=rhel56.qcow2,if=ide,bus=0,unit=0,boot=on,format=qcow2,werror=stop,cache=writeback -net nic,macaddr=54:52:00:27:cd:13,vlan=0,model=virtio -net tap,vlan=0 -serial pty -parallel none -usb -usbdevice tablet -vnc :1 -k en-us -vga cirrus -balloon virtio char device redirected to /dev/pts/1 QEMU 0.9.1 monitor - type 'help' for more information 2.(qemu) savevm sn1 3.(qemu) loadvm sn1 4.(qemu) system_reset actual result: keyboard and mouse work well This bug can not be reproduced on qemu-kvm-0.12.1.2-2.177.el6.x86_64 and kvm-83-205.el5 host info: # uname -r 2.6.32-178.el6.x86_64(intel platform) # rpm -qa|grep kvm qemu-kvm-0.12.1.2-2.177.el6.x86_64 guest info: rhel5.6(x86_64) tested steps on qemu-kvm-0.12.1.2-2.177.el6.x86_64: 1./usr/libexec/qemu-kvm -m 4G -smp 4 -uuid 7c73a852-c316-4d61-b913-9dde17367a30 -drive file=rhel56.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,drive=drive-virtio-disk0,id=virtio-blk-pci0 -boot c -monitor stdio -spice disable-ticketing,port=5912 -vga qxl 2.(qemu) savevm sn1 3.(qemu) loadvm sn1 4.(qemu) system_reset actual result: keyboard and mouse work well host info: # uname -r 2.6.18-227.el5(AMD platform) # rpm -qa|grep kvm kvm-83-205.el5 guest info: rhel5.6(x86_64) tested steps on kvm-83-205.el5 1.# /usr/libexec/qemu-kvm -M rhel5.6.0 -m 4G -smp 4 -name test-qcow2 -uuid 39a565d2-2032-848d-bda0-de7adb149048 -monitor stdio -boot c -drive file=rhel56.qcow2,if=ide,bus=0,unit=0,boot=on,format=qcow2,werror=stop,cache=writeback -net nic,macaddr=54:52:00:27:cd:13,vlan=0,model=virtio -net tap,vlan=0 -serial pty -parallel none -usb -usbdevice tablet -vnc :1 -k en-us -vga cirrus -balloon virtio char device redirected to /dev/pts/1 QEMU 0.9.1 monitor - type 'help' for more information 2.(qemu) savevm sn1 3.(qemu) loadvm sn1 4.(qemu) system_reset actual result: keyboard and mouse work well Thanks. To sum up, the bug can no longer be reproduced on RHEL-5, but we don't know the exact change that fixed it. It can't be reproduced on RHEL-6, but we don't know whether it was broken before there. |