[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-users] network setup for HVM guests
What Distro/version and Xen version are you running? I run HVM guests with bridging and have never had this problem. To clarify, while it is true that the tap interfaces don't necessarily match the domU IDs the way the default vifX interfaces do, in my case, the bridge chosen in the HVM config file always gets both interfaces added to it (regardless of whether or not vifname is used). I haven't ever had a need to have more than one bridge, so the fact that I couldn't tell which tap interface belonged to which hvm wasn't problematic to me, that said, perhaps someone else can shed some light on some method of determining which tap interface belongs to which domU and/or what commands might affect all interfaces tied to a given domU. However, it sounds like you have a bug that needs resolving regardless. Also, FYI, if you us PV drivers (James Harper's GPLPV for Windows or the appropriate Xen kernel drivers for Linux) in your HVMs, you will go through the interfaces identified as vifX or via vifname. Also, if you are able to use install such drivers and they don't work as expected, it could (though one would certainly hope not, and I don't think it would stand to reason) be related to the fact that the vifX and tapY interfaces aren't on the same bridge, and this might be a bug as well. Dustin -----Original Message----- From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Luca Lesinigo Sent: Tuesday, August 19, 2008 22:50 To: xen-users@xxxxxxxxxxxxxxxxxxx Subject: [Xen-users] network setup for HVM guests Hello there. I'm used to xen with paravirtualized guests and am now starting to play with HVM guests. When creating an HVM guest I noted that Xen will create two new network interfaces in Dom0: the usual vifX and a new tapY. The vif one can be renamed as usual with vifname= in the config file, and gets added by xen scripts to the corresponding bridge interface (bridge=blah in config). Little problem is, no traffic appears on this interface. The interface actually 'connected' to the HVM guest is the tap one, which gets a name not associated with the domain id, name or config and doesn't get added to the bridge. Is this expected behavior in one way or another? How do you people deal with bridged networking and HVM guests (eg. how do you add interfaces to bridges and/or iptables) ? Thanks, -- Luca Lesinigo _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |