[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-users] Dedicate Nic's to DomU's


  • To: <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Hans Pfeil" <HPfeil@xxxxxxx>
  • Date: Mon, 09 Jun 2008 13:19:36 -0500
  • Delivery-date: Mon, 09 Jun 2008 11:20:22 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Joe, thanks so much.  I hate to be a bother.  I really appreciate your time and 
efforts.  I started @ 1 because I thought what would Dom0 use?  I thought if I 
configured 0 it would mess up the host, don't know.  We are running Xen 3.0 on 
Novell's SLES10.1  Here are the outputs:

:~ # brctl show
bridge name     bridge id               STP enabled     interfaces
:~ #

:~ # sh /etc/xen/scripts/multi-network-bridge
/etc/xen/scripts/multi-network-bridge: line 3: /etc/xen/scripts: is a directory
/etc/xen/scripts/multi-network-bridge: line 5: /network-bridge: No such file or 
directory
:~ #

-Hans


>>> "Joseph L. Casale" <JCasale@xxxxxxxxxxxxxxxxx> 6/9/2008 12:51 PM >>>
multi-network-bridge
I am not sure it matters, but your vifnuym starts @ 1?

Config looks right...

type:
#brctl show
:)

ifconfig shows an issue :)
Your missing the vifs, the renamed physical device that the bridge in question 
uses.
Whats is the output from this:

#sh /etc/xen/scripts/multi-network-bridge

Your bridges done appear to have been made! What version of xen on what distro?
jlc

________________________________________
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
[xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Hans Pfeil 
[HPfeil@xxxxxxx] 
Sent: Monday, June 09, 2008 11:42 AM
To: xen-users@xxxxxxxxxxxxxxxxxxx 
Subject: RE: [Xen-users] Dedicate Nic's to DomU's

Joe, yep I did make the file executable.  (didn't  know I had to until this 
morning.  A guy here at work showed me.  But it still didn't work)  I deduce 
that it's not working because when I open the virt manager and click "run" to 
start the virt server it automatically goes to pause.  It just sits there in 
pause mode.  When I change everything back, all is well.
Here is copy of the outputs you asked for.  Also, here are some of the other 
files that I have.  I've attached the xend-config.spx file.

# cat /etc/xen/scripts/multi-network-bridge
#!/bin/sh
dir=$(/etc/xen/scripts "$0")
"$dir/network-bridge" "$@" vifnum=1 bridge=xenbr1 netdev=eth1

Here is the config file for the virtual guest server:

ostype="oes2l"
name="XXXXXX"
memory=1024
vcpus=1
uuid="a1ee16a1-cd9b-2493-60cb-77aea298d8fa"
on_crash="destroy"
on_poweroff="destroy"
on_reboot="restart"
localtime=0
builder="linux"
bootloader="/usr/lib/xen/boot/domUloader.py"
bootargs="--entry=xvda2:/boot/vmlinuz-xenpae,/boot/initrd-xenpae"
extra="TERM=xterm "
disk=[ 'file:/var/lib/xen/images/Harrier/disk0,xvda,w', ]
vif=[ 'bridge=eth1, mac=00:16:3e:6f:e6:6a', ]
vfb=["type=vnc,vncunused=1"]


Usage: brctl [commands]
commands:
        addbr           <bridge>                add bridge
        delbr           <bridge>                delete bridge
        addif           <bridge> <device>       add interface to bridge
        delif           <bridge> <device>       delete interface from bridge
        setageing       <bridge> <time>         set ageing time
        setbridgeprio   <bridge> <prio>         set bridge priority
        setfd           <bridge> <time>         set bridge forward delay
        sethello        <bridge> <time>         set hello time
        setmaxage       <bridge> <time>         set max message age
        setpathcost     <bridge> <port> <cost>  set path cost
        setportprio     <bridge> <port> <prio>  set port priority
        show                                    show a list of bridges
        showmacs        <bridge>                show a list of mac addrs
        showstp         <bridge>                show bridge stp info
        stp             <bridge> {on|off}       turn stp on/off


 # ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0F:1F:04:0B:49
          inet addr:xxx.xxx.xxx.xx  Bcast:xxx.xxx.xxx.xx  Mask:255.255.255.0
          inet6 addr: fe80::20f:1fff:fe04:b49/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:597 errors:0 dropped:0 overruns:0 frame:0
          TX packets:214 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:54601 (53.3 Kb)  TX bytes:19415 (18.9 Kb)
          Interrupt:17

eth1      Link encap:Ethernet  HWaddr 00:0F:1F:04:0B:4A
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:18

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:465 errors:0 dropped:0 overruns:0 frame:0
          TX packets:465 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:29962 (29.2 Kb)  TX bytes:29962 (29.2 Kb)



>>> "Joseph L. Casale" <JCasale@xxxxxxxxxxxxxxxxx> 6/9/2008 10:43 AM >>>
Well, I have not actually tested a config with it not configured, so I don't 
know for certain:)
I am not a Linux Bridge Utils guru, but I rembered from a vmware server kb 
article that you
could confiugure a NIC with an IP of 0.0.0.0 to prevent traffic getting the 
host, then unless
there is some specific requirement to Bridging, as long as the guests where in 
the same subnet
they would see each other, someone feel free to CMIIW.

I also neglected to mention I thiink you need to make the new script (mine is 
multi-network-bridge)
executable, just check your existing network-bridge script. Your logs will tell 
all.

What does # brctl show output? What does #ifconfig output?

How do you deduce its not working, I presume you are trying to communicate 
between two guests
that are in this bridge?

jlc

________________________________________
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
[xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Hans Pfeil 
[HPfeil@xxxxxxx] 
Sent: Monday, June 09, 2008 8:49 AM
To: xen-users@xxxxxxxxxxxxxxxxxxx 
Subject: [Xen-users] Dedicate Nic's to DomU's

Hey Joe, thanks for all your help and effort on this.  Unfortunately I couldn't 
get it to work.  Allow me to ask a question.   Does the actual physical nic, 
I'll call eth1, need to be configured with an IP address, routing, and host 
name first?  Right now I have eth1 with nothing configured.

Thanks
-Hans



>Don't happen to have an example of all this stuff do you?  This way I could 
>just copy it over to my side.  >Thanks.
>
>-Hans

I can provide you with the files I use, but without a minimal understanding of 
it, you'll be
hard pressed to make it work for your environment anyway.

I must suggest a good book I am just wrapping it up. One of the list members, 
Todd Deshane
has co-authored *the* most excellent book on Xen, Running Xen. It not only 
details everything
you need to know to run xen, it walks you through everything step by step to do 
things correctly
and it does this most thoroughly! You will be very comfortable running xen 
after this book!

I am running 3.2.0 on this host, so the bridge names are identical to the 
original eth names.
That most certainly could be different from your version, check your docs.

You need to edit /etc/xen/xend-config.sxp
-Locate the line: (network-script network-bridge)
-Make it say something like: (network-script multi-network-bridge)
-Now create a script in /etc/xen/scripts called multi-network-bridge

# cat /etc/xen/scripts/multi-network-bridge
#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=eth0
"$dir/network-bridge" "$@" vifnum=1 netdev=eth1 bridge=eth1
.
.
.
"$dir/network-bridge" "$@" vifnum=n netdev=ethn bridge=ethn

Now you edit the config for your guests, usually located in /etc/xen but you can
the docs for your distro or follow one of many tutorials available.
-You will see, or need to add a line:
vif = [ 'bridge=eth0, mac=00:16:3E:77:A5:D6', ]
-This will create one nic in the guest, and add it to the bridge named eth0 
which
contains the original eth0 physical nic in the xen server.

Good luck,
jlc


_______________________________________________
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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.