I came back to this again, and I can confirm I still get the same on a
later edition of openvswitch..
Over here I issued,
ovs-vsctl add-port <bridge name> <tap dev> -- set Interface <tap dev>
type=tap
then
ifconfig -a , which would show it is created in the "down" state
applying, ip link set <tap device> up ..
I check what's set with with 'ovs-vsctl show',
A VM gets started and tries to use this tap device, but it stops short
with an error message,
"dev/net/tun (<tap device>): Device or resource busy"
So the tap device gets created and can be configured but the VM
application fails to attach to it. Tried on two different hypervisor
stations and the same outcome
I can start VMs attaching to tuntaps&ovs bridges without issue but as
long as "ip tuntap" is used.
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
