[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v2 1/3] Rework --name to use QemuOpts
From: |
Eric Blake |
Subject: |
Re: [Qemu-devel] [PATCH v2 1/3] Rework --name to use QemuOpts |
Date: |
Tue, 11 Feb 2014 06:30:01 -0700 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 |
On 02/11/2014 02:07 AM, Paolo Bonzini wrote:
> Il 10/02/2014 17:12, Laszlo Ersek ha scritto:
>>> > I'd checked every piece of output I'd found, but hadn't found
>>> > the query-command-line-options; I think you're right there
>>> > are no other \n's in there - but also all the other .help texts
>>> > are much briefer and less chatty; maybe I need to just chop
>>> > them down to a minimum, I wonder if there is anywhere they're
>>> > ever displayed to a human?
>> I share your wondering :)
>
> I do too, but I'd wager the answer is no.
Libvirt logs the result of query-command-line-options, including the
human portion associated with the details. And libvirt also exposes the
'virsh qemu-monitor-command' backdoor which can be used by developers to
get at the human-readable information in this query. I _have_ called
query-command-line-options to see what it output, and did appreciate the
human text available there.
But you are correct that in the day-to-day operation of libvirtd, the
human text is ignored - it's there mainly for developers.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature