<div dir="ltr"><div>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. <br></div>
<div><br></div><div>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. </div><div><br></div><div>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). </div>
<div><br></div><div>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.</div>
<div><br></div><div><br></div><div>Thanks in advance<br></div><div><br></div>-- <br><div dir="ltr">Carlos J. Castillo<br>----------------------------------------------------------------------------------<br>Ingeniero de Soluciones de TI<br>
<a href="tel:%2B58%20426%202542313" value="+584262542313" target="_blank">+58 426 2542313</a><br>
@Dr4g0nKn1ght<br><br><img src="https://lh3.googleusercontent.com/-9rJ4Hxskzqo/T8z4gW054WI/AAAAAAAABWg/JKK3KzFe8jk/s128/qr.png" height="95" width="96"></div>
</div>