On Thu, Dec 07, 2006 at 11:46:25AM +0000, Nick Craig-Wood wrote:
> On Wed, Dec 06, 2006 at 04:39:48PM +0000, Hugo Mills wrote:
> > After I sent the last email, I realised that one aspect of my
> > system was unusual. It turns out that something -- I haven't worked
> > out what yet (probably xend) -- requires and assumes the existence of
> > eth0. I normally have my "eth0" device renamed to "wired", and my
> > "eth1" device to "wireless". If I boot the machine without using
> > nameif to change the device names, then the Xen route scripts allow a
> > domU to start, and I can then configure the networking manually.
>
> Ah... You need to name the netdev in /etc/xen/xend-config.sxp
>
> Eg
>
> (network-script 'network-route netdev=wired')
Ah, gotcha. Thanks for that. For the record, I also found that I
needed to set the same option for vif-script in the xend-config.sxp.
Now all I have to work out is why it's still trying to use vifD.X
for the relevant interface in the dom0, instead of tapY. At the
moment, I'm having to configure that bit manually. As you pointed
out[1], though, that seems to be a bug.
Hugo.
[1] http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=584
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 1C335860 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- Hey, Virtual Memory! Now I can have a *really big* ramdisk! ---
signature.asc
Description: Digital signature
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home