From: Anthony PERARD <anthony.perard@citrix.com>
To: "Lan, Tianyu" <tianyu.lan@intel.com>
Cc: xen-devel@lists.xensource.com, ian.jackson@eu.citrix.com, "Dong,
Eddie" <eddie.dong@intel.com>,
"Wang, Yong Y" <yong.y.wang@intel.com>,
Stefano Stabellini <sstabellini@kernel.org>,
jbeulich@suse.com
Subject: Re: Xen Q35 & virtual VTD support
Date: Tue, 10 May 2016 15:52:42 +0100 [thread overview]
Message-ID: <20160510145242.GA5016@perard.uk.xensource.com> (raw)
In-Reply-To: <fb403518-b1dd-e11a-9723-95182f3d7ece@intel.com>
On Tue, May 10, 2016 at 10:31:38PM +0800, Lan, Tianyu wrote:
> On 5/10/2016 6:11 PM, Stefano Stabellini wrote:
> > Hello Tianyu,
> >
> > What do you mean by reusing Q35 for Xen? If you mean using QEMU to
> > emulate a Q35 based machine for HVM guests, I think that should be OK.
> >
>
> From xl code, I findit passes pc, xenpv or xenfv as "-machine" param
> to Qemu except Q35. I also tried changing code to select Q35 in the xl
> but guest didn't boot up. So I want to check whether Xen supports Q35 in
> the current code or not.
No, Xen do not support Q35.
But that is possible in the future, I did some work on it in the past, you
can find it here if you are curious:
http://xenbits.xen.org/gitweb/?p=people/aperard/xen-unstable.git;a=shortlog;h=refs/heads/machine-q35-wip
I'm not sure if it's going to help you.
--
Anthony PERARD
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-10 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 14:51 Xen Q35 & virtual VTD support Lan, Tianyu
2016-05-10 10:11 ` Stefano Stabellini
2016-05-10 14:31 ` Lan, Tianyu
2016-05-10 14:52 ` Anthony PERARD [this message]
2016-05-10 15:26 ` Lan, Tianyu
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=20160510145242.GA5016@perard.uk.xensource.com \
--to=anthony.perard@citrix.com \
--cc=eddie.dong@intel.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=sstabellini@kernel.org \
--cc=tianyu.lan@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=yong.y.wang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).