Bug 595665
| Summary: | Guest crashed after hot add virtio disk in win7 64bit guest | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Mike Cao <bcao> |
| Component: | qemu-kvm | Assignee: | Markus Armbruster <armbru> |
| Status: | CLOSED NOTABUG | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.0 | CC: | lihuang, llim, michen, ndai, tburke, virt-maint |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-07-08 17:10:59 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: | |||
|
Description
Mike Cao
2010-05-25 10:32:08 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. A couple of questions: Just to make sure: it doesn't happen with a Linux guest, does it? Does the problem exist with device_add instead of pci_add as well? To test, start qemu with "-drive if=none,file=/Images/test3.qcow2,id=foo", then give monitor command "device_add virtio-blk-pci" Could you capture a stack backtrace? (In reply to comment #3) > A couple of questions: > > Just to make sure: it doesn't happen with a Linux guest, does it? yup,I test with RHEL5 ,it will NOT trigger this issue. > Does the problem exist with device_add instead of pci_add as well? To test, > start qemu with "-drive if=none,file=/Images/test3.qcow2,id=foo", then give > monitor command "device_add virtio-blk-pci" (qemu)device_add virtio-blk-pci，drive=foo I tried 2 times ,It does NOT trigger this issue. > Could you capture a stack backtrace? (gdb)bt 0x000000366e8329c5 in raise () from /lib64/libc.so.6 #1 0x000000366e8341a5 in abort () from /lib64/libc.so.6 #2 0x000000000040cee8 in hw_error (fmt=<value optimized out>) at /usr/src/debug/qemu-kvm-0.12.1.2/vl.c:355 #3 0x00000000004a013b in register_ioport_write (start=<value optimized out>, length=<value optimized out>, size=6, func=0xffffffffffffffff, opaque=0x7f03efe44710) at ioport.c:170 #4 0x0000000000420248 in virtio_map (pci_dev=0x1882920, region_num=<value optimized out>, addr=65408, size=<value optimized out>, type=<value optimized out>) at /usr/src/debug/qemu-kvm-0.12.1.2/hw/virtio-pci.c:363 #5 0x000000000041840b in pci_update_mappings (d=0x1882920) at /usr/src/debug/qemu-kvm-0.12.1.2/hw/pci.c:1002 #6 0x00000000004209d0 in virtio_write_config (pci_dev=0x1882920, address=4, val=1031, len=2) at /usr/src/debug/qemu-kvm-0.12.1.2/hw/virtio-pci.c:386 #7 0x000000000042a551 in kvm_handle_io (env=0x17c04c0) at /usr/src/debug/qemu-kvm-0.12.1.2/kvm-all.c:538 #8 kvm_run (env=0x17c04c0) at /usr/src/debug/qemu-kvm-0.12.1.2/qemu-kvm.c:969 #9 0x000000000042a5f9 in kvm_cpu_exec (env=<value optimized out>) at /usr/src/debug/qemu-kvm-0.12.1.2/qemu-kvm.c:1652 #10 0x000000000042b21f in kvm_main_loop_cpu (_env=0x17c04c0) at /usr/src/debug/qemu-kvm-0.12.1.2/qemu-kvm.c:1894 #11 ap_main_loop (_env=0x17c04c0) #12 0x000000366f007761 in start_thread () from /lib64/libpthread.so.0 #13 0x000000366e8e14fd in clone () from /lib64/libc.so.6 Additional info : The issue was found in qemu-kvm-0.12.1.2-2.62.el6 pci_add is gone since qemu-kvm-0.12.1.2-2.76.el6 (bug 602590). According to comment#4, device_add is not affected. Therefore, I'm going to close as NOTABUG. Please reopen if you can reproduce it with device_add. |