All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 71521] New: Host call trace when create guest.
Date: Wed, 05 Mar 2014 02:56:25 +0000	[thread overview]
Message-ID: <bug-71521-28872@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=71521

            Bug ID: 71521
           Summary: Host call trace when create guest.
           Product: Virtualization
           Version: unspecified
    Kernel Version: 3.14.0-rc1
          Hardware: x86-64
                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 128051
  --> https://bugzilla.kernel.org/attachment.cgi?id=128051&action=edit
host-dmesg

Environment:
------------
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Linux
kvm.git Commit:d3714010c307d26df251c45be9cd12ab6d41f0c4
qemu-kvm Commit:9fbee91a131a05e443d7108d7fbdf3ca91020290
Host Kernel Version:3.14.0-rc1
Hardware:Romley_EP, Ivytown_EP


Bug detailed description:
--------------------------
after create guest, the host will call trace


Reproduce steps:
----------------
1. create guest
qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none /root/rhel6u4.qcow

Current result:
----------------
host call trace

Expected result:
----------------
guest and host work fine

Basic root-causing log:
----------------------
vmwrite error: reg 2812 value 0 (err 12)
CPU: 2 PID: 10596 Comm: qemu-system-x86 Not tainted 3.14.0-rc1 #2
Hardware name: Intel Corporation S2600CP/S2600CP, BIOS
SE5C600.86B.02.01.1001.080920131108 08/09/2013
 0000000000000000 ffff880234079c78 ffffffff81482475 0000000000000006
 ffff880623130040 ffff880234079c88 ffffffffa02d51d2 ffff880234079c98
 ffffffffa02d51ed ffff880234079cc8 ffffffffa02dd407 00000000000003c0
Call Trace:
 [<ffffffff81482475>] dump_stack+0x49/0x5c
 [<ffffffffa02d51d2>] vmwrite_error+0x27/0x29 [kvm_intel]
 [<ffffffffa02d51ed>] vmcs_writel+0x19/0x1b [kvm_intel]
 [<ffffffffa02dd407>] vmx_set_msr+0x10b/0x26e [kvm_intel]
 [<ffffffffa025c37c>] do_set_msr+0x27/0x29 [kvm]
 [<ffffffffa02673cf>] msr_io+0xa0/0x101 [kvm]
 [<ffffffffa025c355>] ? kvm_set_msr+0x13/0x13 [kvm]
 [<ffffffffa0267936>] kvm_arch_vcpu_ioctl+0x37e/0xb7b [kvm]
 [<ffffffffa02d5484>] ? update_cr8_intercept+0x1b/0x1d [kvm_intel]
 [<ffffffffa0264495>] ? update_cr8_intercept+0x65/0x6a [kvm]
 [<ffffffffa026a07c>] ? kvm_arch_vcpu_ioctl_set_sregs+0x38b/0x407 [kvm]
 [<ffffffffa025750e>] ? kvm_vcpu_ioctl+0x25c/0x4b5 [kvm]
 [<ffffffffa02681d8>] ? kvm_arch_vcpu_load+0xa5/0x16c [kvm]
 [<ffffffffa02576f0>] kvm_vcpu_ioctl+0x43e/0x4b5 [kvm]
 [<ffffffff8110349b>] ? do_brk+0x265/0x2bc
 [<ffffffff8113495d>] do_vfs_ioctl+0x2a2/0x2be
 [<ffffffff8113c799>] ? __fget_light+0x4a/0x5c
 [<ffffffff811349d2>] SyS_ioctl+0x59/0x7d
 [<ffffffff8148c762>] system_call_fastpath+0x16/0x1b


more tests:
kernel version:3.14.0-rc1
kvm.git  +  qemu.git  =result
d3714010 +  732c66ce  =pass
d3714010 +  9fbee91a  =fail


kernel version:3.13.-rc2
kvm.git   +   qemu.git  =result
7650b687  +   732c66ce  =  pass
7650b687  +   9fbee91a  = pass

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2014-03-05  2:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05  2:56 bugzilla-daemon [this message]
2014-03-11  1:49 ` [Bug 71521] Host call trace when create guest bugzilla-daemon
2014-03-11  1:49 ` bugzilla-daemon
2014-03-25 10:18 ` bugzilla-daemon
2014-03-28  4:32 ` bugzilla-daemon
2014-03-28  4:34 ` bugzilla-daemon
2014-03-28  6:29 ` 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-71521-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.