Red Hat Bugzilla – Bug 1292922
Windows 2012 R2 systems periodically lock up.
Last modified: 2017-03-19 11:56:03 EDT
Description of problem:
Windows 2012 R2 systems periodically lock up and are unreachable, issue does not occur with Windows 2008 servers. Guest tools are installed with the latest.
Version-Release number of selected component (if applicable):
Unknown, only seen with this customer so far.
Windows 2012 VMs are accessible
VM is always accessible when it is running Win 2012 R2 systems
Data and analysis coming shortly
It is highly unlikely to be a Vdsm issue, as it is oblivious of which OS is being run on the VM.
Robert, can you specify versions of libvirt, qemu-kvm and kernel on the host running the VM?
Gal, can you take a look or ask a relevant question?
I'm guessing it's qemu, kenel, or Window guest driver, and not Vdsm.
(In reply to Dan Kenigsberg from comment #3)
> It is highly unlikely to be a Vdsm issue, as it is oblivious of which OS is
> being run on the VM.
> Robert, can you specify versions of libvirt, qemu-kvm and kernel on the host
> running the VM?
> Gal, can you take a look or ask a relevant question?
Robert, is it possible to ask the customer to use NMI and provide a windows crash dump while this hang occurs? See https://support.microsoft.com/en-us/kb/927069 for instructions. Thanks.
Dan, here's what the customer found. It seems like this isn't a hard lock based on his description:
No dump files were generated in the Dump file location (%SystemRoot%\MEMORY.DMP) on either VM. I suspect there could be an underlying storage issue when we run in to this problem. I should note that the systems still respond to ICMP ping when this problem occurs. However, remote desktop cannot establish a socket connection and the log on screen interface via VNC is still there, but is non-responsive (locked up/frozen).
hyperv enlightenment perhaps makes a difference? It's only partially in 3.5. But try disable it for that OS type in osinfo config
Do they have rhel 7 based hypervisor? Worth a try, it may not happen there
Michal, I'll be glad to ask the customer to test under these conditions. Can you confirm how the customer would disable it? Is this under the Edit->Operating System options for the VM or is this in the /etc/ovirt-engine/osinfo.conf.d/00-defaults.properties file on the manager? And if it's in that file, what exactly are we setting and/or changing?
See also issues mentioned in bug 1163828 and associated patch. It is supposedly disabled in 3.5.6 already, just switch it regardless what it is now. There were some contradictory reports about the effect.
Trying on RHEL 7 might make a big difference too
Thanks. Well, time to try to enable hyperv flag or (better) run on 7.2 hypervisor