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
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
