RE: [Xen-devel] xen 2.0.1, 2.4.27, 2.6.9, non-bridge

["James Harper" <james.harper@xxxxxxxxxxxxxxxx>]

> Configuring a bridge is a multi-step process.  At one point during the
> process, normal communication is severed over eth0, while the bridge
> itself is
> not yet fully functional.
> At this point, the root filesystem is no longer available, and the
machine
> falls over.

I wonder if you could do this:

1. mount a tmpfs somewhere
2. copy in enough libs etc to make #4 work
3. chroot to the new tmpfs
4. set up the bridge and transfer the address across
5. leave the chroot environment

You wouldn't want anything much else to be running at this point though
so it would have to be done pretty early in the boot process.

> I'd prefer to not do it with an initrd, as that's an added step, and
extra
> complexity.

I've set up an initrd that boots dom0 over iSCSI, which suffers from the
same problem as nfs only more so as iSCSI is connection based and
downing eth0 cuts the connections. My initrd sets up the first bridge
(my setup has 3 bridges) from the outset so the network disappearing
never becomes an issue.

Under iSCSI an initrd is the only option but for nfs it would be nifty
to be able to do without.

If anyone's interested in the script to create the initrd (debian - not
sure how it would translate to another dist) I can post it here,
shouldn't be too hard to modify it to boot from nfs... in fact my home
pc's boot off nfs using almost the same setup.

James



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel