From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Andreas Jud <save@webflash.ch>, kvm@vger.kernel.org
Subject: Re: w2k8 - reboots unexpected
Date: Thu, 18 Jun 2009 15:45:54 +0300 [thread overview]
Message-ID: <4A3A3702.80301@redhat.com> (raw)
In-Reply-To: <20090618113747.GD20289@redhat.com>
On 06/18/2009 02:37 PM, Gleb Natapov wrote:
> On Thu, Jun 18, 2009 at 01:27:25PM +0200, Andreas Jud wrote:
>
>> Hi
>>
>> We are running kvm-84 on debian x64 Linux.
>>
>> We have serveral guest running on this host.
>>
>> One guest witch is running windows 2008 server and used as a terminal
>> server, reboots sometimes unexpected.
>>
>> All what I found so far is the following error in the kernel-logfile:
>> Jun 18 10:33:17 sov07l kernel: [1470365.925930] kvm_handle_exit: Breaking
>> out of NMI-blocked state on VCPU 1 after 1 s timeout
>> Jun 18 10:33:17 sov07l kernel: [1470365.929077] kvm_handle_exit: Breaking
>> out of NMI-blocked state on VCPU 2 after 1 s timeout
>> Jun 18 10:33:17 sov07l kernel: [1470365.929077] kvm_handle_exit: Breaking
>> out of NMI-blocked state on VCPU 3 after 1 s timeout
>>
>> Does anybody have an idea what this mean? And what we could do, to make the
>> system stable? resolve this error?
>>
>>
> You host cpu does not support NMI injection in VMX (your Intel processor
> is too old). I can't tell for sure if this is what causes w2k8 to reboot
> itself, but this is possible. Does w2k8 has some kind of NMI watchdog?
>
>
It doesn't inject NMIs here.
Can you set up memory dumping on BSODs and run the !analyze command in
windbg?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-06-18 12:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 11:27 w2k8 - reboots unexpected Andreas Jud
2009-06-18 11:37 ` Gleb Natapov
2009-06-18 12:45 ` Avi Kivity [this message]
2009-06-18 14:16 ` Andreas Jud
2009-06-18 14:24 ` Andreas Jud
2009-06-18 13:55 ` Andreas Jud
2009-06-18 14:02 ` Gleb Natapov
2009-06-19 5:44 ` Andreas Jud
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=4A3A3702.80301@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=save@webflash.ch \
/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