[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [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
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |