From: Eduardo Habkost <ehabkost@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Xin Xiaohui <xiaohui.xin@intel.com>,
Vincent Palatin <vpalatin@chromium.org>,
Jiang Yunhong <yunhong.jiang@intel.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Rui Prior <rprior@dcc.fc.up.pt>,
Zhang Xiantao <xiantao.zhang@intel.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: vmx=on with -accel hax
Date: Mon, 9 Mar 2020 12:18:47 -0400 [thread overview]
Message-ID: <20200309161847.GD1187748@habkost.net> (raw)
In-Reply-To: <87tv331i5k.fsf@dusky.pond.sub.org>
On Thu, Mar 05, 2020 at 06:32:07AM +0100, Markus Armbruster wrote:
> Cc'ing people listed by "scripts/get_maintainer.pl -f target/i386/hax*".
>
Thanks! get_maintainer.pl output here is a bit misleading. We
have no maintainers listed for the hax accel. CCing the original
authors, hoping they can help.
> Rui Prior <rprior@dcc.fc.up.pt> writes:
>
> > Dear qemu developers,
> >
> > I found a bug/limitation of qemu on windows (qemu-w64-setup-20200201.exe
> > from https://qemu.weilnetz.de/w64/ ) that makes qemu terminate
> > immediately with "VCPU shutdown request" (twice) if I try to use the
> > "vmx=on" CPU option while simultaneously using "-accel hax". Without
> > "vmx=on", it works fine (but it prevents me from using nested
> > virtualization).
> >
> > I am using HAXM v7.5.6.
> >
I don't see any CPUID handling in the hax accel code, so "vmx=on"
isn't even supposed to have any effect. I don't think HAXM
supports nested virtualization, does it?
> > Should you need any further information, please let me know.
> >
> > Best regards,
--
Eduardo
next prev parent reply other threads:[~2020-03-09 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 17:42 vmx=on with -accel hax Rui Prior
2020-03-05 5:32 ` Markus Armbruster
2020-03-09 16:18 ` Eduardo Habkost [this message]
2020-03-09 16:31 ` Paolo Bonzini
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=20200309161847.GD1187748@habkost.net \
--to=ehabkost@redhat.com \
--cc=armbru@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rprior@dcc.fc.up.pt \
--cc=rth@twiddle.net \
--cc=vpalatin@chromium.org \
--cc=xiantao.zhang@intel.com \
--cc=xiaohui.xin@intel.com \
--cc=yunhong.jiang@intel.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.