[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Confused by QOM: /machine/unattached/device[5]/dr-conne

From: Andreas Färber
Subject: Re: [Qemu-devel] Confused by QOM: /machine/unattached/device[5]/dr-connector[255]/fdt
Date: Wed, 9 Sep 2015 16:46:05 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0

Hi Markus,

Am 09.09.2015 um 16:38 schrieb Markus Armbruster:
> I ran into this:
>     $ qemu-system-ppc64 -nodefaults -S -display none -monitor stdio -machine 
> pseries-2.4
>     QEMU 2.4.50 monitor - type 'help' for more information
>     (qemu) qom-list /machine/unattached/device[5]/dr-connector[255]
>     fdt (struct)
>     entity-sense (uint32)
>     name (string)
>     connector_type (uint32)
>     index (uint32)
>     id (uint32)
>     allocation-state (uint32)
>     indicator-state (uint32)
>     isolation-state (uint32)
>     parent_bus (link<bus>)
>     hotplugged (bool)
>     hotpluggable (bool)
>     realized (bool)
>     type (string)
>     (qemu) qom-list /machine/unattached/device[5]/dr-connector[255]/fdt
>     Device '/machine/unattached/device[5]/dr-connector[255]/fdt' not found
> According to the first qom-list, .../fdt exists.  According to the
> second, it doesn't.

Actually this is fully expected: qom-list operates on QOM objects. The
fdt property returns a struct, which is considered a value QOM-wise, so
to read it you need to use qom-get, not qom-list.

Now, it may well be that visiting a struct does not work as expected, I
remember we ran into issues there, that held up the qom-tree stuff...


SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]