All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
To: Wm <bill@boughton.org.uk>
Cc: xen-devel@lists.sourceforge.net, Ian.Pratt@cl.cam.ac.uk
Subject: Re: xen 2.0, networking, bridging, and nfsroot
Date: Thu, 12 Aug 2004 06:59:53 +0100	[thread overview]
Message-ID: <E1Bv8d1-0002Ab-00@mta1.cl.cam.ac.uk> (raw)
In-Reply-To: Your message of "Wed, 11 Aug 2004 11:28:59 BST." <20040811102858.GA29026@yuri.org.uk>

> On Tue, Aug 10, 2004 at 05:29:30PM -0500, Adam Heath wrote:
> > Our current setup(based on 1.0 and 1.2) uses completely diskless machines.
> > They pxeboot, which then runs grub, which then loads xen.  dom0 and domN all
> > do nfsroot, and everything is happy.
> > 
> > So, along comes 2.0.  It now uses a normal bridge to connect dom0 and domN.
> > However, the bridge has a hole, where the network does not exist, while it
> > copies the addresses from eth0 to br0, and changes all the routes.
> 
> Can you use initramfs to configure the bridge/networking and mount the rootfs?

This should work fine.  I believe using an initramfs is now the
preferred way to setup things like NFS root these days, though
using the in-kernel functions is certainly more convenient.
 
> My work arround was to add and configure the bridged interface at boot
> time, also i found the script for copying over the IP addresses
> was never reliable especailly when multiple addresses had been added
> to the old interface, and it made no attempt to deal with v6 addresses
> and routing completely breaks.

The script manages to copy multiple IPv4 addresses for me -- I'd
be grateful for a an example of it failing.

Fixing it for IPv6 shouldn't be hard, particularly if you could
post the output of 'ip addr show ethX' and 'ip route list'. 

Ian


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285

  reply	other threads:[~2004-08-12  5:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-10 22:29 xen 2.0, networking, bridging, and nfsroot Adam Heath
2004-08-10 23:59 ` Brian Wolfe
2004-08-11  0:13   ` Adam Heath
2004-08-11  0:43   ` Ian Pratt
2004-08-11 12:02     ` James Harper
2004-08-11 12:57       ` Ian Pratt
2004-08-11  3:05 ` Sachin Goyal
2004-08-11  5:52   ` Brian Wolfe
2004-08-11 10:28 ` Wm
2004-08-12  5:59   ` Ian Pratt [this message]
2004-08-11 16:56 ` Derek Glidden

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1Bv8d1-0002Ab-00@mta1.cl.cam.ac.uk \
    --to=ian.pratt@cl.cam.ac.uk \
    --cc=bill@boughton.org.uk \
    --cc=xen-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.