Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
Comment 5Michael S. Tsirkin
2012-10-31 09:53:17 UTC
<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: