On Wed, 2014-12-10 at 08:51 +0800, tlau@xxxxxxxxxxxxxxxxxx wrote: > Hi, > > Anything you want me to try on my side? > There is an open bug in bugzilla which looks pretty similar to your problem https://bugzilla.redhat.com/show_bug.cgi?id=1139928 Please take a look at comment #18 posted by Eduardo https://bugzilla.redhat.com/show_bug.cgi?id=1139928#c18 Best regards, Vadim. > Sent from my BlackBerry 10 smartphone. > > Thomas Lau > Director of Infrastructure > Tetrion Capital Limited > > Direct: +852-3976-8903 > Mobile: +852-9323-9670 > Address: 20/F, IFC 1, Central district, Hong Kong > Original Message > From: Thomas Lau > Sent: Tuesday, 9 December, 2014 4:24 PM > To: Vadim Rozenfeld > Cc: Zhang Haoyu; kvm; imammedo > Subject: Re: Windows 7 VM BSOD > > Hi Vadim, > > Now turning on is OK somehow, shutdown still stuck. > > On Tue, Dec 9, 2014 at 4:03 PM, Vadim Rozenfeld <vrozenfe@xxxxxxxxxx> wrote: > > On Tue, 2014-12-09 at 15:54 +0800, Thomas Lau wrote: > >> I changed CPU type to Westmere, it boot up with 0x05C BSOD > > > > It should be four parameters printed on the screen, right below > > the error code string. Could you please post them? > > > > Vadim. > > > >> > >> On Tue, Dec 9, 2014 at 3:10 PM, Vadim Rozenfeld <vrozenfe@xxxxxxxxxx> wrote: > >> > On Tue, 2014-12-09 at 11:54 +0800, Thomas Lau wrote: > >> >> Hi Vadim, > >> >> > >> >> I want to quote back to your original post back in early 2014: > >> >> https://www.mail-archive.com/kvm@xxxxxxxxxxxxxxx/msg99782.html > >> >> > >> >> > >> >> According to http://msdn.microsoft.com/en-us/library/windows/hardware/ff559069(v=vs.85).aspx > >> >> the 0x5C means HAL_INITIALIZATION_FAILED > >> >> > >> >> Problem matched exactly, which I am using CPU IvyBridge-EP and I got > >> >> same BSOD as well. > >> > > >> > Some CPU flags (feature bits) should be missing. > >> > Can you try changing cpu type? > >> > > >> > Best regards, > >> > Vadim. > >> > > >> >> > >> >> Are we missing some hyperv feature? > >> >> > >> >> On Wed, Dec 3, 2014 at 7:29 PM, Vadim Rozenfeld <vrozenfe@xxxxxxxxxx> wrote: > >> >> > If you run WS2008(R2) or Win7 - always turn on relaxed timing. Otherwise > >> >> > it's just a matter of time when you hit 101 BOSD. > >> >> > Bugcheck 78 is quite rare one. What is your setup, and how easy it's > >> >> > reproducible? > >> >> > > >> >> > Best regards, > >> >> > Vadim. > >> >> > > >> >> > On Wed, 2014-12-03 at 19:13 +0800, Thomas Lau wrote: > >> >> >> "it works on your side" meaning that you had such issue but afterwards > >> >> >> it's all fixed by apply hv_relaxed ? > >> >> >> > >> >> >> On Wed, Dec 3, 2014 at 7:08 PM, Zhang Haoyu <zhanghy@xxxxxxxxxxx> wrote: > >> >> >> >> https://bugzilla.redhat.com/show_bug.cgi?id=893857 > >> >> >> >> > >> >> >> >> In fact I am doing testing now, but are we fixing one problem and > >> >> >> >> introduce other problem?! > >> >> >> >> > >> >> >> > I'm not sure about this, but it works on my side, > >> >> >> > I think BSOD(error:0x00000078) has been fixed, > >> >> >> > please show your environment. > >> >> >> > > >> >> >> > Thanks, > >> >> >> > Zhang Haoyu > >> >> >> >> On Wed, Dec 3, 2014 at 6:36 PM, Thomas Lau <tlau@xxxxxxxxxxxxxxxxxx> wrote: > >> >> >> >> > Hi, > >> >> >> >> > > >> >> >> >> > How do I know if my qemu-kvm version support this? > >> >> >> >> > > >> >> >> >> > On Wed, Dec 3, 2014 at 6:25 PM, Zhang Haoyu <zhanghy@xxxxxxxxxxx> wrote: > >> >> >> >> >>> Hi All, > >> >> >> >> >>> > >> >> >> >> >>> I am running 3.13.0-24-generic kernel on Ubuntu 14, Windows 7 VM > >> >> >> >> >>> installation was fine, but it does random reboot by itself, the error > >> >> >> >> >>> code is 0x00000101, does anyone know how to fix this? > >> >> >> >> >> Could you try hv_relaxed, like "-cpu kvm64,hv_relaxed". > >> >> >> >> >> > >> >> >> >> >> Thanks, > >> >> >> >> >> Zhang Haoyu > >> >> >> > > >> >> >> -- > >> >> >> To unsubscribe from this list: send the line "unsubscribe kvm" in > >> >> >> the body of a message to majordomo@xxxxxxxxxxxxxxx > >> >> >> More majordomo info at http://vger.kernel.org/majordomo-info.html > >> >> > > >> >> > > >> >> > >> >> > >> >> > >> > > >> > > >> > >> > >> > > > > > > > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
