Description of problem:
Boot the guest with multiple tap devices which contains at least a virtio tap device, and then ifdown one NIC card will cause another NIC card down as well.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. boot the guest with two NIC devices which contains a virtio NIC card
2. after the guest booted up, ifdown one NIC card
3. another NIC devices is down as well which means the network broken
Both tap devices down if only ifdown one of them in guest
The other tap device should survive after ifdown one
Reference bug #505232 comment #6
What's the qemu cmdline? It is weird that the tap state was changed.
Development Management has reviewed and declined this request. You may appeal
this decision by reopening this request.
(In reply to comment #1)
> What's the qemu cmdline? It is weird that the tap state was changed.
Sorry for the late reply. As referred in this bug description, the FULL command line could be found in bug #505232, and I also would paste it here:
#/usr/libexec/qemu-kvm -name 'vm1' -drive
-uuid 4b66fdbe-b86d-42f3-8efd-76db26aaedb6 -net
tap,vlan=2,ifname=test3,script=/etc/qemu-ifup-switch,downscript=no -m 2048 -smp
2 -vnc :0
Seems this problem still exists but I'm not sure. Yeah it's weird and important for keep guest's network stable I think. Do you think we need to reopen it?
Are you running STP on the bridge? It might be the cause. We use stp off by default.