From: Gleb Natapov <gleb@redhat.com>
To: Kashyap Chamarthy <kashyap.cv@gmail.com>
Cc: Abel Gordon <ABELG@il.ibm.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
kvm-owner@vger.kernel.org
Subject: Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.
Date: Sun, 12 May 2013 18:52:17 +0300 [thread overview]
Message-ID: <20130512155217.GB26185@redhat.com> (raw)
In-Reply-To: <CAOaxAcbc52Yq1XnAPWGL5o9ygDQ2mQQOmm2C=rWyMKnWwJSOAg@mail.gmail.com>
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
> contibuously see the below fragment (F18/F19, whatever the L2 guest
> is):
>
> --------------------
> ....
> [ 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?
> [ 222.524073] Dazed and confused, but trying to continue
> [ 243.860319] Uhhuh. NMI received for unknown reason 30 on CPU 0
> .....
> --------------------
> At the moment, L2 guest creation stuck at the above message
>
Are those in L2 dmesg or L1?
> However I have neither HPET or NMI Watchdog enabled on L0/L1. I checked it by:
>
> $ cat /etc/grub2.cfg | egrep -i 'hpet|nmi'
>
IIRC watchdog is enabled by default.
> I wonder if I'm missing something trivial, or maybe this is some kind
> of bug that needs more deeper investigation. But Jan Kiszka reported
> he isn't seeing any probs (but he isn't using "Haswell" ).
>
> Thanks.
--
Gleb.
next prev parent reply other threads:[~2013-05-12 15:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 13:00 [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted Kashyap Chamarthy
[not found] ` <CAOaxAcZ1uyx-RrmDEiZhG2H8H5zTCK9iz1nHJKEJwUfhn=vZHA@mail.gmail.com>
2013-05-10 14:41 ` Kashyap Chamarthy
2013-05-10 15:12 ` Jan Kiszka
2013-05-10 15:24 ` Jan Kiszka
2013-05-10 15:39 ` Kashyap Chamarthy
2013-05-10 15:46 ` Kashyap Chamarthy
2013-05-10 16:33 ` Jan Kiszka
2013-05-10 17:40 ` Nakajima, Jun
2013-05-10 18:09 ` Jan Kiszka
2013-05-10 21:37 ` Kashyap Chamarthy
2013-05-11 6:55 ` Kashyap Chamarthy
2013-05-12 8:32 ` Gleb Natapov
2013-05-12 12:30 ` Kashyap Chamarthy
2013-05-12 12:38 ` Gleb Natapov
2013-05-12 12:42 ` Kashyap Chamarthy
2013-05-12 12:59 ` Abel Gordon
2013-05-12 13:06 ` Kashyap Chamarthy
2013-05-12 13:31 ` Kashyap Chamarthy
2013-05-12 13:33 ` Kashyap Chamarthy
2013-05-12 15:52 ` Gleb Natapov [this message]
2013-05-12 16:52 ` Kashyap Chamarthy
2013-05-13 6:31 ` Jan Kiszka
2013-05-13 6:39 ` Gleb Natapov
2013-05-13 6:45 ` Ren, Yongjie
2013-05-13 6:57 ` Jan Kiszka
2013-05-13 7:06 ` Gleb Natapov
2013-05-12 13:48 ` Abel Gordon
2013-05-12 15:35 ` Gleb Natapov
2013-05-12 16:29 ` Kashyap Chamarthy
2013-05-10 21:37 ` Kashyap Chamarthy
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=20130512155217.GB26185@redhat.com \
--to=gleb@redhat.com \
--cc=ABELG@il.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=jun.nakajima@intel.com \
--cc=kashyap.cv@gmail.com \
--cc=kvm-owner@vger.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