From: anthony.perard@citrix.com
To: xen-devel@lists.xensource.com
Cc: Anthony PERARD <anthony.perard@citrix.com>,
Stefano.Stabellini@eu.citrix.com
Subject: [PATCH v2 0/3] libxl, Handle the command line options of qemu 0.12.
Date: Fri, 6 Aug 2010 18:23:42 +0100 [thread overview]
Message-ID: <1281115425-8417-1-git-send-email-anthony.perard@citrix.com> (raw)
In-Reply-To: <1280938265-12107-1-git-send-email-anthony.perard@citrix.com>
From: Anthony PERARD <anthony.perard@citrix.com>
This patch gives the ability to the libxl to handle the command line argument
of the last qemu version. I begin by checking the version of the device model
with '-h' options, '--version' is not handled in qemu-xen. If I found a version
upper than 0.12, I use the new command line argument, or else I use the old
functions to build args.
The second patch introduces a udev rule to handle tap devices and add them to
the bridge instead of using a script called by qemu.
Anthony PERARD (3):
libxl, Fix name of tap device.
libxl, Introduce the command line handler for the new qemu.
tools/hotplug, Use udev rules instead of qemu script to setup the
bridge.
tools/hotplug/Linux/vif-bridge | 20 +++--
tools/hotplug/Linux/vif-common.sh | 70 ++++++++++----
tools/hotplug/Linux/xen-backend.rules | 5 +-
tools/libxl/libxl.c | 164 ++++++++++++++++++++++++++++++++-
tools/libxl/libxl_utils.c | 78 ++++++++++++++++
tools/libxl/libxl_utils.h | 6 +
6 files changed, 312 insertions(+), 31 deletions(-)
next prev parent reply other threads:[~2010-08-06 17:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 16:11 [PATCH 0/2] libxl, Handle the command line options of qemu 0.12 anthony.perard
2010-08-04 16:11 ` [PATCH 1/2] libxl, Introduce the command line handler for the new qemu anthony.perard
2010-08-04 16:41 ` Gianni Tedesco
2010-08-04 17:24 ` Stefano Stabellini
2010-08-05 13:25 ` Anthony PERARD
2010-08-05 14:40 ` Gianni Tedesco
2010-08-05 16:45 ` Stefano Stabellini
2010-08-05 16:48 ` Gianni Tedesco
2010-08-05 18:03 ` [PATCH] Change the first line of help to add 'QEMU-DM' anthony.perard
2010-08-05 18:03 ` [PATCH v2 1/2] tools/hotplug, Use udev rules instead of qemu script to setup the bridge anthony.perard
2010-08-05 18:06 ` Anthony PERARD
2010-08-05 18:05 ` [PATCH v2 1/2] libxl, Introduce the command line handler for the new qemu anthony.perard
2010-08-04 16:11 ` [PATCH 2/2] tools/hotplug, Use udev rules instead of qemu script to setup the bridge anthony.perard
2010-08-04 17:44 ` Stefano Stabellini
2010-08-06 15:49 ` Anthony PERARD
2010-08-10 10:52 ` Ian Campbell
2010-08-06 17:23 ` anthony.perard [this message]
2010-08-06 17:23 ` [PATCH v2 1/3] libxl, Fix name of tap device anthony.perard
2010-08-06 17:23 ` [PATCH v2 2/3] libxl, Introduce the command line handler for the new qemu anthony.perard
2010-08-06 17:23 ` [PATCH v2 3/3] tools/hotplug, Use udev rules instead of qemu script to setup the bridge anthony.perard
2010-08-09 15:40 ` [PATCH v2 0/3] libxl, Handle the command line options of qemu 0.12 Stefano Stabellini
2010-08-10 15:20 ` Ian Jackson
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=1281115425-8417-1-git-send-email-anthony.perard@citrix.com \
--to=anthony.perard@citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.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).