[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] VLAN problem

  • To: Xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Urs Golla" <urs.golla@xxxxxxxxx>
  • Date: Fri, 18 Jan 2008 08:49:03 +0100
  • Delivery-date: Thu, 17 Jan 2008 23:49:27 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=MRYlOdOJp1x8X8lvvW9oQ+s3U7EKHtegpZCHwhjJNxLMD/Vzs4PZ3ojXm/0PUeISd1xaLLbxF8IB/NDLeGRRnb61ll1ijNmwiUfd1Z8kKSW9C9REz2CzrTB44Ixxm1vHMnAUnNSeeg8je2EHr1Qj28JTfYhe0jQ1EtlLAiIdzkY=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi all

I have a DOM-0 running with 2 network interfaces and one bond0
interface for load balancing and failover. This works perfect. But now
i have to use VLAN tagging to be able to reach our backup-network.
This is working on a standard server but not on my DOM-0. If I try to
start the bond0.xxx it says that "device bond0.xxx does not seem to be

Is VLAN tagging (with or without bonding) possible at all?

I am using RHEL5 with xen-3.0.3 and xen kernel 2.6.18-8


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.