WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] xen-br1

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] xen-br1
From: Sanjay Upadhyay <glowfriend@xxxxxxxxx>
Date: Fri, 3 Feb 2006 18:03:44 +0530
Delivery-date: Fri, 03 Feb 2006 12:44:42 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=qaX4XYafcF+02w+0dSdXRwxMm33c2Dzb1syp2vIa+s5cqBe1cCBQYaJTJWGLCkGN4vMIYsNqYj7LlT0fylwsZnEb1GoKbioJe+E99ui9qOFbKrS8IOq4P9YBooQspYcW6IXsLkPQIGc7cMcE3Gi9YiUrHOmWPZAzAnlW3boeHoQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <3C051DA2FCF4BC4A8E9BA485023933AA03D308@xxxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <3C051DA2FCF4BC4A8E9BA485023933AA03D308@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi Kris,
One doc that helped me a lot was this
http://wiki.xensource.com/xenwiki/HowToInstallXenOnSlackware?highlight=%28slackware%29
it explains a bit. If eth1 is a real nic, then things should work,
however in case you have two nice etho, and eth1, the bridging wouldnt
work (IMHO)...
you can try natting, without DHCP, and snat from vifx.0 which to me
seems easier.

regards


On 2/3/06, Kris Hollingsworth <Kris@xxxxxxxxxx> wrote:
>
>
> Hi, I'm setting up my first xen machine, and I'm trying to setup two Virtual
> Machines, each mapped to a physical adapter on a different network.
>
>  The virtual machine mapped to xen-br0 and eth0 works fine. However, when I
> bring up a VM with this configuration file:
>
>  -----------------
>  name = "test77"
>  kernel = "/boot/vmlinuz-2.6.11.12-xenU"
>  root = "/dev/hda1"
>  memory = 64
>  disk =
> ['file:/vserver/images/vmPROD.img,hda1,w','file:/vserver/images/vmPROD-swap.img,hda2,w']
>
>  #Network:
>  nics=1
>  dhcp="off"
>  ip="192.168.1.80"
>  netmask="255.255.255.0"
>  gateway="192.168.1.1"
>  hostname="jidoorPROD"
>  vif=[ 'bridge=xen-br1' ]
>
>  extra="3"
>  -----------------
>
>  On the VM my ifconfig for eth0 looks correct:
>  -----------------
>  eth0      Link encap:Ethernet HWaddr AA:00:00:65:9A:F0
>            inet addr:192.168.1.80  Bcase:192.168.1.255  Mask:255.255.255.0
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:31 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:110 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>            RX bytes:2136 (2.0 KiB)  TX bytes:9396 (9.1KiB)
>  -----------------
>
>  "brctl show" on the DOM0 HOST shows the xen-br1 bridge connected to eth1
> like it should be:
>  -----------------
>  xen-br1       8000.0012175a875c    no       eth1
>  -----------------
>
>  I'm able to get outside name resolution from the DOM0 Host, and my routing
> table looks like this:
>
>  >From "netstat -r"
>  -----------------
>  192.168.1.0    *                255.255.255.0     U      0 0          0
> xen-br1
>  default        192.168.1.1      0.0.0.0           UG     0 0          0
> xen-br1
>  -----------------
>
>  I created the bridge using
>  -----------------
>  /etc/xen/scripts network start antispoof=no bridge=xen-br1 netdev=eth1
>  -----------------
>
>  I'm running Debian Sarge for both the DOM0 and DOMU's, and as I said, it
> works off of xen-br0 on the other network.
>
>  If you can think of any other information relevant to this, let me know and
> I'll be happy to send it on. Any help is greatly appreciated, I've been
> working on this for several days now and can't for the life of me figure
> this out.
>
>  -Kris Hollingsworth
> _______________________________________________
> 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
<Prev in Thread] Current Thread [Next in Thread>