On Fri, Jul 26, 2013 at 10:43:44AM +0100, Peter Maydell wrote: > On 26 July 2013 10:25, Stefan Hajnoczi <stefa...@gmail.com> wrote: > > On Thu, Jul 25, 2013 at 05:53:06PM +0300, Michael S. Tsirkin wrote: > >> On Thu, Jul 25, 2013 at 03:12:31PM +0100, Peter Maydell wrote: > >> > On 25 July 2013 03:08, Anthony Liguori <anth...@codemonkey.ws> wrote: > >> > > We really ought to strongly deprecate -net because it's misleading. > >> > > >> > ...we still need to figure out how -netdev is supposed to > >> > work for embedded (created-by-default) network devices first. > > >> I guess it could work just like -net does: assume a default netdev name? > > (for clarity, rather than as an argument against this idea) > This isn't how -net works : "-net nic,options" sets up an > entry in the nd_table[], and the board will then pick up those > entries based on some ad-hoc combination of order and whether > a model= was specified for that nic. > > > Sounds like a simple way to solve it, as long as machines use the > > standard name(s) for build-in NICs. > > How would this work for (for example) specifying a macaddr > for the built-in NIC? At the moment you can do that with > -net nic,macaddr=<whatever>. > > -- PMM
ATM you can use -global for that. We generally need a way to specify properties for built-in devices by path. -- MST
