Bug 1085686

Summary: Machine type rhel6.1.0 and balloon and uhci cause guest call trace from RHEL6.5 host to RHEL7.0 host
Product: Red Hat Enterprise Linux 7 Reporter: FuXiangChun <xfu>
Component: qemu-kvmAssignee: Virtualization Maintenance <virt-maint>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: acathrow, juzhang, michen, qzhang, virt-maint
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-04-09 07:35:30 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:

Description FuXiangChun 2014-04-09 06:44:28 UTC 
Description of problem:
Boot RHEL7.0 guest with rhel6.1.0 machine type and balloon and uhci device on RHEL6.5 host. Guest show call trace in destination RHEL7.0 host after migrating. 

Version-Release number of selected component (if applicable):
RHEL6.5 host:
2.6.32-452.el6.x86_64
qemu-kvm-0.12.1.2-2.420.el6.x86_64
qemu-kvm-0.12.1.2-2.422.el6.x86_64

RHEL7.0 host:
3.10.0-121.el7.x86_64
qemu-kvm-1.5.3-60.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Boot guest in src RHEL6.5 host
/usr/libexec/qemu-kvm -M rhel6.1.0 -cpu Opteron_G3 -enable-kvm  -m 4096 -smp 4,sockets=2,cores=2,threads=1,maxcpus=160 -k en-us -device virtio-balloon-pci,id=ballooning,bus=pci.0,addr=0x5 -drive file=/dev/sdb,if=none,id=drive-virtio-disk,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop,media=disk,snapshot=off,bus=1,unit=1 -device virtio-blk-pci,scsi=off,drive=drive-virtio-disk,id=virtio-disk,bus=pci.0,addr=0x7,bootindex=1 -device ich9-usb-uhci1,id=usb1,addr=0x11 -device usb-tablet,id=input0 -device usb-mouse,id=input1  -monitor stdio -serial unix:/tmp/monitor,server,nowait -net none -vnc :1

2.Boot guest in des RHEL7.0 host
/usr/libexec/qemu-kvm -M rhel6.1.0 -cpu Opteron_G3 -enable-kvm  -m 4096 -smp 4,sockets=2,cores=2,threads=1,maxcpus=160 -k en-us -device virtio-balloon-pci,id=ballooning,bus=pci.0,addr=0x5 -drive file=/dev/sdb,if=none,id=drive-virtio-disk,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop,media=disk,snapshot=off,bus=1,unit=1 -device virtio-blk-pci,scsi=off,drive=drive-virtio-disk,id=virtio-disk,bus=pci.0,addr=0x7,bootindex=1 -device ich9-usb-uhci1,id=usb1,addr=0x11 -device usb-tablet,id=input0 -device usb-mouse,id=input1  -monitor stdio -serial unix:/tmp/monitor,server,nowait -net none -vnc :1 -incoming tcp:0:5555

3.do migration


Actual results:
[  198.032009] Call Trace:
[  198.032009]  <IRQ>  [<ffffffff815ec0ba>] dump_stack+0x19/0x1b
[  198.032009]  [<ffffffff810f96e2>] __report_bad_irq+0x32/0xd0
[  198.032009]  [<ffffffff810f9b02>] note_interrupt+0x132/0x1f0
[  198.032009]  [<ffffffff810f7221>] handle_irq_event_percpu+0xe1/0x1e0
[  198.032009]  [<ffffffff810f735d>] handle_irq_event+0x3d/0x60
[  198.032009]  [<ffffffff810fa7ba>] handle_fasteoi_irq+0x5a/0x100
[  198.032009]  [<ffffffff81014c3f>] handle_irq+0xbf/0x150
[  198.032009]  [<ffffffff81067247>] ? irq_enter+0x17/0xa0
[  198.032009]  [<ffffffff815fea4f>] do_IRQ+0x4f/0xf0
[  198.032009]  [<ffffffff815f3bad>] common_interrupt+0x6d/0x6d
[  198.032009]  [<ffffffff8106fe8e>] ? update_process_times+0x6e/0x80
[  198.032009]  [<ffffffff81066ff0>] ? __do_softirq+0xa0/0x290
[  198.032009]  [<ffffffff81066f70>] ? __do_softirq+0x20/0x290
[  198.032009]  [<ffffffff810bd9a4>] ? tick_program_event+0x24/0x30
[  198.032009]  [<ffffffff815fe15c>] call_softirq+0x1c/0x30
[  198.032009]  [<ffffffff81014d25>] do_softirq+0x55/0x90
[  198.032009]  [<ffffffff810673e5>] irq_exit+0x115/0x120
[  198.032009]  [<ffffffff815feb35>] smp_apic_timer_interrupt+0x45/0x60
[  198.032009]  [<ffffffff815fd49d>] apic_timer_interrupt+0x6d/0x80
[  198.032009]  <EOI>  [<ffffffff81046346>] ? native_safe_halt+0x6/0x10
[  198.032009]  [<ffffffff8101b39f>] default_idle+0x1f/0xc0
[  198.032009]  [<ffffffff8101bc96>] arch_cpu_idle+0x26/0x30
[  198.032009]  [<ffffffff810b4725>] cpu_startup_entry+0xf5/0x290
[  198.032009]  [<ffffffff815ce027>] rest_init+0x77/0x80
[  198.032009]  [<ffffffff81a18fa7>] start_kernel+0x429/0x44a
[  198.032009]  [<ffffffff81a18987>] ? repair_env_string+0x5c/0x5c
[  198.032009]  [<ffffffff81a18120>] ? early_idt_handlers+0x120/0x120
[  198.032009]  [<ffffffff81a185ee>] x86_64_start_reservations+0x2a/0x2c
[  198.032009]  [<ffffffff81a18742>] x86_64_start_kernel+0x152/0x175
[  198.032009] handlers:
[  198.032009] [<ffffffffa00606d0>] vp_interrupt [virtio_pci]
[  198.032009] Disabling IRQ #10

Expected results:
works well

Additional info:
1. Tested qemu-kvm-0.12.1.2-2.420.el6.x86_64 and qemu-kvm-0.12.1.2-2.422.el6.x86_64,  will hit the same issue,  if <qemu-kvm-0.12.1.2-2.420.el6.x86_64 version, will hit existing bug 1027561. so this is not a regression bug.

2.guest call ctrace, But guest still works.

3.I added multiple devices to qemu-kvm cli. debugging result is balloon and uhci device only cause guest call trace.  I will add full command line and and guest dmesg log to attachment.
Comment 2 FuXiangChun 2014-04-09 07:35:30 UTC 
Open 2 same bzs by accident, close this bz as duplicated to bug 1085701.

*** This bug has been marked as a duplicate of bug 1085701 ***