[Top][All Lists]

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

Re: [Qemu-devel] What's the next QEMU version after 2.9 ? (or: when is a

From: John Snow
Subject: Re: [Qemu-devel] What's the next QEMU version after 2.9 ? (or: when is a good point in time to get rid of old interfaces)
Date: Tue, 18 Apr 2017 13:18:14 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0

On 04/18/2017 07:57 AM, Gerd Hoffmann wrote:
>   Hi,
>>> Just like -device is a general way to plug in devices, replacing
>>> multiple special ways (-net, -drive, -usb, ...), we could use a general
>>> way to configure onboard devices.
>> I looked at the -device implementation to see if the bus= parameter
>> could be used to specify onboard device addresses, but I think you may
>> be right that we need a separate command-line argument for onboard
>> devices.
> I think so.
> There is -global, which is actually used by libvirt to configure
> built-in floppy devices.  But as the name suggests it sets properties
> globally, i.e. for all instances.  Which works in this specific use
> case, as there can be only one floppy controller per machine, but I

Spec-wise, Can't you have two?

> don't think this is something we want build on.
> There is -set, but that works only for devices created via -device,
> because it operates on QemuOpts, and we don't have QemuOpts for built-in
> devices.
> We probably want something like
>   -qom-set-property {objpath|alias}.prop=value
> cheers,
>   Gerd

reply via email to

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