Displaying 1 result from an estimated 1 matches for "de699bd4dc4d".
2013 Mar 07
0
Bug#702428: log output
...;
The message about
"can't add tap10.0 to bridge xapi1: Operation not supported"
seems to be the point where it fails.
xapi1 does exist and two PV domUs are connected to it already:
# brctl show xapi1
bridge name bridge id STP enabled interfaces
xapi1 0000.de699bd4dc4d no vif1.2
vif3.1
It is only the HVM domU that has this error.
Why is it talking about tap10.0 and not vif10.0 in the qemu-dm log
message? Do HVM vifs use the tapX naming convention? Or is this the
cause of the problem?
dmesg output shows that a vif10.0 did...