Re: [Xen-API] [Pkg-xen-devel] Bug#702428: HVM networking tap/vif bug (Debian bug 702428)

[Ian Campbell <ijc@xxxxxxxxxxxxxx>]

I'm afraid I don't know about the issue you are seeing but I can comment
on one part:

On Sun, 2013-03-17 at 15:02 +0100, Daniel Pocock wrote:
> while the output from dmesg suggests that the interface vif10.0 was
> created.  It appears there is confusion between the vifX.Y and tapX.Y
> naming schemes.

An HVM guest with a network device should get *both* vifX.Y and tapX.Y,
they are kind of two faces of the same "device". The tapX.Y is the
emulated NIC (rtl8169 or e1000 or something) while the vifX.Y is the PV
NIC which the guest can choose to switch over too (for increased perf
etc) if it has a suitable driver (e.g. Linux PVHVM support, PV drivers
for Windows etc etc).

As to why tapX.Y cannot be added to a bridge, I've no idea, sorry. Are
you using bridge or vswitch? Can you manually enslave the tap device to
the bridge?

Ian.

-- 
Ian Campbell


Put your brain in gear before starting your mouth in motion.

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api