![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
I'm looking for someone with some knowledge of Xen on Debian (Lenny), to help me out with some networking woes!
My original plan was to have the following configuration on my Debian Lenny machine:
...however, I couldn't seem to get this working, for various reasons (Debian wouldn't bond my NICs, kept giving me errors about "Handshake with driver failed" and other nonsense, and then when I did get that working, networking in the Xen DomUs wouldn't work with a multitude of different errors!), so I've pretty much given up on that and now* I want something like this:
Any ideas on how to set this up? I've read the XenNetworking documentation but this particular scenario isn't described, at least as far as I can tell.
* I WOULD like to get bonding working, and I'm going to try tonight to reinstall Lenny and start again from scratch, however, if that doesn't work I'm willing to go with the split NIC configuration. The reason is Dom1 is my fileserver, which will be under heavy load most of the time (mostly reading), while 0 is just folding, 2 is a light-use webserver, and 3 is my download/BitTorrent server, all of which are light-duty tasks. I'd like to have the one NIC take care of just the fileserver, and then a second NIC for the other tasks.
More info: The NICs are Intel 10/100/1000 82573V & 82573L controllers on a Supermicro X7DCL-i, and I'm running Debian Lenny (5.0), though as I said I'm probably going to upgrade to 5.0.1 tonight. I was using the latest e1000e driver from Sourceforge (1.0.3.5).
My original plan was to have the following configuration on my Debian Lenny machine:
Code:
eth0 ------|
|------ bond0 (in Dom0, mode 5) ------ [Xen Networking] ------ DomUs
eth1 ------|...however, I couldn't seem to get this working, for various reasons (Debian wouldn't bond my NICs, kept giving me errors about "Handshake with driver failed" and other nonsense, and then when I did get that working, networking in the Xen DomUs wouldn't work with a multitude of different errors!), so I've pretty much given up on that and now* I want something like this:
Code:
eth0 ------ [Xen Networking] ------ Dom0/2/3
eth1 ------ [Xen Networking] ------ Dom1Any ideas on how to set this up? I've read the XenNetworking documentation but this particular scenario isn't described, at least as far as I can tell.
* I WOULD like to get bonding working, and I'm going to try tonight to reinstall Lenny and start again from scratch, however, if that doesn't work I'm willing to go with the split NIC configuration. The reason is Dom1 is my fileserver, which will be under heavy load most of the time (mostly reading), while 0 is just folding, 2 is a light-use webserver, and 3 is my download/BitTorrent server, all of which are light-duty tasks. I'd like to have the one NIC take care of just the fileserver, and then a second NIC for the other tasks.
More info: The NICs are Intel 10/100/1000 82573V & 82573L controllers on a Supermicro X7DCL-i, and I'm running Debian Lenny (5.0), though as I said I'm probably going to upgrade to 5.0.1 tonight. I was using the latest e1000e driver from Sourceforge (1.0.3.5).