From: Ian Campbell <Ian.Campbell@eu.citrix.com>
To: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Cc: Vincent Hanquez <Vincent.Hanquez@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: xl vs. xm: floppy support
Date: Tue, 1 Mar 2011 20:29:01 +0000 [thread overview]
Message-ID: <1299011341.21399.10.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.00.1103011759440.2917@kaball-desktop>
On Tue, 2011-03-01 at 18:00 +0000, Stefano Stabellini wrote:
> On Tue, 1 Mar 2011, Ian Jackson wrote:
> > Ian Campbell writes ("Re: [Xen-devel] xl vs. xm: floppy support"):
> > > On Tue, 2011-03-01 at 12:31 +0000, Vincent Hanquez wrote:
> > > > xenops support passing arbitrary extra arguments to qemu-dm, so I will
> > > > suggest someone add the same feature to xl.
> > >
> > > libxl has the support but it's not plumbed through to xl :-(
> >
> > This ought to be fixed for 4.1 I think. It's quite an important
> > escape hatch.
> >
>
> I am ok with having this in 4.1.
> At this point we could have the two lines fix to support dm_args as well
> (libxenlight already supports optional device model arguments, we just
> need to parse dm_args in xl).
I think that's the "escape hatch" Ian was referring to.
I'll knock up a patch in the morning.
Ian.
next prev parent reply other threads:[~2011-03-01 20:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 9:37 xl vs. xm: floppy support Christoph Egger
2011-03-01 10:38 ` Ian Campbell
2011-03-01 12:00 ` Gianni Tedesco
2011-03-01 12:11 ` Ian Campbell
2011-03-01 12:31 ` Vincent Hanquez
2011-03-01 13:03 ` Ian Campbell
2011-03-01 17:56 ` Ian Jackson
2011-03-01 18:00 ` Stefano Stabellini
2011-03-01 20:29 ` Ian Campbell [this message]
2011-03-02 9:31 ` Ian Campbell
2011-03-02 10:03 ` Ian Campbell
2011-03-02 13:56 ` Stefano Stabellini
2011-03-03 17:09 ` Ian Jackson
2011-03-03 19:29 ` Stefano Stabellini
2011-03-03 17:07 ` 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=1299011341.21399.10.camel@localhost.localdomain \
--to=ian.campbell@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=Vincent.Hanquez@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 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.