Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-13 Thread Jan Kiszka
On 2013-05-12 18:52, Kashyap Chamarthy wrote: [ 217.938034] Uhhuh. NMI received for unknown reason 30 on CPU 0. [ 217.938034] Do you have a strange power saving mode enabled? .[ 222.523373] Uhhuh. NMI received for unknown reason 20 on CPU 0. [ 222.524073] Do you

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-13 Thread Gleb Natapov
On Mon, May 13, 2013 at 08:31:33AM +0200, Jan Kiszka wrote: On 2013-05-12 18:52, Kashyap Chamarthy wrote: [ 217.938034] Uhhuh. NMI received for unknown reason 30 on CPU 0. [ 217.938034] Do you have a strange power saving mode enabled? .[ 222.523373] Uhhuh.

RE: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-13 Thread Ren, Yongjie
with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted. On Mon, May 13, 2013 at 08:31:33AM +0200, Jan Kiszka wrote: On 2013-05-12 18:52, Kashyap Chamarthy wrote: [ 217.938034] Uhhuh. NMI received for unknown reason 30 on CPU 0. [ 217.938034] Do

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-13 Thread Jan Kiszka
...@vger.kernel.org Subject: Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted. On Mon, May 13, 2013 at 08:31:33AM +0200, Jan Kiszka wrote: On 2013-05-12 18:52, Kashyap Chamarthy wrote: [ 217.938034] Uhhuh. NMI received for unknown reason 30

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-13 Thread Gleb Natapov
Chamarthy; Abel Gordon; Nakajima, Jun; kvm@vger.kernel.org; kvm-ow...@vger.kernel.org Subject: Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted. On Mon, May 13, 2013 at 08:31:33AM +0200, Jan Kiszka wrote: On 2013-05-12 18:52, Kashyap Chamarthy wrote

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-12 Thread Gleb Natapov
On Fri, May 10, 2013 at 10:40:22AM -0700, Nakajima, Jun wrote: On Fri, May 10, 2013 at 9:33 AM, Jan Kiszka jan.kis...@siemens.com wrote: On 2013-05-10 17:39, Kashyap Chamarthy wrote: On Fri, May 10, 2013 at 8:54 PM, Jan Kiszka jan.kis...@siemens.com wrote: On 2013-05-10 17:12, Jan Kiszka

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-12 Thread Kashyap Chamarthy
I tried to reproduce such a problem, and I found L2 (Linux) hangs in SeaBIOS, after line iPXE (http://ipxe.org) It happens with or w/o VMCS shadowing (and even without my virtual EPT patches). I didn't realize this problem until I updated the L1 kernel to the latest (e.g. 3.9.0) from

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-12 Thread Gleb Natapov
On Sun, May 12, 2013 at 06:00:38PM +0530, Kashyap Chamarthy wrote: I tried to reproduce such a problem, and I found L2 (Linux) hangs in SeaBIOS, after line iPXE (http://ipxe.org) It happens with or w/o VMCS shadowing (and even without my virtual EPT patches). I didn't realize this

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-12 Thread Kashyap Chamarthy
On Sun, May 12, 2013 at 6:08 PM, Gleb Natapov g...@redhat.com wrote: On Sun, May 12, 2013 at 06:00:38PM +0530, Kashyap Chamarthy wrote: I tried to reproduce such a problem, and I found L2 (Linux) hangs in SeaBIOS, after line iPXE (http://ipxe.org) It happens with or w/o VMCS

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-12 Thread Abel Gordon
Kashyap Chamarthy kashyap...@gmail.com wrote on 12/05/2013 03:42:33 PM: Again, sorry :(. I was just about to reply that this was physical host. I'm testing by disabling VMCS Shadowing per Jan Kiszka's suggestion, and retrying. But I doubt that's the reason my L2 is seg-faulting. If it

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-12 Thread Kashyap Chamarthy
On Sun, May 12, 2013 at 6:29 PM, Abel Gordon ab...@il.ibm.com wrote: Kashyap Chamarthy kashyap...@gmail.com wrote on 12/05/2013 03:42:33 PM: Again, sorry :(. I was just about to reply that this was physical host. I'm testing by disabling VMCS Shadowing per Jan Kiszka's suggestion, and

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-12 Thread Kashyap Chamarthy
So, from the above info shadow-vmcs is ruled-out. I'm trying to investigate further, will post details if I have new findings. Update: - I just tried to create L2 w/ Fedora-19 TC4 compose of 11MAY2013, I contibuously see the below fragment (F18/F19, whatever the L2 guest is):

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-12 Thread Kashyap Chamarthy
[ 217.938034] Uhhuh. NMI received for unknown reason 30 on CPU 0. [ 217.938034] Do you have a strange power saving mode enabled? .[ 222.523373] Uhhuh. NMI received for unknown reason 20 on CPU 0. [ 222.524073] Do you have a strange power saving mode enabled? [

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-12 Thread Abel Gordon
Kashyap Chamarthy kashyap...@gmail.com wrote on 12/05/2013 04:06:40 PM: Note shadow vmcs is disabled unless you have a processor that supports this feature. Do you ?! Yes, I noted this in my previous email. I'm using Intel Haswell. Here's the info from MSR bits on the machine(From

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-12 Thread Gleb Natapov
On Sun, May 12, 2013 at 04:48:28PM +0300, Abel Gordon wrote: Kashyap Chamarthy kashyap...@gmail.com wrote on 12/05/2013 04:06:40 PM: Note shadow vmcs is disabled unless you have a processor that supports this feature. Do you ?! Yes, I noted this in my previous email. I'm using

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-12 Thread Gleb Natapov
On Sun, May 12, 2013 at 07:01:43PM +0530, Kashyap Chamarthy wrote: So, from the above info shadow-vmcs is ruled-out. I'm trying to investigate further, will post details if I have new findings. Update: - I just tried to create L2 w/ Fedora-19 TC4 compose of 11MAY2013, I

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-12 Thread Kashyap Chamarthy
Yep, shadow-vmcs enabled :) :) Good to clarify. Just for reference, here's the detailed procedure I noted while testing it on Haswell -- https://raw.github.com/kashyapc/nvmx-haswell/master/SETUP-nVMX.rst Also note you can disable shadow-vmcs using the kvm-intel kernel module

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-12 Thread Kashyap Chamarthy
[ 217.938034] Uhhuh. NMI received for unknown reason 30 on CPU 0. [ 217.938034] Do you have a strange power saving mode enabled? .[ 222.523373] Uhhuh. NMI received for unknown reason 20 on CPU 0. [ 222.524073] Do you have a strange power saving mode enabled? [

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-11 Thread Kashyap Chamarthy
Side note: While testing nVMX, I was hitting a libvirt bug, and filed this one: -- https://bugzilla.redhat.com/show_bug.cgi?id=961665 -- [virsh] Attempt to force destroy a guest fails due to 'unknown' reason, leaves a defunct qemu process which I was told is possibly a Kernel/KVM bug. Any

[nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-10 Thread Kashyap Chamarthy
Heya, This is on Intel Haswell. First, some version info: L0, L1 -- both of them have same versions of kernel, qemu: = $ rpm -q kernel --changelog | head -2 * Thu May 09 2013 Josh Boyer - 3.10.0-0.rc0.git23.1 - Linux v3.9-11789-ge0fd9af = = $ uname -r ; rpm -q qemu-kvm

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-10 Thread Kashyap Chamarthy
On Fri, May 10, 2013 at 8:03 PM, Kashyap Chamarthy kashyap...@gmail.com wrote: Also, I'm able to reproduce this consistently: When I create an L2 guest: -- [.] [ 463.655031] Dazed and confused, but trying to continue [ 463.975563] Uhhuh. NMI received for unknown reason

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-10 Thread Jan Kiszka
On 2013-05-10 15:00, Kashyap Chamarthy wrote: Heya, This is on Intel Haswell. First, some version info: L0, L1 -- both of them have same versions of kernel, qemu: = $ rpm -q kernel --changelog | head -2 * Thu May 09 2013 Josh Boyer - 3.10.0-0.rc0.git23.1 - Linux

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-10 Thread Jan Kiszka
On 2013-05-10 17:12, Jan Kiszka wrote: On 2013-05-10 15:00, Kashyap Chamarthy wrote: Heya, This is on Intel Haswell. First, some version info: L0, L1 -- both of them have same versions of kernel, qemu: = $ rpm -q kernel --changelog | head -2 * Thu May 09 2013 Josh Boyer -

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-10 Thread Kashyap Chamarthy
On Fri, May 10, 2013 at 8:54 PM, Jan Kiszka jan.kis...@siemens.com wrote: On 2013-05-10 17:12, Jan Kiszka wrote: On 2013-05-10 15:00, Kashyap Chamarthy wrote: Heya, This is on Intel Haswell. First, some version info: L0, L1 -- both of them have same versions of kernel, qemu:

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-10 Thread Kashyap Chamarthy
[3] Libvirt XMLs I used (for reference) -- https://github.com/kashyapc/nvmx-haswell/tree/master/tests/libvirt-xmls-for-l1-l2 Oops, forgot to add, here we go -- https://github.com/kashyapc/nvmx-haswell/tree/master/tests/libvirt-xmls-for-l1-l2 /kashyap -- To unsubscribe from this list: send the

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-10 Thread Jan Kiszka
On 2013-05-10 17:39, Kashyap Chamarthy wrote: On Fri, May 10, 2013 at 8:54 PM, Jan Kiszka jan.kis...@siemens.com wrote: On 2013-05-10 17:12, Jan Kiszka wrote: On 2013-05-10 15:00, Kashyap Chamarthy wrote: Heya, This is on Intel Haswell. First, some version info: L0, L1 -- both of them

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-10 Thread Nakajima, Jun
On Fri, May 10, 2013 at 9:33 AM, Jan Kiszka jan.kis...@siemens.com wrote: On 2013-05-10 17:39, Kashyap Chamarthy wrote: On Fri, May 10, 2013 at 8:54 PM, Jan Kiszka jan.kis...@siemens.com wrote: On 2013-05-10 17:12, Jan Kiszka wrote: On 2013-05-10 15:00, Kashyap Chamarthy wrote: Heya, This

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-10 Thread Jan Kiszka
On 2013-05-10 19:40, Nakajima, Jun wrote: On Fri, May 10, 2013 at 9:33 AM, Jan Kiszka jan.kis...@siemens.com wrote: On 2013-05-10 17:39, Kashyap Chamarthy wrote: On Fri, May 10, 2013 at 8:54 PM, Jan Kiszka jan.kis...@siemens.com wrote: On 2013-05-10 17:12, Jan Kiszka wrote: On 2013-05-10

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-10 Thread Kashyap Chamarthy
We know after you tried. I don't have access to a Haswell box, so we better exclude this beforehand. Fair enough. I'll try that too, and let you know. You get that backtrace in L1, correct? Yes. If you have any further tracing pointers, I could do some debugging. Thanks, I may come

Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

2013-05-10 Thread Kashyap Chamarthy
On Fri, May 10, 2013 at 11:39 PM, Jan Kiszka jan.kis...@siemens.com wrote: On 2013-05-10 19:40, Nakajima, Jun wrote: On Fri, May 10, 2013 at 9:33 AM, Jan Kiszka jan.kis...@siemens.com wrote: On 2013-05-10 17:39, Kashyap Chamarthy wrote: On Fri, May 10, 2013 at 8:54 PM, Jan Kiszka