From: Anthony PERARD <anthony.perard@citrix.com>
To: Xen Devel <xen-devel@lists.xen.org>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Anthony PERARD <anthony.perard@citrix.com>
Subject: [PATCH 0/2] Handle xen_platform_pci=0 case
Date: Fri, 22 Nov 2013 15:13:09 +0000 [thread overview]
Message-ID: <1385133191-23033-1-git-send-email-anthony.perard@citrix.com> (raw)
Hi,
Here is a little series that attempt to fix the issue regarding
xen_platform_pci=0 not been handled.
There are two patches, the first one adds an option to specifies the QEMU
machine that a user wants and we handle the xen_platform_pci=0 case using the
new option.
The new options "qemu_machine_override" will help if one want to try a q35
based device model. Otherwise, it will be used by libxl to switch to the "pc"
machine instead of the "xenfv" one when necessary, as the only difference
between both (since QEMU 1.6) is the presence of the xen-platform pci device.
Regards,
Anthony PERARD (2):
libxl: adding support to use -machine option of QEMU.
libxl: Handle xen_platform_pci=0 case with qemu-xen.
tools/libxl/libxl_dm.c | 31 +++++++++++++++++++++++++++++--
tools/libxl/libxl_types.idl | 1 +
tools/libxl/xl_cmdimpl.c | 3 +++
3 files changed, 33 insertions(+), 2 deletions(-)
--
Anthony PERARD
next reply other threads:[~2013-11-22 15:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 15:13 Anthony PERARD [this message]
2013-11-22 15:13 ` [PATCH 1/2] libxl: adding support to use -machine option of QEMU Anthony PERARD
2013-11-29 12:29 ` Stefano Stabellini
2013-11-22 15:13 ` [PATCH 2/2] libxl: Handle xen_platform_pci=0 case with qemu-xen Anthony PERARD
2013-11-29 12:31 ` Stefano Stabellini
2013-11-29 12:49 ` Fabio Fantoni
[not found] ` <20131122151838.GA10855@perard.uk.xensource.com>
2013-11-22 15:30 ` Processed: Re: [PATCH 0/2] Handle xen_platform_pci=0 case xen
2013-11-22 15:49 ` Fabio Fantoni
2013-11-22 16:54 ` Anthony PERARD
2013-11-25 9:04 ` Fabio Fantoni
2013-11-25 11:11 ` Anthony PERARD
2013-11-29 16:06 ` Fabio Fantoni
2013-11-29 16:20 ` Sander Eikelenboom
2013-11-26 19:08 ` Konrad Rzeszutek Wilk
2013-11-26 20:09 ` Konrad Rzeszutek Wilk
2013-11-28 16:14 ` Anthony PERARD
2013-11-22 15:56 ` Ian Campbell
2013-11-22 17:18 ` Anthony PERARD
2013-11-22 17:23 ` Ian Campbell
2013-11-22 17:31 ` Ian Campbell
2013-11-22 17:40 ` Anthony PERARD
2013-11-22 17:24 ` George Dunlap
2013-11-22 17:06 ` George Dunlap
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=1385133191-23033-1-git-send-email-anthony.perard@citrix.com \
--to=anthony.perard@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@citrix.com \
--cc=xen-devel@lists.xen.org \
/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).