From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:50304)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <dmantipov@yandex.ru>) id 1Xxzny-0006mn-LM
	for qemu-devel@nongnu.org; Mon, 08 Dec 2014 10:01:01 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <dmantipov@yandex.ru>) id 1Xxznp-0000LH-5z
	for qemu-devel@nongnu.org; Mon, 08 Dec 2014 10:00:54 -0500
Received: from forward2o.mail.yandex.net ([37.140.190.31]:32949)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <dmantipov@yandex.ru>) id 1Xxzno-0000IM-Hy
	for qemu-devel@nongnu.org; Mon, 08 Dec 2014 10:00:45 -0500
Received: from smtp4o.mail.yandex.net (smtp4o.mail.yandex.net [37.140.190.29])
	by forward2o.mail.yandex.net (Yandex) with ESMTP id A03AF4860AC8
	for <qemu-devel@nongnu.org>; Mon,  8 Dec 2014 18:00:41 +0300 (MSK)
Received: from smtp4o.mail.yandex.net (localhost [127.0.0.1])
	by smtp4o.mail.yandex.net (Yandex) with ESMTP id 6E3A923230EF
	for <qemu-devel@nongnu.org>; Mon,  8 Dec 2014 18:00:41 +0300 (MSK)
Message-ID: <5485BD18.1050303@yandex.ru>
Date: Mon, 08 Dec 2014 18:00:40 +0300
From: Dmitry Antipov <dmantipov@yandex.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Redundant VDE network
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: qemu-devel@nongnu.org

(This is a partial repost from qemu-discuss@ list since I'm suspecting a bug)

I'm using QEMU 2.1.1 to emulate SPARC system and have vde network between two
VMs and host system, organized as shown:

               host
               tap0
         + 192.168.100.254 +
         |                 |
         |                 |
         vm0               vm1
         eth0              eth0
     192.168.100.1 --- 192.168.100.2

On host, I'm running vde_switch and extra stuff as:

vde_switch -tap tap0 -daemon -mod 660 -group [group]
ip addr add 192.168.100.254/24 dev tap0
ip link set tap0 up
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -t nat -A POSTROUTING -s 192.168.100.0/24 -o [external network iface] -j MASQUERADE

VMs are running with:

qemu-system-sparc -m 256 -net nic -net vde -hda vm0.img
qemu-system-sparc -m 256 -net nic -net vde -hda vm1.img

Everything looks good, but...

...the problem: I need to build redundant network by using the same method, i.e.
improve the network shown above with:

               host
               tap1
         + 192.168.101.254 +
         |                 |
         |                 |
         vm0               vm1
         eth1              eth1
     192.168.101.1 --- 192.168.101.2

I'm trying to run two vde switches:

vde_switch -sock /tmp/vde0 -tap tap0 -daemon -mod 660 -group [group]
vde_switch -sock /tmp/vde1 -tap tap1 -daemon -mod 660 -group [group]

and run VMs with:

qemu-system-sparc -m 256 -net nic,vlan=0 -net vde,sock=/tmp/vde0,vlan=0 -net nic,vlan=1 -net vde,sock=/tmp/vde1,vlan=1 -hda vm0.img

but the result is:

Warning: hub port hub1port0 has no peer
Warning: vlan 1 with no nics
Warning: netdev hub1port0 has no peer
Warning: requested NIC (anonymous, model unspecified) was not created (not supported by this machine?)

Is this a bug? In general, what's the best method to build redundant network?

Thanks in advance,
Dmitry