I want to change my xen server to run all the virtual machines in their own subnet and act as a router to get traffic from the VMs to the rest of the lab. This way I can have near infinite numbers of IPs for lots of virtual machines instead of sharing the somewhat limited pool available in the rest of the lab. Is this what the network-route script does versus the default network-bridge script? Is there a dummies guide anywhere explaining all this in terms someone who has looked at the network-* scripts and seen only characters fired from a shotgun could understand? :-). I''m guessing I''d also need to change the main lab router to know how to get to the xen subnet someway? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 2/18/08, Tom Horsley <tom.horsley@att.net> wrote:> This way I can have near infinite numbers of IPs for > lots of virtual machines instead of sharing the somewhat > limited pool available in the rest of the lab.you might get that, or you might find yourself that only Dom0 can connect, or maybe you suddenly need another NAT layer... it''s not a Xen issue, it''s a routing and network design issue. you have to think it in terms of network equipement: you''re given a ethernet port and many machines. how do you connect? a switch? a router? use NAT, firewalls, tunnels? (almost) any answer you would get for physical machines, you can replicate in Xen. -- Javier _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, 18 Feb 2008 18:01:30 -0500 "Javier Guerra" <javier@guerrag.com> wrote:> answer you would get > for physical machines, you can replicate in XenThe problem is the difference between "can replicate" and "knows how to replicate": That''s why I''m looking for a dummies guide :-). On the other hand, I suppose a physical solution would work as well - I could let the xen host continue to do the default bridge stuff, and plug it into a separate router, really putting it in a separate physical subnet, but that seems to defeat the purpose of virtualization :-). _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Feb 18, 2008 5:11 PM, Tom Horsley <tom.horsley@att.net> wrote:> I want to change my xen server to run all the virtual > machines in their own subnet and act as a router > to get traffic from the VMs to the rest of the lab. > > This way I can have near infinite numbers of IPs for > lots of virtual machines instead of sharing the somewhat > limited pool available in the rest of the lab. > > Is this what the network-route script does versus the > default network-bridge script? > > Is there a dummies guide anywhere explaining all this > in terms someone who has looked at the network-* scripts > and seen only characters fired from a shotgun could > understand? :-). >I would recommend taking a look at: http://runningxen.com/chapters/chapter10/ Our book is currently on Safari Rough Cuts and should released in a couple months. Todd> > I''m guessing I''d also need to change the main lab router > to know how to get to the xen subnet someway? > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users