Regarding vif names, if you have a new enough version of xen, you
can try the vifname= parameter in the vif config line to keep the names of
the vifs consistent. Then they won't be changing. It is worth noting that
this may prevent xentop from showing network traffic associated with the
DomUs (I think maybe it does in F8, but that version of xen may not be new
enough and may only support that through a patch). You can use
/etc/xen/auto for everything and name my domU files xm#name (where # causes
them to be started in the same order and name reminds you which config file
is which), but in order to keep the same domIDs, you then have to restart
the dom0 after shutting down domUs (or, in my case, configuring xendomains
to shut down domUs on shutdown) instead of being able to just restart domUs,
and I think that is what you don't want to deal with.
All of that said, though, by default, the bridge= parameter in the
vif config line determines which bridge to use, for instance, bridge=eth0
would but the vif being created on the eth0 bridge regardless of what the
vif gets named. Is there some reason you can't keep this functionality in
your bridge script?
Dustin
-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of David
Dyer-Bennet
Sent: Friday, August 22, 2008 12:13
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] More complex bridging setup
To test on one box of virtual servers an LVS-plus-real-servers
configuration I need to do something more complicated than the basic
bridging installation that I finally figured out.
Seems simple enough to mess with the network-bridge script. But I'm
seeing problems with naming conventions. The ethernet interfaces are
named according to domain ids (numbers), which depends on the order
they're created in. This will presumably be stable when I've got it all
configured and the box just loads my config when it starts; but during
development, each time I start a new domU it'll have a new number.
So, how do people deal with connecting particular virtual interfaces in
particular domUs to particular bridges in their configs in a way not
dependent on startup order? Having to reboot everything from scratch for
every step of debugging seems like a nightmare, and I'd like to hope I can
avoid it.
(New to Xen; this is my first Xen box, running with Centos 5.2, currently
two Centos 5.2 guests and a Windows Server 2000 guest. In play / test
mode so far.)
--
David Dyer-Bennet, dd-b@xxxxxxxx; http://dd-b.net/
Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/
Photos: http://dd-b.net/photography/gallery/
Dragaera: http://dragaera.info
_______________________________________________
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
|
Home