This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] Fully virtualized domU Linux network (VLAN) trouble

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Fully virtualized domU Linux network (VLAN) trouble
From: Jan Bakuwel <jan.bakuwel@xxxxxxxxx>
Date: Thu, 30 Jul 2009 17:30:05 +1200
Delivery-date: Wed, 29 Jul 2009 22:30:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A6F0381.3000806@xxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4A6F0381.3000806@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20090608)

After some more experiments I have now concluded that using VLANs in a
fully virtualized domU doesn't seem to work properly. It works fine if
domU is para virtualized. Even though I managed to get it to work once,
a change in the config file resulted in Xen generating new MAC addresses
and the subsequent updates to the xenstore db rendered the VM inoperable
(with its network) again. At least that's my conclusion so far.

Does anyone have any success with VLANs in fully virtualized domU's?

Debian Lenny 64 bit, Xen 3.2.1, kernel 2.6.26-2-xen-amd64, Super micro
hardware, Quad core AMD, NVIDIA MCP55 NICs.


Jan Bakuwel wrote:
> Hi,
> I have a 64bit Debian Lenny server with two physical network interfaces,
> one is connected to a switch without VLANs (eth0), the other (eth1) is
> connected to a switch with tagged VLANs (eth1). I'm running a couple of
> paravirtualized VMs that have no problem using the eth0 interface
> (bridged). I'm also running a couple of fully virtualized VMs, one being
> a Linux box (with a specific kernel); others being Windows VMs with a
> single network interface bridged to eth0. The Windows VMs are working
> fine. The (fully virtualized) Linux VM has two network interfaces
> bridged to the physical network interfaces in dom0 (ie. to both eth0 and
> eth1). This VM comes up fine, has two network interfaces as specified in
> its Xen config but is not able to use any of the networks on eth0 and
> the VLANs on eth1. The VM obviously has the vlan package installed and
> the VLAN interfaces are set up.
> So: all VMs (para Linux and full Windows) except the fully virtualized
> Linux VM are able to use the eth0 interface (no VLANs). The fully
> virtualized Linux VM is not able to use eth0 (no VLANs), nor eth1 (with
> tagged VLANs).
> I've managed to get it to work with all interfaces once (ie. eth0 and a
> few VLAN interfaces on eth1), then had to change the network config and
> lost all network connectivity after the reboot. I've also observed that
> sometimes one virtual nic can be used, sometimes the other. The only
> variable here being making changes to the vif entry in the Xen config
> file for this VM. It currently looks like:
> vif        = ['mac=03:16:3e:00:02:39, type=ioemu, bridge=eth0',
>            'mac=03:16:3E:01:00:00, type=ioemu, bridge=eth1']
> The vif interfaces are created and bridged correctly in the dom0 once
> the fully virtualized Linux domU starts.
> dom0 has no business on the VLANs so it seems preferable to setup VLANs
> in domU, not dom0. I've found a few documents that suggest to use VLANs
> in dom0, and bridge the virtual interfaces to the VLAN interfaces in
> dom0. I've spend a few hours trying to get that to work but
> unfortunately that didn't work either.
> The physical NICs are:
> 00:08.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a3)
> 00:09.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a3)
> How should I further debug/analyse this problem?
> kind regards,
> Jan
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>