The subject of this email possibly suggest that I'm publishing in the wrong place but I'm not. I'm would like try to see if anyone faced a similar situation with Windows VM's.
Since the beginning of week 2 of my database servers (oVirt's VM's), are presenting a BSoD (STOP) because of a bugfix 0x00000101 CLOCK_WATCHDOG_TIMEOUT. After analyzing the minidump and make some review I found that this problem commonly occurs on Windows Server 2008 R2 installed in machine's with Intel processors Nehalan class (Xeon 5675 as we have in our solution). 99% of our Windows VM's run Windows 2008 R2, and although the situation has now generated only 2 servers affectation I wonder if exists some procedure to solve or a way to mask the processor type in the virtual machines. Thanks in advance -- Carlos J. Castillo ---------------------------------------------------------------------------------- Ingeniero de Soluciones de TI +58 426 2542313 @Dr4g0nKn1ght
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
