Hi,
On 8/14/06, Chris Bradford <chrisbradford@xxxxxxxxxxxxxxxxxxxx> wrote:
[...]
I had to use eth0 as the network interface on the xen0 machine,
otherwise the xenU
machine would not find the ftp server to install from.
What do you mean by "I had to use eth0 as the network interface on the
xen0 machine"?
I don't understand your network setup - can you describe it a bit better?
The only thing I understood from your description is that you where
using bridged networking, and you configured the network-script to
connect eth1 on the dom0 to the bridge, instead of connecting eth0 to
this bridge.
[...]
Is there a simple way to get the xenU install process to use eth1?
xen as it is provided by xensource doesn't come with any install
process for domU's, and so you can't make this process to "use" eth1.
So what install process are you using? The Fedora-specific domU
install script? (something *.py)
If so, you might ask on the fedora-xen mailing list, they might know
much better how this works and how to fix errors with it.
Or to get xen to use eth1 for all xenU clients?
A xenU instance never "uses" the eth1 from you dom0, at best you would
make the xenU use one interface from your real hardwrae directly with
pci-passthrough, but it doesn't seem like this is what you are about
to do here. Apart from that, domU instances only get virtual network
interfaces.
Please read the xen wiki page "XenNetworking" to learn about how xen
networking works, I think this will help you better understand the
whole context in the first place.
I am not sure how these fedora install scripts work, but normally, if
you configured xend to use eth1 for the bridge, all domU's get
connected to the same bridge, and should have the same problems as
well as success for outside network connections.
Henning
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users