From: Anthony PERARD <anthony.perard@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xenproject.org, Ian Jackson <ian.jackson@eu.citrix.com>
Subject: Re: [PATCH] libxl: Handle deprecation of QEMU's -usbdevice
Date: Mon, 20 Aug 2018 15:58:23 +0100 [thread overview]
Message-ID: <20180820145823.GB1256@perard.uk.xensource.com> (raw)
In-Reply-To: <20180820143258.ykk7pwrhmoto7moh@citrix.com>
On Mon, Aug 20, 2018 at 03:32:58PM +0100, Wei Liu wrote:
> On Wed, Jul 25, 2018 at 11:43:29AM +0100, Anthony PERARD wrote:
> > On Wed, Jul 25, 2018 at 09:38:20AM +0100, Wei Liu wrote:
> > > How does libvirt handle QEMU option deprecation?
> >
> > I don't think they handle it very well. I think it's basicaly when the
> > deprecated option is removed from QEMU that they notice libvirt need to
> > be fixed (That's what I got from reading a thread on qemu-devel).
>
> How do they fix this sort of things? Do they reject removed options or
> try (as best effort) to translate?
I don't think those questions make senses. What "sort of things" ? Which
"options", qemu command line/qmp options or user facing options?
In anycase, I don't think I know enough about libvirt (even as a user)
to be able to respond to those questions, but they would probably not
have exposed -usbdevice to users, like we do.
--
Anthony PERARD
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2018-08-20 14:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 17:29 [PATCH] libxl: Handle deprecation of QEMU's -usbdevice Anthony PERARD
2018-07-25 8:38 ` Wei Liu
2018-07-25 10:43 ` Anthony PERARD
2018-08-20 14:32 ` Wei Liu
2018-08-20 14:58 ` Anthony PERARD [this message]
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=20180820145823.GB1256@perard.uk.xensource.com \
--to=anthony.perard@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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).