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?
[quote]
We will install SP2 for w2k8 this evening… but I don’t think it’s the problem/solution.[/quote]
Yesterday evening our TerminalServer did a reboot again. Also I’ve got the same message in the kern.log again:
Jun 28 23:07:05 v07l kernel: [3727054.923259] kvm_handle_exit: Breaking out of NMI-blocked state on VCPU 0 after 1 s timeout
Jun 28 23:07:05 v07l kernel: [3727054.923259] kvm_handle_exit: Breaking out of NMI-blocked state on VCPU 2 after 1 s timeout
Jun 28 23:07:05 v07l kernel: [3727054.923259] kvm_handle_exit: Breaking out of NMI-blocked state on VCPU 3 after 1 s timeout
[quote]
We will install SP2 for w2k8 this evening… but I don’t think it’s the problem/solution.[/quote]
Yesterday evening our TerminalServer did a reboot again. Also I’ve got the same message in the kern.log again:
Jun 28 23:07:05 v07l kernel: [3727054.923259] kvm_handle_exit: Breaking out of NMI-blocked state on VCPU 0 after 1 s timeout
Jun 28 23:07:05 v07l kernel: [3727054.923259] kvm_handle_exit: Breaking out of NMI-blocked state on VCPU 2 after 1 s timeout
Jun 28 23:07:05 v07l kernel: [3727054.923259] kvm_handle_exit: Breaking out of NMI-blocked state on VCPU 3 after 1 s timeout
Nobody as any idea?
Thanks
Andy[/quote]
Not sure if this will help you diagnose the problem but it might prevent the server rebooting:
Control Panel > System > Advanced > Startup and Recovery > Automatically Restart.
I have W2K3 running on Proxmox for 8 months without a single hitch. Proxmox is a ready-to-go version of KVM on Debian 64. (Note to mod: am I allowed to mention Proxmox here? It is KVM-based.)
[quote=“gezley”]
Not sure if this will help you diagnose the problem but it might prevent the server rebooting:
Control Panel > System > Advanced > Startup and Recovery > Automatically Restart.
I have W2K3 running on Proxmox for 8 months without a single hitch. Proxmox is a ready-to-go version of KVM on Debian 64. (Note to mod: am I allowed to mention Proxmox here? It is KVM-based.)[/quote]
If I disable the automatic reboot, the system is waiting for a reboot at a bluescreen. (So, this is no solution!)
We are running others w2k8 machines, witch are not on heavy load, with no porblem.
I think the reboots have any relationship with the load memory and CPU on the guest and host-system.
Just a few random thoughts here to hopefully open some more doors here…
Did you happen to have a subsequent kernel update to the host operating system? Anything in the /var/log directories of relevance?
Does your machine have any scheduled tasks running at a specific time?
I think you said your server 2008 system is a terminal server. Is there any chance your server 2008 system that reboots is performing (and failing) some sort of authentication at the time? Perhaps check your domain controller logs for unsuccessful authentications right around the time of the reboots. Can you run wireshark (or something like that) against the network interface (with proper permission from whoever grants it) to get some idea of what your bsod server 2008 system is doing some time before it’s reboot (is it attempting to talk to “anyone” (any server))?
Is it only that one specific system that reboots?
Have you heard of Zenoss (it’s free, yet they have a paid/enterprise version). Very powerful, not good for your immediate issue, but good for overall systemic health if properly set up.
Just an idea to hopefully garner more clues – consider running process explorer on the victim kvm guest operating system (your System 2008). technet.microsoft.com/en-us/sysi … 96653.aspx
Process Explorer I believe was originally created by sysinternals, and Microsoft bought them out (because they were too good). Anyway, run process explorer, make notes of what you see soon after the reboot, and then later at different times of the day.
Is there a specific time this occurs? Is the only change a service pack? (I think I read that a service pack was installed?) Is there anything from the event logs during/after the time of the reboot?
After the server 2008 reboot, go to (on the host system) /var/log/ and ‘ls -altr’ to see what was written to last, or a find command that is set to see the last files written to in about 30 minutes?
[quote=“uid99”]Just a few random thoughts here to hopefully open some more doors here…
Did you happen to have a subsequent kernel update to the host operating system? Anything in the /var/log directories of relevance?
[/quote]
See first post:
Jun 28 23:07:05 v07l kernel: [3727054.923259] kvm_handle_exit: Breaking out of NMI-blocked state on VCPU 0 after 1 s timeout
Jun 28 23:07:05 v07l kernel: [3727054.923259] kvm_handle_exit: Breaking out of NMI-blocked state on VCPU 2 after 1 s timeout
Jun 28 23:07:05 v07l kernel: [3727054.923259] kvm_handle_exit: Breaking out of NMI-blocked state on VCPU 3 after 1 s timeout
No. The reboot is sometimes twice a day, somtimes there is no reboot for a week.
No, but one will reboot more frequently. But on this host are many (about 10) guests, and there is a average load of 3 or 4.
We use zabbix for monitoring, and we are very happy with this.
I know the Process-Explorer, but i don’t know what I should watching.
No, there is no specified timeframe. It’s Service Pack 2 installed and all patches. But we had this issue allready with SP1.
As I said, there are the following entries in kern.log
Jun 28 23:07:05 v07l kernel: [3727054.923259] kvm_handle_exit: Breaking out of NMI-blocked state on VCPU 0 after 1 s timeout
Jun 28 23:07:05 v07l kernel: [3727054.923259] kvm_handle_exit: Breaking out of NMI-blocked state on VCPU 2 after 1 s timeout
Jun 28 23:07:05 v07l kernel: [3727054.923259] kvm_handle_exit: Breaking out of NMI-blocked state on VCPU 3 after 1 s timeout
But recently we switched to the new stable branch: 0.10.6, and I don’t get this entries in the kern.log anymore.
[quote]Hi Andreas.
I’m reading your post for reboots of w2k8. My w2k8 reboots too and windbg return the same error. How can you resolve it?
Thanks Miguel[/quote]
Hi Miguel
Good questions. You can minimize the frequency be reducing the load of the host-system. We still have this Problem sometimes.
If you will find any solution, let me know… i would be happy too…
Is there a specific time this occurs? Is the only change a service pack? (I think I read that a service pack was installed?) Is there anything from the event logs during/after the time of the reboot?
After the server 2008 reboot, go to (on the host system) /var/log/ and ‘ls -altr’ to see what was written to last, or a find command that is set to see the last files written to in about 30 minutes?
