Greetings Markus, Thank you very much for the information. I will review the bugzilla that you attached.
Thank you. 2014-08-08 10:39 GMT-04:30 Markus Stockhausen <[email protected]>: > Hi, > > will be fixed in 3.5. In advance you should set hv_relaxed options via > hook. > See: https://bugzilla.redhat.com/show_bug.cgi?id=1110305 > > Best regards. > > Markus > ------------------------------ > *Von:* [email protected] [[email protected]]" im Auftrag von > "Carlos Castillo [[email protected]] > *Gesendet:* Freitag, 8. August 2014 16:54 > *An:* users > *Betreff:* [ovirt-users] BSoD in windows servers V.M due the processor > Class > > 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 > > -- Carlos J. Castillo ---------------------------------------------------------------------------------- Ingeniero de Soluciones de TI +58 426 2542313 @Dr4g0nKn1ght
_______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
