On Tue, 2009-02-17 at 14:58 +0700, Fajar A. Nugraha wrote:
> On Tue, Feb 17, 2009 at 2:48 PM, Gary Koskenmaki <garyk@xxxxxxxxxxxxx> wrote:
> > It turns out I just needed to use "xm network-attach domain.name
> > ip=xxx.xxx.xxx.xxx bridge=bridge_name" to create the extra interface in
> > the DomU's, and then do an ifup on that interface.
> Ah, so your problem is on domU side :)
> Here's what might help :
> (1) Assign both domU's NIC from the start on domU config file, put
> static MAC on them. Something like
> vif = [
> 'mac=00:16:3E:EC:C4:6A, bridge=br1',
> 'mac=00:16:3E:EC:C4:6B, bridge=br2',
> If you rather use "xm network-attach", be sure to specifiy the "mac" option.
> >From your command above I see that you're not using a static MAC,
> which may cause a problem.
> (2) Do NOT assign IP address on domU config file (or in your case, xm
> network-attach). Simply use normal method of assigning IP address (on
> Debian it would be domU's /etc/network/interfaces). What is the
> contents of your domU's /etc/network/interfaces? What does "ifconfig
> -a" shows on your domU? What is the contents of
> /etc/udev/rules.d/70-persistent-net.rules (or similar) on domU?
Fajar, you da man. Thanks for all your help.
I had two issues that were keeping me from getting networking working
the way I wanted it to and you solved both. The vif = line hadn't
worked for me because the examples I had seen of using two interfaces
there had either used dynamic mac address creation or had typos in them
that used single quotes at only the beginning of the first interface and
the end of the second interface.
Manually assigning mac addresses and adding the two extra single quote
marks that differentiate the two interfaces solved all the xen
networking issues I have experienced. Thanks once again for all your
> Xen-users mailing list
Xen-users mailing list