[Top][All Lists]

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

Re: [qemu-s390x] [Qemu-devel] [RFC PATCH 1/1] s390x/css: unresrict cssid

From: Boris Fiuczynski
Subject: Re: [qemu-s390x] [Qemu-devel] [RFC PATCH 1/1] s390x/css: unresrict cssids
Date: Tue, 28 Nov 2017 12:49:04 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0

On 11/28/2017 11:22 AM, Cornelia Huck wrote:
On Tue, 28 Nov 2017 09:53:15 +0100
Boris Fiuczynski <address@hidden> wrote:

On 11/27/2017 05:56 PM, Cornelia Huck wrote:
Proposal 2: Export the default cssid as a machine property. If this
property exists, it also implies that devices can be put into any css
image (although it makes the most sense to put them into the default
css image as indicated by the property). Can be made r/w later if it is
too much for 2.12.
Just as a side discussion:
I know of qom command query-machines but that does not seem to provide
the information you suggest to use with proposal 2.
Sorry, I meant query-command-line-options.

What qom command do you suggest to use for the introspection of the
machine options access mode?

Is qom-get what you are looking for?

virsh # qemu-monitor-command vm1 --pretty '{ "execute": "qom-get", "arguments": { "path": 
"/machine/", "property": "accel"} }'
   "return": "kvm",
   "id": "libvirt-18"

How do you find out from returned values that accel is r/o or r/w?

Mit freundlichen Grüßen/Kind regards
   Boris Fiuczynski

IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Martina Köderitz
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

reply via email to

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