From: "Andreas Färber" <afaerber@suse.de>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: ghammer@redhat.com, Igor Mammedov <imammedo@redhat.com>,
qemu-devel@nongnu.org, David Gibson <dgibson@redhat.com>
Subject: Re: [Qemu-devel] [PATCH V14 2/3] pc: add a Virtual Machine Generation ID device
Date: Wed, 04 Mar 2015 15:03:29 +0100 [thread overview]
Message-ID: <54F710B1.7040101@suse.de> (raw)
In-Reply-To: <20150304134900.GA29478@redhat.com>
Am 04.03.2015 um 14:49 schrieb Michael S. Tsirkin:
> On Wed, Mar 04, 2015 at 02:12:32PM +0100, Igor Mammedov wrote:
>> On Wed, 4 Mar 2015 13:11:48 +0100
>> "Michael S. Tsirkin" <mst@redhat.com> wrote:
>>> On Tue, Mar 03, 2015 at 09:33:51PM +0100, Igor Mammedov wrote:
>>>> On Tue, 3 Mar 2015 18:35:39 +0100
>>>> "Michael S. Tsirkin" <mst@redhat.com> wrote:
>>>>> On Tue, Mar 03, 2015 at 05:18:14PM +0100, Igor Mammedov wrote:
>>>>>> To change uuid in runtime use:
>>>>>> qom-set "/machine/peripheral/FOO.uuid"
>>>>>> "124e6eaf-d1d1-4bf6-bf41-b9bb6c91fb87"
>>>>>
>>>>> Looking just at this, how does user discover this functionality?
>>>> what do you mean?
>>>>
>>>> [...]
>>>
>>> Just this. You are a user. You want to change the vm gen id.
>>> Adding devices is partially documented
>>> in -help and -device help. commands are documented in hmp help.
>>> But how do you find out that qom-set should be used to
>>> update vm gen id, and how do you find out how to do this?
>> I don't really know, it's approach used in original patches.
>> Any suggestions?
>> Do QOM properties have some 'help' connected to them? If yes we
>> could stick explanation there so that -device vmgenid,help
>> would show it at least.
>
> Eric, Andreas, any comments on this part?
Since recently there is some function to add a description to either
qdev or QOM properties, I don't quite remember where exactly...
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton; HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2015-03-04 14:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 16:18 [Qemu-devel] [PATCH V14 0/3] Virtual Machine Generation ID Igor Mammedov
2015-03-03 16:18 ` [Qemu-devel] [PATCH V14 1/3] docs: vm generation id device's description Igor Mammedov
2015-03-04 19:57 ` Eric Blake
2015-03-03 16:18 ` [Qemu-devel] [PATCH V14 2/3] pc: add a Virtual Machine Generation ID device Igor Mammedov
2015-03-03 17:35 ` Michael S. Tsirkin
2015-03-03 20:33 ` Igor Mammedov
2015-03-04 12:11 ` Michael S. Tsirkin
2015-03-04 13:12 ` Igor Mammedov
2015-03-04 13:49 ` Michael S. Tsirkin
2015-03-04 14:03 ` Andreas Färber [this message]
2015-03-04 15:14 ` Igor Mammedov
2015-03-04 15:31 ` Michael S. Tsirkin
2015-03-04 16:33 ` Igor Mammedov
2015-03-04 19:12 ` Michael S. Tsirkin
2015-03-05 14:22 ` Igor Mammedov
2015-03-11 5:35 ` David Gibson
2015-03-19 9:50 ` Michael S. Tsirkin
2015-03-19 11:31 ` Gal Hammer
2015-03-20 4:58 ` David Gibson
2015-03-03 16:18 ` [Qemu-devel] [PATCH V14 3/3] tests: add a unit test for the vmgenid device Igor Mammedov
2015-04-15 10:38 ` [Qemu-devel] [PATCH V14 0/3] Virtual Machine Generation ID Michael S. Tsirkin
2015-04-15 13:59 ` Igor Mammedov
2015-04-19 7:52 ` Michael S. Tsirkin
2015-04-19 13:38 ` Yan Vugenfirer
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=54F710B1.7040101@suse.de \
--to=afaerber@suse.de \
--cc=dgibson@redhat.com \
--cc=ghammer@redhat.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.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).