[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: |
Stefan Hajnoczi |
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 10:51:03 +0100 |
User-agent: |
Mutt/1.8.0 (2017-02-23) |
On Tue, Apr 11, 2017 at 02:53:00PM +0200, Markus Armbruster wrote:
> Stefan Hajnoczi <address@hidden> writes:
>
> > On Mon, Mar 27, 2017 at 01:49:44PM +0100, Peter Maydell wrote:
> >> On 27 March 2017 at 13:01, Stefan Hajnoczi <address@hidden> wrote:
> >> > It would be nice to get rid of the legacy -net option in 3.0.0. I have
> >> > added it and included pointers to loose ends. I think this is doable
> >> > but will require some time to achieve.
> >>
> >> What's the syntax for using -netdev with embedded network
> >> devices that you can't create with -device ?
> >> (We should document this at
> >> http://wiki.qemu-project.org/Documentation/Networking)
> >
> > I mentioned that on the wiki. This isn't an option we can drop easily.
> > Work is necessary to make -netdev a complete replacement or to remove
> > the legacy stuff from -net.
>
> 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.
signature.asc
Description: PGP signature