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" <m...@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" <m...@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)