From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jim Fehlig Subject: Re: [PATCH 03/28] libxl: Provide libxl__dm_support_* Date: Mon, 11 Jan 2016 10:00:43 -0700 Message-ID: <5693DFBB.7050701@suse.com> References: <1450809903-3393-1-git-send-email-ian.jackson@eu.citrix.com> <1450809903-3393-4-git-send-email-ian.jackson@eu.citrix.com> <1452186813.21055.262.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1452186813.21055.262.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell , Ian Jackson , xen-devel@lists.xensource.com Cc: Wei Liu , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On 01/07/2016 10:13 AM, Ian Campbell wrote: > On Tue, 2015-12-22 at 18:44 +0000, Ian Jackson wrote: >> This allows code elsewhere in libxl to find out what options a device >> model executable supports. This is done by searching the usage >> message for fixed strings. > Has anyone (ever, not necessarily a Xen person nor in this context) > approached upstream QEMU about a machine readable output of some sort? > > I know libvirt does something similar to this, but they want to support > older versions, whereas we at least have the luxury of not caring about > versions before the point this code lands. Since qemu 1.2.0, libvirt has been using the various QMP commands to probe for qemu capabilities, instead of parsing help output. Regards, Jim