Still trying to make my VMs appear on a subnet of their very own and route traffic to/from them from the Dom0. This network-multinet script sounds ideal for what I want: http://thepenguinpriest.com/linux/scripts/network-multinet.html However, the description of building a routed network says I need to call the script and give it the "virtual ethernet device (vethX)" that lives in Dom0. Where the heck do I get one of those? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, On Fri, Feb 22, 2008 at 9:32 PM, Tom Horsley <tom.horsley@att.net> wrote:> Still trying to make my VMs appear on a subnet of their very > own and route traffic to/from them from the Dom0. > > This network-multinet script sounds ideal for what I want: > > http://thepenguinpriest.com/linux/scripts/network-multinet.html > > However, the description of building a routed network says > I need to call the script and give it the "virtual ethernet > device (vethX)" that lives in Dom0. > > Where the heck do I get one of those? >This may be as simple as using ethX depending on how the scripts rename stuff. Also remember that you should do ifconfig -a so that you actually see the vethX devices. The vethX devices should be created automatically by Xen according to the faq [1] Section 3.7. Too many vethX and vif0.X By default, 8 vethX and vif0.X are created. These interfaces are "cheap" but clutter list of interfaces. If you want to allocate only the necessary number, pass netloop.nloopbacks=NUMBER parameter to kernel command line. Best Regards, Todd [1] http://wiki.xensource.com/xenwiki/XenFaq> > > _______________________________________________ > 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
On Fri, 22 Feb 2008 21:52:17 -0500 "Todd Deshane" <deshantm@gmail.com> wrote:> Also remember that you should do ifconfig -a so that you actually see the > vethX devices.Tried that, don''t see any different output with or without -a, also explicitly tried ifconfig vethN for N in 0..9, nothing there :-);> The vethX devices should be created automatically by Xen according to the > faq [1]I learned to stop reading the FAQ years ago :-). _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sat, Feb 23, 2008 at 6:55 PM, Tom Horsley <tom.horsley@att.net> wrote:> On Fri, 22 Feb 2008 21:52:17 -0500 > "Todd Deshane" <deshantm@gmail.com> wrote: > > > Also remember that you should do ifconfig -a so that you actually see > the > > vethX devices. > > Tried that, don''t see any different output with or without -a, also > explicitly tried ifconfig vethN for N in 0..9, nothing there :-); > > > The vethX devices should be created automatically by Xen according to > the > > faq [1] > > I learned to stop reading the FAQ years ago :-). >So, remind me again what versions of Xen, kernel version, base distro if that is relevant, etc. that you have? And also what are the key points of configs that you needed to change to get where you are? And finally the end goal is: "to make my VMs appear on a subnet of their very own and route traffic to/from them from the Dom0. " can you expand on that a little? Since it could be interpreted in a couple ways. Todd> _______________________________________________ > 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
On Sat, 23 Feb 2008 19:03:50 -0500 "Todd Deshane" <deshantm@gmail.com> wrote:> On Sat, Feb 23, 2008 at 6:55 PM, Tom Horsley <tom.horsley@att.net> wrote: > > > On Fri, 22 Feb 2008 21:52:17 -0500 > > "Todd Deshane" <deshantm@gmail.com> wrote: > > > > > Also remember that you should do ifconfig -a so that you actually see > > the > > > vethX devices. > > > > Tried that, don''t see any different output with or without -a, also > > explicitly tried ifconfig vethN for N in 0..9, nothing there :-); > > > > > The vethX devices should be created automatically by Xen according to > > the > > > faq [1] > > > > I learned to stop reading the FAQ years ago :-). > > > > > So, remind me again what versions of Xen, kernel version, base distro if > that is relevant, etc. that you have? > > And also what are the key points of configs that you needed to change to get > where you are? > > And finally the end goal is: > > "to make my VMs appear on a subnet of their very > own and route traffic to/from them from the Dom0. > " > can you expand on that a little? Since it could be interpreted in a couple > ways. > > ToddI''m running debian 40r2 (etch) x86_64 with xen 3.2.1 built from the mercurial repo (downloaded sometime near the beginning of Feb). I''m using the 2.6.18.8 kernel Xen built for me, not the debian kernel. (Incidentally the xen 3.2 seems to run much better than the previous versions of xen we tried that were included in various distros like fedora and sles - the VMs are much more stable with no mysterious crashes, which is part of the reason I''m trying to do all this since xen is starting to look useful :-). Right now I''m using the default network-bridge script, but IP addrs are scarce in the subnet I''m in, so we''ve been doing this nonsense with giving some of the VMs the same IPs and hostnames and just never booting them at the same time. It was a good way to get started, but now I''d like to make things convenient for users - give all the virtual machines meaningful hostnames and unique IP addresses on a nice empty subnet just for the virtual machines (say 192.168.88.0/24). To also make things convenient for me, I''d like to run a DHCP server on the debian host machine that tells the virtual machines what IP and hostname to use when they boot. I''d like the debian host to route all the 192.168.88.0/24 traffic to the subnet and vice-versa so all the machines in the lab can get to all the virtual machines and all the virtual machines can get out to the lab. (Worst case, machines in the lab might have to run a route command to define the debian xen host as the gateway to the VM subnet, but hopefully we can convince the powers that be to tell the the primary gateway machine about it, but only if we get everything else working first). We trust everyone - not interested in any firewall or security (yet), just want the packets to flow :-). I''m sure this is all very simple to do with linux networking, and once I memorize the terabyte of man pages, jargon, and linux source code, it will be obvious just how easy it is :-). I''ve tried a couple of things I thought would work, but ping remains silent in my attempts so far. It almost seems simpler to just put the xen host itself on a physical separate subnet and continue to use network-bridge. At least the IT folks are familiar with hardware subnets :-). _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> This network-multinet script sounds ideal for what I want: > > http://thepenguinpriest.com/linux/scripts/network-multinet.html > > However, the description of building a routed network says > I need to call the script and give it the "virtual ethernet > device (vethX)" that lives in Dom0. > > Where the heck do I get one of those?Hey! Maybe I can just use "xm network-attach" with Dom0 as both the front and back end (but would infinite recursion happen trying to run this command from inside the network setup script? :-). _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sun, 24 Feb 2008 00:41:39 -0500 Tom Horsley <tom.horsley@att.net> wrote:> Hey! Maybe I can just use "xm network-attach" with Dom0 as both > the front and back end (but would infinite recursion happen > trying to run this command from inside the network setup script? :-).Hmmm... I tried it on my existing network-bridge xen just to see what would happen (figuring an extra ethernet shouldn''t hurt anything). I get new vif0.N devices showing up in brctl, but no new ethN showing up in the Dom0. There are no error or success entries of any kind referring to domain/0 in the xen-hotplug.log file I do see this in xend.log: [2008-02-24 00:53:55 4416] DEBUG (__init__:1072) XendDomainInfo.device_create: [''vif''] [2008-02-24 00:53:55 4416] DEBUG (__init__:1072) XendDomainInfo.device_create: {''mac'': ''00:16:3e:79:86:09'', ''uuid'': ''bd1f4502-7e3b-a2f3-2b2f-550ed5852f90''} [2008-02-24 00:53:55 4416] DEBUG (__init__:1072) DevController: writing {''backend-id'': ''0'', ''mac'': ''00:16:3e:79:86:09'', ''handle'': ''0'', ''state'': ''1'', ''backend'': ''/local/domain/0/backend/vif/0/0''} to /local/domain/0/device/vif/0. [2008-02-24 00:53:55 4416] DEBUG (__init__:1072) DevController: writing {''domain'': ''Domain-0'', ''handle'': ''0'', ''uuid'': ''bd1f4502-7e3b-a2f3-2b2f-550ed5852f90'', ''script'': ''/etc/xen/scripts/vif-bridge'', ''state'': ''1'', ''frontend'': ''/local/domain/0/device/vif/0'', ''mac'': ''00:16:3e:79:86:09'', ''online'': ''1'', ''frontend-id'': ''0''} to /local/domain/0/backend/vif/0/0. [2008-02-24 00:53:55 4416] DEBUG (__init__:1072) Waiting for 0. [2008-02-24 00:53:55 4416] DEBUG (__init__:1072) hotplugStatusCallback /local/domain/0/backend/vif/0/0/hotplug-status. [2008-02-24 00:53:56 4416] DEBUG (__init__:1072) hotplugStatusCallback /local/domain/0/backend/vif/0/0/hotplug-status. [2008-02-24 00:53:56 4416] DEBUG (__init__:1072) hotplugStatusCallback 1. [2008-02-24 00:56:09 4416] DEBUG (__init__:1072) XendDomainInfo.device_create: [''vif'', [''bridge'', ''eth0''], [''backend'', ''0'']] [2008-02-24 00:56:09 4416] DEBUG (__init__:1072) XendDomainInfo.device_create: {''bridge'': ''eth0'', ''mac'': ''00:16:3e:52:ef:e6'', ''uuid'': ''d6b7889c-24cb-f1f9-6786-50c6cca4b151'', ''backend'': ''0''} [2008-02-24 00:56:09 4416] DEBUG (__init__:1072) DevController: writing {''backend-id'': ''0'', ''mac'': ''00:16:3e:52:ef:e6'', ''handle'': ''1'', ''state'': ''1'', ''backend'': ''/local/domain/0/backend/vif/0/1''} to /local/domain/0/device/vif/1. [2008-02-24 00:56:09 4416] DEBUG (__init__:1072) DevController: writing {''bridge'': ''eth0'', ''domain'': ''Domain-0'', ''handle'': ''1'', ''uuid'': ''d6b7889c-24cb-f1f9-6786-50c6cca4b151'', ''script'': ''/etc/xen/scripts/vif-bridge'', ''state'': ''1'', ''frontend'': ''/local/domain/0/device/vif/1'', ''mac'': ''00:16:3e:52:ef:e6'', ''online'': ''1'', ''frontend-id'': ''0''} to /local/domain/0/backend/vif/0/1. [2008-02-24 00:56:09 4416] DEBUG (__init__:1072) Waiting for 1. [2008-02-24 00:56:09 4416] DEBUG (__init__:1072) hotplugStatusCallback /local/domain/0/backend/vif/0/1/hotplug-status. [2008-02-24 00:56:09 4416] DEBUG (__init__:1072) hotplugStatusCallback /local/domain/0/backend/vif/0/1/hotplug-status. [2008-02-24 00:56:09 4416] DEBUG (__init__:1072) hotplugStatusCallback 1. (That was from two separate tries). Does the fact that eth0 already exists screw it up? (I also have an eth1 that is a real nic). Maybe if I tried it one more time eth2 would actually show up? :-). Nah, just tried it, merely have another vif0.N, but no eth2. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users