'CLOCK_WATCHDOG_TIMEOUT (101)' BSOD on Windows KVM guests

Solution Verified - Updated -

Issue

Windows guests running on KVM hosts produce BSODs with the following error:

CLOCK_WATCHDOG_TIMEOUT (101)

An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts.

Environment

• Red Hat Enterprise Linux (RHEL) 5 KVM host
• Red Hat Enterprise Linux 6.4 (or earlier) KVM host
• Microsoft Windows guests

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.