Re: [Xen-devel] Must have been asked before, but I can't find the solution

[Kip Macy <kmacy@xxxxxxxxxxx>]

bootscript "xenargs":
 more ~mowat/xen/xenargs
BSD_KERNEL=/u/mowat/p4/tricks/freebsd/usr/src/sys/i386/compile/XENCONF/kernel
CONFIG=/u/mowat/xen/freebsd
BOOTARGS="boot_verbose=yes, boot_gdb=yes"

# Other BSD bootargs
#
# boot_single=yes
# boot_gdb_pause=yes

# curly IP addresses
# SIM_NAME=xen-vm1
# IPADDR="172.16.9.213 172.16.9.214"
# DISKS=loop5
#
# Don't need to specify number of NICS if we specify the list of MACs
# NICS=2

# mowat1/mowat2 sim IPs
SIM_NAME=mowat1
IPADDR="10.56.18.123 10.56.18.125"
MACS="aa:1:0:0:3:37 aa:1:0:0:3:38"
DISKS="loop0 loop1 loop2 loop3 loop4 loop5 loop6 loop7"

xm create -f $CONFIG -c name=$SIM_NAME ipstr="$IPADDR" macstr="$MACS"
diskstr="$DI
SKS" bsdbootargs="$BOOTARGS" kernel=$BSD_KERNEL





excerpt from /u/mowat/xen/freebsd:

i = 0
vlist = string.split(macstr,' ')
for vintf in vlist:
    if vintf == "":
        break
    if i == 0:
        vif = [ "mac="+vintf+",bridge=xen-br0" ]
    else:
        vif += [ "mac="+vintf+",bridge=xen-br0" ]
    i = i + 1

try:
    nics
except:
    if i > 1:
        nics = i




On Wed, 19 Jan 2005, B.G. Bruce wrote:

> On Wed, 2005-01-19 at 17:52, Felipe Alfaro Solana wrote:
> > On 19 Jan 2005, at 22:21, Ian Pratt wrote:
> >
> > >
> > >> I'm attempting to migrate from vmware to xen, however I need
> > >> to be able
> > >> to run more than one bridge.
> > >
> > > Should be no problem.
> > >
> > >> Now, I can modify the existing network/vif-bridge or build replacement
> > >> scripts/config files that will get this done, with the
> > >> exception of the
> > >> MAC.  If you configure (xen-2.0.3-src.tar.bz2) a domain for
> > >> more than 1
> > >> nic, the xenU domains use the same MAC for all interfaces. EX.
> > >
> > > OK, we need to add the vif number into the MAC generation hash. Anyone
> > > care to submit a patch?
> > >
> > >> How/where do I change this? (not in the config file as far as I can
> > >> tell)
> > >
> > > I believe you can set the MAC for each vif.
> >
> > Yep! By adding
> >
> > vif = [ "mac = XX:XX:XX:XX:XX:XX" ]
> >
> > to the domain configuration file.
> >
>
> Ok, yes, that works for eth0, but what about eth1,eth2,eth3,.... what
> voodoo do I use for multiple vif?
>
> B.
>
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> > Tool for open source databases. Create drag-&-drop reports. Save time
> > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> > Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxxxx
> > https://lists.sourceforge.net/lists/listinfo/xen-devel
> >
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel