On 4/30/05, andrew mathes <amathes@xxxxxxxxxxxx> wrote:
> i added a new script to auto:
OK, you are way ahead of me.
I use separate conf files in /etc/xen/auto as those a re different machine.
I think I am failing to comprehend the script / conf relation in this
directory.
What I am looking to achieve is the to bring the bridges up on xend
start and have them available for whichever domain requires them.
>
> import os
>
> os.system('./etc/xen/scripts/network start bridge=xen-br1 netdev=eth3')
>
> os.system('xm create -f /etc/xen/xm.conf vmid=1')
> os.system('xm create -f /etc/xen/xm.conf vmid=2')
> os.system('xm create -f /etc/xen/xm.conf vmid=3')
> os.system('xm create -f /etc/xen/xm.conf vmid=4')
>
> my vif in the xm.conf file is:
>
> vif = [ 'mac=aa:00:00:1a:%d:11, bridge=xen-br0' % (vmid),
> 'mac=aa:00:00:1a:%d:12, bridge=xen-br1' % (vmid)]
>
> (i've tried them as two seperate lines as well ... ie. vif=[ and vif=[)
>
> are you up and going now?
>
> On Fri, 29 Apr 2005, Gil Freund wrote:
>
> > On 4/29/05, andrew mathes <amathes@xxxxxxxxxxxx> wrote:
> >> ok, things seem to be ok on my side now, i just put the manual start in my
> >> auto/ script directory, and seems to start the bridge correctly. However,
> >> the secondary vif for every VM seems to be tied to the first bridge, no
> >> matter how i bring it up (manually:./vif-bridge up domain=VM1 vif=vif1.1
> >> bridge=xen-br1 mac=AA:00:00:00:00:12)
> >
> > Questions:
> > 1. Did you modify the distribution scripts or add a new one?
> > 2. How did you configure the NIC's in the DomU config file?
> >
> >>
> >> the hwAddr of the resulting vif is ALWAYS the same as the first bridge
> >> (xen-br0) and i can't seem to get it to tie to the second bridge ...
> >> making networking fairly useless on that second nic
> >>
> >> thanks for any help-
> >>
> >> On Thu, 28 Apr 2005, Gil Freund wrote:
> >>
> >>> On 4/28/05, andrew mathes <amathes@xxxxxxxxxxxx> wrote:
> >>>> wow, i was just going to post about this, i can't find it either ...
> >>>>
> >>>> i think it's in xend-config.sxp: under
> >>>> (network-script network bridge=xen-br0 netdev=eth0)
> >>>> (network-script network bridge=xen-br1 netdev=eth3)
> >>>>
> >>>> but this isn't actually setting up two bridges for me ...
> >>>
> >>> Nor here. I can set up other bridges manual (see below)
> >>>
> >>>>
> >>>> and i think you don't need to declare specific MAC's, as long as the
> >>>> bridge/vif is set up correctly. ( I am specifying MAC's for DHCP
> >>>> reservation)
> >>>>
> >>>> any help for the both of us? maybe we'll figure it out together
> >>>
> >>> OK, I will start with manual settings:
> >>>
> >>> circus:/etc/xen/scripts# ./network start bridge=xen-br1 netdev=eth1
> >>> antispoof=yes
> >>> network start bridge=xen-br1 netdev=eth1 antispoof=yes
> >>> iptables: No chain/target/match by that name
> >>>
> >>> in the domU I can see two NIC, but DHCP does not work. DomU domains
> >>> with static IPs work.
> >>>
> >>> Now I have a bridge (xen-br1) using the mac address of eth1, however,
> >>> when I do
> >>> ./network stop bridge=xen-br1 netdev=eth1 antispoof=yes
> >>> xen-br1 us still up. Is this normal?
> >>>
> >>>
> >>>> andrew
> >>>>
> >>>> On Thu, 28 Apr 2005, Gil Freund wrote:
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> Apologies: I recall this being asked (and answered) before, but I
> >>>>> cannot find the thread.
> >>>>>
> >>>>> I have two NICs. I would like to setup three bridges:
> >>>>>
> >>>>> xen-br0 - eth0
> >>>>> xen-br1 - eth1
> >>>>> xen-br2 - virtual only for domU interconnect
> >>>>>
> >>>>> Where would be a suitable location to implement this so the startup
> >>>>> scripts pick this configuration?
> >>>>>
> >>>>> Furthermore, do MAC addresses need to be explicitly declared in the
> >>>>> domU configuration files? The example files state that random MAC
> >>>>> addresses will be used, but simply stating nics=2 does not seem to
> >>>>> work.
> >>>>>
> >>>>> Thanks
> >>>>>
> >>>>>
> >>>>> Gil
> >>>>>
> >>>>> _______________________________________________
> >>>>> Xen-users mailing list
> >>>>> Xen-users@xxxxxxxxxxxxxxxxxxx
> >>>>> http://lists.xensource.com/xen-users
> >>>>>
> >>>>
> >>>
> >>> _______________________________________________
> >>> Xen-users mailing list
> >>> Xen-users@xxxxxxxxxxxxxxxxxxx
> >>> http://lists.xensource.com/xen-users
> >>>
> >>
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
> >
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home