From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 72381] New: [Nested] L1 call trace when create windows 7 guest as L2 guest.
Date: Tue, 18 Mar 2014 07:43:26 +0000 [thread overview]
Message-ID: <bug-72381-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=72381
Bug ID: 72381
Summary: [Nested] L1 call trace when create windows 7 guest as
L2 guest.
Product: Virtualization
Version: unspecified
Kernel Version: 3.14.0-rc3
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: Robert.Hu@intel.com
Regression: No
Created attachment 129911
--> https://bugzilla.kernel.org/attachment.cgi?id=129911&action=edit
L1 serial
Environment:
------------
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):linux
kvm.git Commit:94b3ffcd41a90d2cb0b32ca23aa58a01111d5dc0
qemu.git Commit:087edb503afebf184f07078900efc26c73035e98
Host Kernel Version:3.14.0-rc3
Hardware:Romley_EP
Bug detailed description:
--------------------------
when create a windows 7 guest as L2 guest,L2 guest boot up fail, L1 guest will
call trace. ping L1 guest pass, but ssh L1 guest fail
note:
when create a rhel6u4 guest as L2 guest, L1 guest and L2 guest work fine
Reproduce steps:
----------------
1.1.create L1 guest:
qemu-system-x86_64 -enable-kvm -m 6G -smp 4 -net nic,macaddr=00:12:52:13:46:67
-net tap,script=/etc/kvm/qemu-ifup ia32e_nested_kvm.img -cpu host,level=9
2.create L2 guest:
qemu-system-x86_64 -enable-kvm -m 1G -smp 2 -net none ia32e_win7.img
Current result:
----------------
L1 call trace
Expected result:
----------------
L1 and L2 guest boot up fine.
Basic root-causing log:
----------------------
sending NMI to all CPUs:
NMI backtrace for cpu 3
CPU: 3 PID: 4186 Comm: qemu-system-x86 Not tainted 3.12.0-rc5 #2
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
task: ffff8801b890c040 ti: ffff8801b77b8000 task.ti: ffff8801b77b8000
RIP: 0010:[<ffffffff8145dac4>] [<ffffffff8145dac4>] _raw_spin_lock+0x20/0x24
RSP: 0018:ffff8801b77b9bc8 EFLAGS: 00000293
RAX: 0000000000006e6b RBX: ffff8801b8170080 RCX: 000000000018a337
RDX: 000000000000006e RSI: 0000000000000000 RDI: ffff8801b77dc000
RBP: ffff8801b77b9bc8 R08: 0000000000000007 R09: ffff8801b77b9c20
R10: 0000000000002900 R11: 0000000000002931 R12: 0000000000000000
R13: 000000001278f000 R14: 0000000000000000 R15: 0000000000000000
FS: 00007ff63bfff700(0000) GS:ffff8801bfd80000(0000) knlGS:fffff880009e6000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffff8a0000e7000 CR3: 00000000b1e6d000 CR4: 00000000000026e0
Stack:
ffff8801b77b9c58 ffffffffa01c8cb3 ffff8801b77b9c27 0000000000000001
ffff8801b77b9bf8 00ffffffa022d1bf 0000000000001b66 00000002a01b481b
000000000001278f 000000000018a337 00000001b77b9c88 01ffffff00000000
Call Trace:
[<ffffffffa01c8cb3>] tdp_page_fault+0x146/0x1dc [kvm]
[<ffffffffa01c9024>] kvm_mmu_page_fault+0x22/0xc5 [kvm]
[<ffffffffa022f10c>] handle_ept_violation+0x13d/0x149 [kvm_intel]
[<ffffffffa02314c9>] vmx_handle_exit+0x171/0x193 [kvm_intel]
[<ffffffffa022b14e>] ? vmx_invpcid_supported+0x18/0x18 [kvm_intel]
[<ffffffffa01bc5ea>] vcpu_enter_guest+0x65a/0x696 [kvm]
[<ffffffff81064030>] ? __cond_resched+0x25/0x30
[<ffffffffa01bc6cb>] __vcpu_run+0xa5/0x262 [kvm]
[<ffffffffa01c015c>] kvm_arch_vcpu_ioctl_run+0xef/0x1ac [kvm]
[<ffffffffa01af04f>] kvm_vcpu_ioctl+0x121/0x4b1 [kvm]
[<ffffffff81085b3d>] ? futex_wake+0xeb/0xfd
[<ffffffff81464530>] ? ret_from_fork+0xb0/0xb0
[<ffffffff8112a5a1>] do_vfs_ioctl+0x2ad/0x2c9
[<ffffffffa01ba29b>] ? kvm_on_user_return+0x4f/0x51 [kvm]
[<ffffffff8112a616>] SyS_ioctl+0x59/0x7d
[<ffffffff814645a2>] system_call_fastpath+0x16/0x1b
Code: 07 38 d0 74 04 f3 90 eb f6 c9 c3 55 48 89 e5 b8 00 01 00 00 f0 66 0f c1
07 89 c2 66 c1 ea 08 38 c2 74 0a 8a 07 38 d0 74 04 f3 90 <eb> f6 c9 c3 55 48 89
e5 9c 58 fa ba 00 01 00 00 f0 66 0f c1 17
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2014-03-19 18:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 7:43 bugzilla-daemon [this message]
2014-03-24 17:38 ` [Bug 72381] [Nested] L1 call trace when create windows 7 guest as L2 guest bugzilla-daemon
2014-03-26 8:38 ` bugzilla-daemon
2014-08-08 5:35 ` bugzilla-daemon
2014-08-08 5:36 ` bugzilla-daemon
2014-08-08 5:38 ` bugzilla-daemon
2014-08-08 5:38 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-72381-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox