From: Vadim Rozenfeld <vrozenfe@redhat.com>
To: Thomas Lau <tlau@tetrioncapital.com>
Cc: Zhang Haoyu <zhanghy@sangfor.com>, kvm <kvm@vger.kernel.org>,
imammedo <imammedo@redhat.com>
Subject: Re: Windows 7 VM BSOD
Date: Wed, 03 Dec 2014 22:29:51 +1100 [thread overview]
Message-ID: <1417606191.17426.10.camel@oscar> (raw)
In-Reply-To: <CAEZt6eB4+Dn3JfmE7QFc6FHeUjk5YUuYxWL2G3MWoBvPAsRS=w@mail.gmail.com>
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@sangfor.com> 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@tetrioncapital.com> 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@sangfor.com> 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@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-12-03 11:30 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 10:18 Windows 7 VM BSOD Thomas Lau
2014-12-03 10:25 ` Zhang Haoyu
2014-12-03 10:36 ` Thomas Lau
2014-12-03 10:56 ` Thomas Lau
2014-12-03 11:08 ` Zhang Haoyu
2014-12-03 11:13 ` Thomas Lau
2014-12-03 11:29 ` Vadim Rozenfeld [this message]
2014-12-03 11:36 ` tlau
2014-12-03 12:14 ` Vadim Rozenfeld
2014-12-03 14:51 ` Thomas Lau
2014-12-03 15:05 ` Thomas Lau
2014-12-04 1:24 ` Zhang Haoyu
2014-12-04 1:34 ` Thomas Lau
2014-12-04 1:45 ` Thomas Lau
2014-12-04 2:01 ` Zhang Haoyu
2014-12-04 2:02 ` Thomas Lau
2014-12-04 2:06 ` Zhang Haoyu
2014-12-04 2:48 ` Thomas Lau
2014-12-04 4:32 ` Zhang Haoyu
2014-12-04 6:22 ` Thomas Lau
2014-12-04 6:24 ` Thomas Lau
2014-12-04 7:15 ` Zhang Haoyu
2014-12-04 8:37 ` Thomas Lau
2014-12-04 9:09 ` Thomas Lau
2014-12-04 9:19 ` Zhang Haoyu
2014-12-04 9:20 ` Thomas Lau
2014-12-04 8:36 ` Vadim Rozenfeld
2014-12-09 3:54 ` Thomas Lau
2014-12-09 7:10 ` Vadim Rozenfeld
2014-12-09 7:54 ` Thomas Lau
2014-12-09 8:03 ` Vadim Rozenfeld
2014-12-09 8:24 ` Thomas Lau
2014-12-10 0:51 ` tlau
2014-12-10 6:19 ` Vadim Rozenfeld
2014-12-10 7:42 ` Thomas Lau
2014-12-10 9:16 ` Vadim Rozenfeld
2014-12-03 11:01 ` Zhang Haoyu
2014-12-03 11:04 ` Thomas Lau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1417606191.17426.10.camel@oscar \
--to=vrozenfe@redhat.com \
--cc=imammedo@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=tlau@tetrioncapital.com \
--cc=zhanghy@sangfor.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.