From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46368) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZG0Nz-0005jR-Cx for qemu-devel@nongnu.org; Fri, 17 Jul 2015 03:48:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZG0Nt-0005ws-8E for qemu-devel@nongnu.org; Fri, 17 Jul 2015 03:48:47 -0400 Received: from mx1.redhat.com ([209.132.183.28]:48047) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZG0Nt-0005wo-0Z for qemu-devel@nongnu.org; Fri, 17 Jul 2015 03:48:41 -0400 Message-ID: <55A8B352.2090605@redhat.com> Date: Fri, 17 Jul 2015 09:48:34 +0200 From: Thomas Huth MIME-Version: 1.0 References: <1432322539-23719-1-git-send-email-thuth@redhat.com> <20150526125235.GJ13262@stefanha-thinkpad.redhat.com> <87egm34dk0.fsf@blackfin.pond.sub.org> <55A8A654.5070003@redhat.com> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jtIxs3lfDtnVgR06VWVEQfvvu9mGKDuaL" Subject: Re: [Qemu-devel] net: Next steps to deprecate -net List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Jason Wang , "Michael S. Tsirkin" , Markus Armbruster , Stefan Hajnoczi , QEMU Developers This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --jtIxs3lfDtnVgR06VWVEQfvvu9mGKDuaL Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 07/17/2015 09:25 AM, Peter Maydell wrote: > On 17 July 2015 at 07:53, Thomas Huth wrote: >> Ok, assuming that my "Network traffic dumping for -netdev devices" pat= ch >> series is going to solve the dumping-for-netdev problem, how do we >> tackle the remaining problems that we have to solve before we can >> deprecate -net? Does anybody have a survey of the (onboard) NICs that >> can only be configured with -net but not with -device? Could they >> nowadays be changed to work with -device, too, or are there still majo= r >> obstacles to solve first? >=20 > The problem is that "-device" says "create a new device and > configure it like this". But onboard NICs are created by > the board, so we want let the user say how to configure > those devices, not create new ones... Ok, I see ... maybe it makes sense to simply keep "-net nic" to be able to configure the default/onboard NIC, and only to remove all the other -net options instead ("-net user" etc.). The disliked vlan/hub concept could then be removed, too, since "-net nic" can be used together with "-netdev" nowadays by using something like "-net nic,netdev=3Dxxx" as far= as I know. That would clean up most points of confusion, I think, and would not cause too much code churn for the onboard NICs. Does that sound feasible? Thomas --jtIxs3lfDtnVgR06VWVEQfvvu9mGKDuaL Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJVqLNSAAoJEC7Z13T+cC21WhgP/3ig0m6WNQ39dnjuwUjoiV5d 4YBXyRvIo2uXB6A1yhiQUmXJTPQidb+hH7g/xu6quKcO+LmoRug68he6RSGaOqJd M7ciAN5ynnAAyTELU1eh7VognM66cwPNN18Ao3snnX28UaVOiZSz/zojol4SaXdl dWlXZ12qTJcRluLaMMBRnuyACfO1ZhALZsroyRYNwrJscu0XzdOCtzeqd1GYW7C4 gP1VMstIATSysf2pPmbMZ7qpSMN7vL/bu+uqpark+TsyHoTl2FnVor4ow92nEHzd 18c/3k9ukb7KCPn/bcx0hprP2V6BLrhYewOf9gIX3oa9QvWQG3BVftDPPd3NLbyR hqSXMA2lTiV76L3gsjJns70hcjoy6++MSlNgvL/Ek1geGvmlodhMCCZFu91bHScx QIvNrhNOSHwFxpMU+PRI3MyK2kaNOtQyMTeXBd1rhIRLQP6qVkmhy7tqTDgoEs0B aGDeMdmXQPuCnwl89+lkMghhI2nexMjnUYystsVqCWwe0c+LLnhEgSKww0HwD9Nz 3MnSW+eAgJm6jTXVFTqqV7cOlC6tpehSPVuxEfL1gFVJJJhEjCkUrQaYuEfiX84q gOrlxcW4ROhVlEUx1irZ8M4ywwH5GUisYD0rOSXVvzGOSMhDTBuz03+smBJSXNZz 739/PP3ssLJFHVTKyL79 =uEd6 -----END PGP SIGNATURE----- --jtIxs3lfDtnVgR06VWVEQfvvu9mGKDuaL--