From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:45935)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <thuth@redhat.com>) id 1a8sXx-0001fI-Tf
	for qemu-devel@nongnu.org; Tue, 15 Dec 2015 11:33:58 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <thuth@redhat.com>) id 1a8sXs-0007tQ-Sp
	for qemu-devel@nongnu.org; Tue, 15 Dec 2015 11:33:53 -0500
Received: from mx1.redhat.com ([209.132.183.28]:35247)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <thuth@redhat.com>) id 1a8sXs-0007sV-NX
	for qemu-devel@nongnu.org; Tue, 15 Dec 2015 11:33:48 -0500
References: <1450179992-15959-1-git-send-email-thuth@redhat.com>
	<56700CBA.5010505@redhat.com>
	<CAFEAcA_E+vDpOmM-oV1nxheJtiUMhHYYVvQXNwz+mmYNMhwYig@mail.gmail.com>
From: Thomas Huth <thuth@redhat.com>
Message-ID: <567040E8.3000605@redhat.com>
Date: Tue, 15 Dec 2015 17:33:44 +0100
MIME-Version: 1.0
In-Reply-To: <CAFEAcA_E+vDpOmM-oV1nxheJtiUMhHYYVvQXNwz+mmYNMhwYig@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH] net: Inform the user about deprecated -net
 options
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Peter Maydell <peter.maydell@linaro.org>, Paolo Bonzini <pbonzini@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>, QEMU Developers <qemu-devel@nongnu.org>

On 15/12/15 17:17, Peter Maydell wrote:
> On 15 December 2015 at 12:51, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> Honestly, I still do not believe that they will be removed.  They are
>> little more than syntactic sugar at this point.
> 
> If they're just syntactic sugar, what is the new-style command
> line mechanism for configuring boards with embedded network
> controller devices? Last time I looked at this that was just
> impossible...and as long as it is, you can't get rid of any
> of the backend -net config either, because it has to be either
> all -net or all new-style and not a mix (I think).

No, you can use "-netdev user,id=mynet -net nic,netdev=mynet" for
example to wire an embedded network controller to a netdev device, so
that's not a problem anymore.

 Thomas