Bug 869216
| Summary: | host kernel panic while booting a guest with -cpu host,-kvm_pv_eoi | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Chao Yang <chayang> |
| Component: | kernel | Assignee: | Michael S. Tsirkin <mst> |
| Status: | CLOSED DUPLICATE | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.4 | CC: | acathrow, areis, bsarathy, dyasny, gleb, juzhang, michen, mkenneth, qzhang, shuang, virt-maint, xfu |
| Target Milestone: | rc | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-10-31 09:53:17 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: | |||
Retesed with '-M rhel6.4.0 -cpu cpu64-rhel6,-kvm_pv_eoi', not reproducible. CLI: /usr/libexec/qemu-kvm -M rhel6.4.0 -cpu cpu64-rhel6,-kvm_pv_eoi -enable-kvm -m 2048 -smp 2,sockets=2,cores=1,threads=1 -usb -device usb-tablet,id=input0 -netdev tap,id=hostnet0,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,id=virtio-net-pci0,mac=98:3B:CB:2E:91:A9,bus=pci.0,addr=0x5 -vnc :1 -monitor stdio -drive file=/root/rhel6.3.GA.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,werror=stop,rerror=stop,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 Tested 2.6.32-336.el6.x86_64 and 2.6.32-328.el6.x86_64 and 2.6.32-313.el6.x86_64 1.kernel 2.6.32-336.el6.x86_64 and 2.6.32-328.el6.x86_64 Boot guest with "-cpu host", host kernel panic. and get the same call trace information as comment 0 2.kernel 2.6.32-313.el6.x86_64 Boot guest with "-cpu host", host and guest work well. so it is a regression bug. I added regression keyword. and change component to kernel. <gleb> mst, dup of 865380 *** This bug has been marked as a duplicate of bug 865380 *** |
Description of problem: Booting a guest with '-M rhel6.4.0 -cpu host,-kvm_pv_eoi', host got kernel panic during guest booting. Version-Release number of selected component (if applicable): host: qemu-kvm-0.12.1.2-2.330.el6.x86_64 2.6.32-336.el6.x86_64 guest: 2.6.32-335.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: KERNEL: /usr/lib/debug/lib/modules/2.6.32-336.el6.x86_64/vmlinux DUMPFILE: /var/crash/127.0.0.1-2012-10-23-17:27:37/vmcore [PARTIAL DUMP] CPUS: 4 DATE: Tue Oct 23 17:26:28 2012 UPTIME: 00:21:08 LOAD AVERAGE: 0.70, 0.25, 0.10 TASKS: 177 NODENAME: sluo-10-55 RELEASE: 2.6.32-336.el6.x86_64 VERSION: #1 SMP Mon Oct 22 17:39:08 EDT 2012 MACHINE: x86_64 (3092 Mhz) MEMORY: 7.8 GB PANIC: "Oops: 0000 [#1] SMP " (check log for details) PID: 2615 COMMAND: "qemu-kvm" TASK: ffff8802318d4080 [THREAD_INFO: ffff8802348ec000] CPU: 0 STATE: TASK_RUNNING (PANIC) crash> bt PID: 2615 TASK: ffff8802318d4080 CPU: 0 COMMAND: "qemu-kvm" #0 [ffff8802348ed160] machine_kexec at ffffffff81035b8b #1 [ffff8802348ed1c0] crash_kexec at ffffffff810c0a92 #2 [ffff8802348ed290] oops_end at ffffffff8150fda0 #3 [ffff8802348ed2c0] no_context at ffffffff81046bfb #4 [ffff8802348ed310] __bad_area_nosemaphore at ffffffff81046e85 #5 [ffff8802348ed360] bad_area_nosemaphore at ffffffff81046f53 #6 [ffff8802348ed370] __do_page_fault at ffffffff810476b1 #7 [ffff8802348ed490] do_page_fault at ffffffff81511cee #8 [ffff8802348ed4c0] page_fault at ffffffff8150f0a5 [exception RIP: x86_schedule_events+288] RIP: ffffffff8101c830 RSP: ffff8802348ed578 RFLAGS: 00010093 RAX: 00000000dc527000 RBX: ffff88002c20cc40 RCX: 0000000000000009 RDX: 0000000000000004 RSI: 0000000000000001 RDI: ffff88002c20cc48 RBP: ffff8802348ed7d8 R8: ffff880233b85800 R9: ffff8802348ed798 R10: ffffffff81df1ec0 R11: 0000000000000000 R12: 0000000000000003 R13: ffff8802348ed598 R14: 0000000000000000 R15: ffff8802348ed7f8 ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 #9 [ffff8802348ed7e0] x86_pmu_add at ffffffff8101b3a3 #10 [ffff8802348ed930] event_sched_in at ffffffff81110981 #11 [ffff8802348ed960] __perf_install_in_context at ffffffff81114b8e #12 [ffff8802348ed9b0] remote_function at ffffffff8110ee48 #13 [ffff8802348ed9d0] smp_call_function_single at ffffffff810ae28c #14 [ffff8802348eda40] task_function_call at ffffffff8110eea4 #15 [ffff8802348eda80] perf_install_in_context at ffffffff81111c58 #16 [ffff8802348edad0] perf_event_create_kernel_counter at ffffffff81117785 #17 [ffff8802348edb10] reprogram_counter at ffffffffa035a9db [kvm] #18 [ffff8802348edb80] reprogram_gp_counter at ffffffffa035ab30 [kvm] #19 [ffff8802348edba0] reprogram_idx at ffffffffa035ac99 [kvm] #20 [ffff8802348edbb0] kvm_pmu_set_msr at ffffffffa035af0f [kvm] #21 [ffff8802348edbf0] kvm_set_msr_common at ffffffffa03408c5 [kvm] #22 [ffff8802348edc20] vmx_set_msr at ffffffffa0396106 [kvm_intel] #23 [ffff8802348edc50] handle_wrmsr at ffffffffa0398d08 [kvm_intel] #24 [ffff8802348edc80] vmx_handle_exit at ffffffffa0398ef3 [kvm_intel] #25 [ffff8802348edcc0] kvm_arch_vcpu_ioctl_run at ffffffffa0345c26 [kvm] #26 [ffff8802348eddc0] kvm_vcpu_ioctl at ffffffffa032eff4 [kvm] #27 [ffff8802348ede60] vfs_ioctl at ffffffff81194ab2 #28 [ffff8802348edea0] do_vfs_ioctl at ffffffff81194f7a #29 [ffff8802348edf30] sys_ioctl at ffffffff811951d1 #30 [ffff8802348edf80] system_call_fastpath at ffffffff8100b072 RIP: 00007fd17626a7b7 RSP: 00007fd16bdfdac8 RFLAGS: 00000246 RAX: 0000000000000010 RBX: ffffffff8100b072 RCX: ffffffffffffffff RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 000000000000000b RBP: 00007fd1787e3000 R8: 000000003766a6f5 R9: 00000000000004f4 R10: 0000000000000001 R11: 0000000000000246 R12: 00007fd179a97350 R13: 00007fd179a96f10 R14: 0000000000000000 R15: 00007fd179c12e50 ORIG_RAX: 0000000000000010 CS: 0033 SS: 002b Expected results: Additional info: