[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v3 00/30] qapi/qom: QAPIfy --object and object-add
From: |
Peter Krempa |
Subject: |
Re: [PATCH v3 00/30] qapi/qom: QAPIfy --object and object-add |
Date: |
Wed, 10 Mar 2021 15:48:39 +0100 |
User-agent: |
Mutt/2.0.5 (2021-01-21) |
On Wed, Mar 10, 2021 at 15:31:57 +0100, Paolo Bonzini wrote:
> On 10/03/21 15:22, Peter Krempa wrote:
> > I've stumbled upon a regression with this patchset applied:
> >
> > error: internal error: process exited while connecting to monitor:
> > qemu-system-x86_64: -object
> > memory-backend-ram,id=pc.ram,size=1048576000,host-nodes=0,policy=bind:
> > Invalid parameter type for 'host-nodes', expected: array
>
> This is the magic conversion of "string containing a list of integers" to
> "list of integers".
>
> The relevant code is in qapi/string-input-visitor.c, but I'm not sure where
> to stick it in the keyval-based parsing flow (i.e.
> qobject_input_visitor_new_keyval). Markus, any ideas?
I've got a slightly off-topic question/idea.
Would it be reasonably easy/straightforward to run qemu's init code
which parses arguments and possibly validates them but quit before
actually starting to initiate resources?
The use case would be to plug it (optionally?) into libvirt's
qemuxml2argvtest to prevent such a thing from happening.
It's not feasible to run all the configurations we have with a real VM
but a partial validation would possibly make sense if it's easy enough.
- [PATCH v3 29/30] vl: QAPIfy -object, (continued)
- [PATCH v3 29/30] vl: QAPIfy -object, Kevin Wolf, 2021/03/08
- [PATCH v3 16/30] qapi/qom: Add ObjectOptions for input-*, Kevin Wolf, 2021/03/08
- [PATCH v3 22/30] qom: Factor out user_creatable_process_cmdline(), Kevin Wolf, 2021/03/08
- [PATCH v3 26/30] qemu-img: Use user_creatable_process_cmdline() for --object, Kevin Wolf, 2021/03/08
- [PATCH v3 30/30] qom: Drop QemuOpts based interfaces, Kevin Wolf, 2021/03/08
- [PATCH v3 15/30] qapi/qom: Add ObjectOptions for confidential-guest-support, Kevin Wolf, 2021/03/08
- Re: [PATCH v3 00/30] qapi/qom: QAPIfy --object and object-add, Peter Krempa, 2021/03/10
- Re: [PATCH v3 00/30] qapi/qom: QAPIfy --object and object-add, Paolo Bonzini, 2021/03/10
- Re: [PATCH v3 00/30] qapi/qom: QAPIfy --object and object-add,
Peter Krempa <=
- Re: [PATCH v3 00/30] qapi/qom: QAPIfy --object and object-add, Kevin Wolf, 2021/03/10
- Re: [PATCH v3 00/30] qapi/qom: QAPIfy --object and object-add, Peter Krempa, 2021/03/11
- Re: [PATCH v3 00/30] qapi/qom: QAPIfy --object and object-add, Paolo Bonzini, 2021/03/11
- Re: [PATCH v3 00/30] qapi/qom: QAPIfy --object and object-add, Kevin Wolf, 2021/03/11
- Re: [PATCH v3 00/30] qapi/qom: QAPIfy --object and object-add, Peter Krempa, 2021/03/11
- Re: [PATCH v3 00/30] qapi/qom: QAPIfy --object and object-add, Kevin Wolf, 2021/03/11
- Re: [PATCH v3 00/30] qapi/qom: QAPIfy --object and object-add, Peter Krempa, 2021/03/11
- Re: [PATCH v3 00/30] qapi/qom: QAPIfy --object and object-add, Markus Armbruster, 2021/03/11
- Re: [PATCH v3 00/30] qapi/qom: QAPIfy --object and object-add, Paolo Bonzini, 2021/03/11
- Re: [PATCH v3 00/30] qapi/qom: QAPIfy --object and object-add, Kevin Wolf, 2021/03/11