public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Zhang Haoyu" <zhanghy@sangfor.com>
To: "Thomas Lau" <tlau@tetrioncapital.com>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: Windows 7 VM BSOD
Date: Wed, 3 Dec 2014 19:01:47 +0800	[thread overview]
Message-ID: <201412031901466656850@sangfor.com> (raw)
In-Reply-To: CAEZt6eD30NUQ_gWWpFxWkNrRFQKAh7r8M-CxfFMmPjOz0hL2SQ@mail.gmail.com

> Hi,
> 
> How do I know if my qemu-kvm version support this?
> 
I don't know which qemu version starts to support hv-relaxed,
but I'm sure qemu-1.4.1 and later versions support it.
qemu will report error if it dosen't support it.

Please show your qemu version.

Thanks,
Zhang Haoyu
hv-relaxed was started to support from commit 89314504, 
> 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


  parent reply	other threads:[~2014-12-03 11:01 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
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 [this message]
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=201412031901466656850@sangfor.com \
    --to=zhanghy@sangfor.com \
    --cc=kvm@vger.kernel.org \
    --cc=tlau@tetrioncapital.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox