Hey all I''m new to Linux and Virtualizing. I''m trying to dedicate my nic''s to each virtual server. For instance, virt server A would use nic1 and virt server B would use nic2 and so on. I''ve been reading some stuff for this list and to tell you the truth I''m a bit overwhelmed. We are going to run SLES10.1 and Xen. I would appreciate any assistance. :) Thanks all, -Hans _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>Hey all I''m new to Linux and Virtualizing. I''m trying to dedicate my nic''s to each virtual server. For instance, >virt server A would use nic1 and virt server B would use nic2 and so on. I''ve been reading some stuff for this >list and to tell you the truth I''m a bit overwhelmed. We are going to run SLES10.1 and Xen. I would >appreciate any assistance. :)You could pass the NIC through into each pv guest, or create a bridge for each NIC using a custom wrapper and then use a vif statement to add a NIC in each guets to each bridge you want. The later is the least complex. jlc _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>>> "Joseph L. Casale" <JCasale@activenetwerx.com> 6/6/2008 10:09 AM >>> >Hey all I''m new to Linux and Virtualizing. I''m trying to dedicate my nic''s to each virtual server. For instance, >virt server A would use nic1 and virt server B would use nic2 and so on. I''ve been reading some stuff for this >list and to tell you the truth I''m a bit overwhelmed. We are going to run SLES10.1 and Xen. I would >appreciate any assistance. :)You could pass the NIC through into each pv guest, or create a bridge for each NIC using a custom wrapper and then use a vif statement to add a NIC in each guets to each bridge you want. The later is the least complex. jlc Joe, thanks for your valuable info. Unfortunately, I''m kinda dumb at this. Don''t know where or how to create vif statements, bridges, wrappers or the like. 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 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>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. > >-HansI 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@lists.xensource.com http://lists.xensource.com/xen-users
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. > >-HansI 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@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Jun 09, 2008 at 09:49:51AM -0500, Hans Pfeil wrote:> Hey Joe,Now, how can I get rid off Jimi Hendrix in my mind? ;-)> Does the actual physical nic, I''ll call eth1, need to be configured > with an IP address, routing, and host name first?In dom0? No. You only have to make sure that both dom0''s eth and domU''s vif share the same bridge. Rainer _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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@lists.xensource.com [xen-users-bounces@lists.xensource.com] On Behalf Of Hans Pfeil [HPfeil@uca.edu] Sent: Monday, June 09, 2008 8:49 AM To: xen-users@lists.xensource.com 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. > >-HansI 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@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>Now, how can I get rid off Jimi Hendrix in my mind? ;-)Hilarious...>In dom0? No. You only have to make sure that both dom0''s eth and domU''s >vif share the same bridge. > >RainerBoth Dom0''s? I am a bit confused. Did you mean both eth config scripts inside each DomU and their respective vif statements inside the config files? jlc _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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@activenetwerx.com>
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@lists.xensource.com
[xen-users-bounces@lists.xensource.com] On Behalf Of Hans Pfeil [HPfeil@uca.edu]
Sent: Monday, June 09, 2008 8:49 AM
To: xen-users@lists.xensource.com
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@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
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@lists.xensource.com
[xen-users-bounces@lists.xensource.com] On Behalf Of Hans Pfeil [HPfeil@uca.edu]
Sent: Monday, June 09, 2008 11:42 AM
To: xen-users@lists.xensource.com
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@activenetwerx.com>
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@lists.xensource.com
[xen-users-bounces@lists.xensource.com] On Behalf Of Hans Pfeil [HPfeil@uca.edu]
Sent: Monday, June 09, 2008 8:49 AM
To: xen-users@lists.xensource.com
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@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
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@activenetwerx.com> 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@lists.xensource.com [xen-users-bounces@lists.xensource.com] On Behalf Of Hans Pfeil [HPfeil@uca.edu] Sent: Monday, June 09, 2008 11:42 AM To: xen-users@lists.xensource.com 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@activenetwerx.com> 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@lists.xensource.com [xen-users-bounces@lists.xensource.com] On Behalf Of Hans Pfeil [HPfeil@uca.edu] Sent: Monday, June 09, 2008 8:49 AM To: xen-users@lists.xensource.com 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. > >-HansI 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@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Heh, you have no bridges, and I suspect it is becuase of that. Use my script _as is_ and reboot. See what happens :) jlc ________________________________________ From: xen-users-bounces@lists.xensource.com [xen-users-bounces@lists.xensource.com] On Behalf Of Hans Pfeil [HPfeil@uca.edu] Sent: Monday, June 09, 2008 12:19 PM To: xen-users@lists.xensource.com Subject: RE: [Xen-users] Dedicate Nic''s to DomU''s 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@activenetwerx.com> 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@lists.xensource.com [xen-users-bounces@lists.xensource.com] On Behalf Of Hans Pfeil [HPfeil@uca.edu] Sent: Monday, June 09, 2008 11:42 AM To: xen-users@lists.xensource.com 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@activenetwerx.com> 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@lists.xensource.com [xen-users-bounces@lists.xensource.com] On Behalf Of Hans Pfeil [HPfeil@uca.edu] Sent: Monday, June 09, 2008 8:49 AM To: xen-users@lists.xensource.com 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. > >-HansI 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@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Joe, no bridges. Here is a new set of info.
:~ # ifconfig
eth0 Link encap:Ethernet HWaddr 00:0F:1F:04:0B:49
inet addr:xxx.xxx.xxx.xx Bcast:xxx.xxx.xxx.xxx 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:139 errors:0 dropped:0 overruns:0 frame:0
TX packets:137 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:21227 (20.7 Kb) TX bytes:12940 (12.6 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:111 errors:0 dropped:0 overruns:0 frame:0
TX packets:111 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7079 (6.9 Kb) TX bytes:7079 (6.9 Kb)
:~ # sh /etc/xen/scripts/multi-network-bridge
Unknown command:
Valid commands are: start, stop, status
Unknown command:
Valid commands are: start, stop, status
:~ #
# 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
-Hans
Heh, you have no bridges, and I suspect it is becuase of that.
Use my script _as is_ and reboot. See what happens :)
jlc
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
You need to actually start the bridge, or at least query it for status but its
obviously not running.
Look at thge output from it as you ran it.
sh /etc/xen/scripts/multi-network-bridge start
jlc
________________________________________
From: xen-users-bounces@lists.xensource.com
[xen-users-bounces@lists.xensource.com] On Behalf Of Hans Pfeil [HPfeil@uca.edu]
Sent: Monday, June 09, 2008 1:12 PM
To: xen-users@lists.xensource.com
Subject: [Xen-users] Dedicate NIC''s to DomU''s
Joe, no bridges. Here is a new set of info.
:~ # ifconfig
eth0 Link encap:Ethernet HWaddr 00:0F:1F:04:0B:49
inet addr:xxx.xxx.xxx.xx Bcast:xxx.xxx.xxx.xxx 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:139 errors:0 dropped:0 overruns:0 frame:0
TX packets:137 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:21227 (20.7 Kb) TX bytes:12940 (12.6 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:111 errors:0 dropped:0 overruns:0 frame:0
TX packets:111 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7079 (6.9 Kb) TX bytes:7079 (6.9 Kb)
:~ # sh /etc/xen/scripts/multi-network-bridge
Unknown command:
Valid commands are: start, stop, status
Unknown command:
Valid commands are: start, stop, status
:~ #
# 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
-Hans
Heh, you have no bridges, and I suspect it is becuase of that.
Use my script _as is_ and reboot. See what happens :)
jlc
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Joe, received some JOY. Here is a copy of the latest:
:~ # rcxend stop
Stopping xend (pid 6278 6286 6303) done
:~ # sh /etc/xen/scripts/multi-network-bridge start
device eth0 already exists; can''t create bridge with the same name
device eth1 already exists; can''t create bridge with the same name
1) Got the above notice so, I made the following change (below). I changed
bridge=eth0 to bridge=xenbr0 and so. Was this correct???
# cat /etc/xen/scripts/multi-network-bridge
#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" "$@" vifnum=0 netdev=eth0
bridge=xenbr0
"$dir/network-bridge" "$@" vifnum=1 netdev=eth1
bridge=xenbr1
2) Below I ran it again.
:~ # sh /etc/xen/scripts/multi-network-bridge start
eth0 device: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
(rev 02)
eth0 configuration: eth-id-00:0f:1f:04:0b:49
eth0 IP address: xxx.xxx.xxx.xxx/24
eth0 device: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
(rev 02)
eth0 configuration: eth-id-00:0f:1f:04:0b:49
Nothing to flush.
Nothing to flush.
Waiting for peth0 to negotiate link..... eth0
eth0 configuration: eth-id-00:0f:1f:04:0b:49
eth0 IP address: xxx.xxx.xxx.xx/24
eth1 device: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
(rev 02)
eth1 configuration: eth-id-00:0f:1f:04:0b:4a
eth1 device: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
(rev 02)
eth1 configuration: eth-id-00:0f:1f:04:0b:4a
Nothing to flush.
Nothing to flush.
Waiting for peth1 to negotiate link...........(link isnt in running state)
eth1
eth1 configuration: eth-id-00:0f:1f:04:0b:4a
:~ # ifconfig
eth0 Link encap:Ethernet HWaddr 00:0F:1F:04:0B:49
inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.xxx.255 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:61 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4530 (4.4 Kb) TX bytes:468 (468.0 b)
eth1 Link encap:Ethernet HWaddr 00:0F:1F:04:0B:4A
inet6 addr: fe80::20f:1fff:fe04:b4a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:398 (398.0 b)
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:493 errors:0 dropped:0 overruns:0 frame:0
TX packets:493 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:32626 (31.8 Kb) TX bytes:32626 (31.8 Kb)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:60 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4902 (4.7 Kb) TX bytes:398 (398.0 b)
Interrupt:17
peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST NOARP 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
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:61 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:468 (468.0 b) TX bytes:4530 (4.4 Kb)
vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:5 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:398 (398.0 b) TX bytes:0 (0.0 b)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:67 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4060 (3.9 Kb) TX bytes:0 (0.0 b)
xenbr1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:5 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:328 (328.0 b) TX bytes:0 (0.0 b)
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Yea,
It looks like your using a slightly older Xen than me. Thats correct...
So, start a guest or two :) What happens?
jlc
________________________________________
From: xen-users-bounces@lists.xensource.com
[xen-users-bounces@lists.xensource.com] On Behalf Of Hans Pfeil [HPfeil@uca.edu]
Sent: Monday, June 09, 2008 2:38 PM
To: xen-users@lists.xensource.com
Subject: [Xen-users] Dedicate NIC''s to DomU''s
Joe, received some JOY. Here is a copy of the latest:
:~ # rcxend stop
Stopping xend (pid 6278 6286 6303) done
:~ # sh /etc/xen/scripts/multi-network-bridge start
device eth0 already exists; can''t create bridge with the same name
device eth1 already exists; can''t create bridge with the same name
1) Got the above notice so, I made the following change (below). I changed
bridge=eth0 to bridge=xenbr0 and so. Was this correct???
# cat /etc/xen/scripts/multi-network-bridge
#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" "$@" vifnum=0 netdev=eth0
bridge=xenbr0
"$dir/network-bridge" "$@" vifnum=1 netdev=eth1
bridge=xenbr1
2) Below I ran it again.
:~ # sh /etc/xen/scripts/multi-network-bridge start
eth0 device: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
(rev 02)
eth0 configuration: eth-id-00:0f:1f:04:0b:49
eth0 IP address: xxx.xxx.xxx.xxx/24
eth0 device: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
(rev 02)
eth0 configuration: eth-id-00:0f:1f:04:0b:49
Nothing to flush.
Nothing to flush.
Waiting for peth0 to negotiate link..... eth0
eth0 configuration: eth-id-00:0f:1f:04:0b:49
eth0 IP address: xxx.xxx.xxx.xx/24
eth1 device: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
(rev 02)
eth1 configuration: eth-id-00:0f:1f:04:0b:4a
eth1 device: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
(rev 02)
eth1 configuration: eth-id-00:0f:1f:04:0b:4a
Nothing to flush.
Nothing to flush.
Waiting for peth1 to negotiate link...........(link isnt in running state)
eth1
eth1 configuration: eth-id-00:0f:1f:04:0b:4a
:~ # ifconfig
eth0 Link encap:Ethernet HWaddr 00:0F:1F:04:0B:49
inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.xxx.255 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:61 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4530 (4.4 Kb) TX bytes:468 (468.0 b)
eth1 Link encap:Ethernet HWaddr 00:0F:1F:04:0B:4A
inet6 addr: fe80::20f:1fff:fe04:b4a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:398 (398.0 b)
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:493 errors:0 dropped:0 overruns:0 frame:0
TX packets:493 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:32626 (31.8 Kb) TX bytes:32626 (31.8 Kb)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:60 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4902 (4.7 Kb) TX bytes:398 (398.0 b)
Interrupt:17
peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST NOARP 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
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:61 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:468 (468.0 b) TX bytes:4530 (4.4 Kb)
vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:5 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:398 (398.0 b) TX bytes:0 (0.0 b)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:67 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4060 (3.9 Kb) TX bytes:0 (0.0 b)
xenbr1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:5 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:328 (328.0 b) TX bytes:0 (0.0 b)
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Yea,
It looks like your using a slightly older Xen than me. Thats correct...
So, start a guest or two :) What happens?
jlc
Morning Joe, started up one of my guests. I don''t think it''s
working. How do you tell if it''s using a different NIC. When I go to
details of that guest server in the virt manager it shows eth0. I''m
trying to get it to use eth1. Here are some more outputs.
:~ # brctl show
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no vif0.0
peth0
vif1.0
xenbr1 8000.feffffffffff no vif0.1
peth1
:~ #
Here is the config file for that guest server, /etc/xen/vm/name of server. Is
this the right one I should be modifying?
ostype="oes2l"
name="xxxxxxx"
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/xxxxxxx/disk0,xvda,w'', ]
vif=[ ''bridge=xenbr1, mac=00:16:3e:6f:e6:6a'', ] (I put
bridge=xenbr1 here. Is this correct?)
vfb=["type=vnc,vncunused=1"]
Here is the xml file in the same path location as the file above. Do I need to
do anything here?
<domain type="xen">
<ostype>oes2l</ostype> <name>xxxxxxx</name>
<memory>1048576</memory>
<maxmemory>16777216</maxmemory>
<vcpu>1</vcpu>
<uuid>a1ee16a1-cd9b-2493-60cb-77aea298d8fa</uuid>
<on_crash>destroy</on_crash>
<on_poweroff>destroy</on_poweroff>
<on_reboot>destroy</on_reboot>
<localtime>0</localtime> <os>
<type>linux</type>
<kernel>/tmp/kernel.w0ivGt</kernel>
<initrd>/tmp/install-initrd.fNK5FG</initrd>
<cmdline>TERM=xterm install=http://xxx.xxx.xxx.xxx/sles10sp1
</cmdline>
</os>
<devices>
<disk type=''file'' device=''disk''>
<driver name=''file''/>
<source file=''/var/lib/xen/images/xxxxxx/disk0''/>
<target dev=''xvda''/>
</disk>
<interface type=''bridge''><mac
address=''00:16:3e:6f:e6:6a''/><script
path=''/etc/xen/scripts/vif-bridge''/></interface>
<graphics type=''vnc''/>
</devices>
</domain>
Thanks
-Hans
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
I have never used virtmanager :)
I suspect it''s the issue. stop the guest, then run ''xm create
{config name}'' as your vif statement in that file is right.
jlc
-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Hans Pfeil
Sent: Tuesday, June 10, 2008 8:49 AM
To: xen-users@lists.xensource.com
Subject: RE: [Xen-users] Dedicate NIC''s to DomU''s
Yea,
It looks like your using a slightly older Xen than me. Thats correct...
So, start a guest or two :) What happens?
jlc
Morning Joe, started up one of my guests. I don''t think it''s
working. How do you tell if it''s using a different NIC. When I go to
details of that guest server in the virt manager it shows eth0. I''m
trying to get it to use eth1. Here are some more outputs.
:~ # brctl show
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no vif0.0
peth0
vif1.0
xenbr1 8000.feffffffffff no vif0.1
peth1
:~ #
Here is the config file for that guest server, /etc/xen/vm/name of server. Is
this the right one I should be modifying?
ostype="oes2l"
name="xxxxxxx"
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/xxxxxxx/disk0,xvda,w'', ]
vif=[ ''bridge=xenbr1, mac=00:16:3e:6f:e6:6a'', ] (I put
bridge=xenbr1 here. Is this correct?)
vfb=["type=vnc,vncunused=1"]
Here is the xml file in the same path location as the file above. Do I need to
do anything here?
<domain type="xen">
<ostype>oes2l</ostype> <name>xxxxxxx</name>
<memory>1048576</memory>
<maxmemory>16777216</maxmemory>
<vcpu>1</vcpu>
<uuid>a1ee16a1-cd9b-2493-60cb-77aea298d8fa</uuid>
<on_crash>destroy</on_crash>
<on_poweroff>destroy</on_poweroff>
<on_reboot>destroy</on_reboot>
<localtime>0</localtime> <os>
<type>linux</type>
<kernel>/tmp/kernel.w0ivGt</kernel>
<initrd>/tmp/install-initrd.fNK5FG</initrd>
<cmdline>TERM=xterm install=http://xxx.xxx.xxx.xxx/sles10sp1
</cmdline>
</os>
<devices>
<disk type=''file'' device=''disk''>
<driver name=''file''/>
<source file=''/var/lib/xen/images/xxxxxx/disk0''/>
<target dev=''xvda''/>
</disk>
<interface type=''bridge''><mac
address=''00:16:3e:6f:e6:6a''/><script
path=''/etc/xen/scripts/vif-bridge''/></interface>
<graphics type=''vnc''/>
</devices>
</domain>
Thanks
-Hans
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hans Pfeil wrote:> #!/bin/sh > dir=$(/etc/xen/scripts "$0") > "$dir/network-bridge" "$@" vifnum=1 bridge=xenbr1 netdev=eth1 >I''m not sure what you''re trying to accomplish with that "dir=..." line but it''s not going to work. The line says "execute /etc/xen/scripts with the name that this script was invoked with as parameter". Well, /etc/xen/scripts is a directory and you can''t execute it. I suspect that you actually want dir=$(dirname "$0") and I''m guessing that there was a transcription error somewhere and you thought you had to replace "dirname" (which is a command) with the name of a directory. jch _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hey John, you are absolutely correct. I fixed it later. Thanks so much :) -Hans>>> John Haxby <john.haxby@oracle.com> 6/11/2008 5:53 AM >>>Hans Pfeil wrote:> #!/bin/sh > dir=$(/etc/xen/scripts "$0") > "$dir/network-bridge" "$@" vifnum=1 bridge=xenbr1 netdev=eth1 >I''m not sure what you''re trying to accomplish with that "dir=..." line but it''s not going to work. The line says "execute /etc/xen/scripts with the name that this script was invoked with as parameter". Well, /etc/xen/scripts is a directory and you can''t execute it. I suspect that you actually want dir=$(dirname "$0") and I''m guessing that there was a transcription error somewhere and you thought you had to replace "dirname" (which is a command) with the name of a directory. jch _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks all for all your help especially to Joe Casale. I have it working and am beginning to understand the tip of the iceberg in this regard. Joe, my boss bought the book you recommended. -Hans _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
hi there, I am not sure whether this issue is solved or not, but I kind of found some relevant information when trying something similar and facing troubles. Having read the tutorial and the blog, I came to understand alot about creating and configuring bridges on xen virtual environment. Just follow this link: http://www.debian-administration.org/articles/470 good luck Augusto Lopes Hans Pfeil <HPfeil@uca.edu> escreveu: 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" 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@lists.xensource.com [xen-users-bounces@lists.xensource.com] On Behalf Of Hans Pfeil [HPfeil@uca.edu] Sent: Monday, June 09, 2008 11:42 AM To: xen-users@lists.xensource.com 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 add bridge delbr delete bridge addif add interface to bridge delif delete interface from bridge setageing set ageing time setbridgeprio set bridge priority setfd set bridge forward delay sethello set hello time setmaxage set max message age setpathcost set path cost setportprio set port priority show show a list of bridges showmacs show a list of mac addrs showstp show bridge stp info stp {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" 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@lists.xensource.com [xen-users-bounces@lists.xensource.com] On Behalf Of Hans Pfeil [HPfeil@uca.edu] Sent: Monday, June 09, 2008 8:49 AM To: xen-users@lists.xensource.com 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. > >-HansI 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@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users --------------------------------- Abra sua conta no Yahoo! Mail, o único sem limite de espaço para armazenamento! --0-1175071386-1213298047=:74874 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit hi there, <br><br>I am not sure whether this issue is solved or not, but I kind of found some relevant information when trying something similar and facing troubles.<br>Having read the tutorial and the blog, I came to understand alot about creating and configuring bridges on xen virtual environment. Just follow this link: http://www.debian-administration.org/articles/470<br><br>good luck<br><br>Augusto Lopes<br><br><b><i>Hans Pfeil <HPfeil@uca.edu></i></b> escreveu:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> 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:<br><br>:~ # brctl show<br>bridge name bridge id STP enabled interfaces<br>:~ #<br><br>:~ # sh /etc/xen/scripts/multi-network-bridge<br>/etc/xen/scripts/multi-network-bridge: line 3: /etc/xen/scripts: is a directory<br>/etc/xen/scripts/multi-network-bridge: line 5: /network-bridge: No such file or directory<br>:~ #<br><br>-Hans<br><br><br>>>> "Joseph L. Casale" <JCasale@activenetwerx.com> 6/9/2008 12:51 PM >>><br>multi-network-bridge<br>I am not sure it matters, but your vifnuym starts @ 1?<br><br>Config looks right...<br><br>type:<br>#brctl show<br>:)<br><br>ifconfig shows an issue :)<br>Your missing the vifs, the renamed physical device that the bridge in question uses.<br>Whats is the output from this:<br><br>#sh /etc/xen/scripts/multi-network-bridge<br><br>Your bridges done appear to have been made! What version of xen on what distro?<br>jlc<br><br>________________________________________<br>From: xen-users-bounces@lists.xensource.com [xen-users-bounces@lists.xensource.com] On Behalf Of Hans Pfeil [HPfeil@uca.edu] <br>Sent: Monday, June 09, 2008 11:42 AM<br>To: xen-users@lists.xensource.com <br>Subject: RE: [Xen-users] Dedicate Nic''s to DomU''s<br><br>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.<br>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.<br><br># cat /etc/xen/scripts/multi-network-bridge<br>#!/bin/sh<br>dir=$(/etc/xen/scripts "$0")<br>"$dir/network-bridge" "$@" vifnum=1 bridge=xenbr1 netdev=eth1<br><br>Here is the config file for the virtual guest server:<br><br>ostype="oes2l"<br>name="XXXXXX"<br>memory=1024<br>vcpus=1<br>uuid="a1ee16a1-cd9b-2493-60cb-77aea298d8fa"<br>on_crash="destroy"<br>on_poweroff="destroy"<br>on_reboot="restart"<br>localtime=0<br>builder="linux"<br>bootloader="/usr/lib/xen/boot/domUloader.py"<br>bootargs="--entry=xvda2:/boot/vmlinuz-xenpae,/boot/initrd-xenpae"<br>extra="TERM=xterm "<br>disk=[ ''file:/var/lib/xen/images/Harrier/disk0,xvda,w'', ]<br>vif=[ ''bridge=eth1, mac=00:16:3e:6f:e6:6a'', ]<br>vfb=["type=vnc,vncunused=1"]<br><br><br>Usage: brctl [commands]<br>commands:<br> addbr <bridge> add bridge<br> delbr <bridge> delete bridge<br> addif <bridge> <device> add interface to bridge<br> delif <bridge> <device> delete interface from bridge<br> setageing <bridge> <time> set ageing time<br> setbridgeprio <bridge> <prio> set bridge priority<br> setfd <bridge> <time> set bridge forward delay<br> sethello <bridge> <time> set hello time<br> setmaxage <bridge> <time> set max message age<br> setpathcost <bridge> <port> <cost> set path cost<br> setportprio <bridge> <port> <prio> set port priority<br> show show a list of bridges<br> showmacs <bridge> show a list of mac addrs<br> showstp <bridge> show bridge stp info<br> stp <bridge> {on|off} turn stp on/off<br><br><br> # ifconfig<br>eth0 Link encap:Ethernet HWaddr 00:0F:1F:04:0B:49<br> inet addr:xxx.xxx.xxx.xx Bcast:xxx.xxx.xxx.xx Mask:255.255.255.0<br> inet6 addr: fe80::20f:1fff:fe04:b49/64 Scope:Link<br> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br> RX packets:597 errors:0 dropped:0 overruns:0 frame:0<br> TX packets:214 errors:0 dropped:0 overruns:0 carrier:0<br> collisions:0 txqueuelen:1000<br> RX bytes:54601 (53.3 Kb) TX bytes:19415 (18.9 Kb)<br> Interrupt:17<br><br>eth1 Link encap:Ethernet HWaddr 00:0F:1F:04:0B:4A<br> UP BROADCAST MULTICAST MTU:1500 Metric:1<br> RX packets:0 errors:0 dropped:0 overruns:0 frame:0<br> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0<br> collisions:0 txqueuelen:1000<br> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)<br> Interrupt:18<br><br>lo Link encap:Local Loopback<br> inet addr:127.0.0.1 Mask:255.0.0.0<br> inet6 addr: ::1/128 Scope:Host<br> UP LOOPBACK RUNNING MTU:16436 Metric:1<br> RX packets:465 errors:0 dropped:0 overruns:0 frame:0<br> TX packets:465 errors:0 dropped:0 overruns:0 carrier:0<br> collisions:0 txqueuelen:0<br> RX bytes:29962 (29.2 Kb) TX bytes:29962 (29.2 Kb)<br><br><br><br>>>> "Joseph L. Casale" <JCasale@activenetwerx.com> 6/9/2008 10:43 AM >>><br>Well, I have not actually tested a config with it not configured, so I don''t know for certain:)<br>I am not a Linux Bridge Utils guru, but I rembered from a vmware server kb article that you<br>could confiugure a NIC with an IP of 0.0.0.0 to prevent traffic getting the host, then unless<br>there is some specific requirement to Bridging, as long as the guests where in the same subnet<br>they would see each other, someone feel free to CMIIW.<br><br>I also neglected to mention I thiink you need to make the new script (mine is multi-network-bridge)<br>executable, just check your existing network-bridge script. Your logs will tell all.<br><br>What does # brctl show output? What does #ifconfig output?<br><br>How do you deduce its not working, I presume you are trying to communicate between two guests<br>that are in this bridge?<br><br>jlc<br><br>________________________________________<br>From: xen-users-bounces@lists.xensource.com [xen-users-bounces@lists.xensource.com] On Behalf Of Hans Pfeil [HPfeil@uca.edu] <br>Sent: Monday, June 09, 2008 8:49 AM<br>To: xen-users@lists.xensource.com <br>Subject: [Xen-users] Dedicate Nic''s to DomU''s<br><br>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.<br><br>Thanks<br>-Hans<br><br><br><br>>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.<br>><br>>-Hans<br><br>I can provide you with the files I use, but without a minimal understanding of it, you''ll be<br>hard pressed to make it work for your environment anyway.<br><br>I must suggest a good book I am just wrapping it up. One of the list members, Todd Deshane<br>has co-authored *the* most excellent book on Xen, Running Xen. It not only details everything<br>you need to know to run xen, it walks you through everything step by step to do things correctly<br>and it does this most thoroughly! You will be very comfortable running xen after this book!<br><br>I am running 3.2.0 on this host, so the bridge names are identical to the original eth names.<br>That most certainly could be different from your version, check your docs.<br><br>You need to edit /etc/xen/xend-config.sxp<br>-Locate the line: (network-script network-bridge)<br>-Make it say something like: (network-script multi-network-bridge)<br>-Now create a script in /etc/xen/scripts called multi-network-bridge<br><br># cat /etc/xen/scripts/multi-network-bridge<br>#!/bin/sh<br>dir=$(dirname "$0")<br>"$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=eth0<br>"$dir/network-bridge" "$@" vifnum=1 netdev=eth1 bridge=eth1<br>.<br>.<br>.<br>"$dir/network-bridge" "$@" vifnum=n netdev=ethn bridge=ethn<br><br>Now you edit the config for your guests, usually located in /etc/xen but you can<br>the docs for your distro or follow one of many tutorials available.<br>-You will see, or need to add a line:<br>vif = [ ''bridge=eth0, mac=00:16:3E:77:A5:D6'', ]<br>-This will create one nic in the guest, and add it to the bridge named eth0 which<br>contains the original eth0 physical nic in the xen server.<br><br>Good luck,<br>jlc<br><br><br>_______________________________________________<br>Xen-users mailing list<br>Xen-users@lists.xensource.com <br>http://lists.xensource.com/xen-users <br><br>_______________________________________________<br>Xen-users mailing list<br>Xen-users@lists.xensource.com <br>http://lists.xensource.com/xen-users<br><br>_______________________________________________<br>Xen-users mailing list<br>Xen-users@lists.xensource.com<br>http://lists.xensource.com/xen-users<br></JCasale@activenetwerx.com></bridge></bridge></bridge></prio></port></bridge></cost></port></bridge></time></bridge></time></bridge></time></bridge></prio></bridge></time></bridge></device></bridge></device></bridge></bridge></bridge></JCasale@activenetwerx.com></blockquote><br><p>  <hr size=1>Abra sua conta no <a href="http://br.rd.yahoo.com/mail/taglines/mail/*http://br.mail.yahoo.com/">Yahoo! Mail</a>, o único sem limite de espaço para armazenamento! --0-1175071386-1213298047=:74874-- --===============0457772914=Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users --===============0457772914==--
whoever might be having the same issue, CHECK OUT THE FOLLOWING TUTORIAL: http://www.debian-administration.org/articles/470 good luck Hans Pfeil <HPfeil@uca.edu> escreveu: >>> "Joseph L. Casale" 6/6/2008 10:09 AM >>>>Hey all I''m new to Linux and Virtualizing. I''m trying to dedicate my nic''s to each virtual server. For instance, >virt server A would use nic1 and virt server B would use nic2 and so on. I''ve been reading some stuff for this >list and to tell you the truth I''m a bit overwhelmed. We are going to run SLES10.1 and Xen. I would >appreciate any assistance. :)You could pass the NIC through into each pv guest, or create a bridge for each NIC using a custom wrapper and then use a vif statement to add a NIC in each guets to each bridge you want. The later is the least complex. jlc Joe, thanks for your valuable info. Unfortunately, I''m kinda dumb at this. Don''t know where or how to create vif statements, bridges, wrappers or the like. 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 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users --------------------------------- Abra sua conta no Yahoo! Mail, o único sem limite de espaço para armazenamento! --0-749614911-1213298960=:20036 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit whoever might be having the same issue, CHECK OUT THE FOLLOWING TUTORIAL: http://www.debian-administration.org/articles/470<br><br>good luck<br><br><b><i>Hans Pfeil <HPfeil@uca.edu></i></b> escreveu:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> >>> "Joseph L. Casale" <JCasale@activenetwerx.com> 6/6/2008 10:09 AM >>><br>>Hey all I''m new to Linux and Virtualizing. I''m trying to dedicate my nic''s to each virtual server. For instance, >virt server A would use nic1 and virt server B would use nic2 and so on. I''ve been reading some stuff for this >list and to tell you the truth I''m a bit overwhelmed. We are going to run SLES10.1 and Xen. I would >appreciate any assistance. :)<br><br>You could pass the NIC through into each pv guest, or create a bridge for<br>each NIC using a custom wrapper and then use a vif statement to add a NIC<br>in each guets to each bridge you want. The later is the least complex.<br><br>jlc<br><br><br><br>Joe, thanks for your valuable info. Unfortunately, I''m kinda dumb at this. Don''t know where or how to create vif statements, bridges, wrappers or the like. 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.<br><br>-Hans<br><br><br>_______________________________________________<br>Xen-users mailing list<br>Xen-users@lists.xensource.com<br>http://lists.xensource.com/xen-users<br></JCasale@activenetwerx.com></blockquote><br><p>  <hr size=1>Abra sua conta no <a href="http://br.rd.yahoo.com/mail/taglines/mail/*http://br.mail.yahoo.com/">Yahoo! Mail</a>, o único sem limite de espaço para armazenamento! --0-749614911-1213298960=:20036-- --===============0833230796=Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users --===============0833230796==--
Well all, I''m making some headway and received a little joy but still
have some issues. Here are my stats:
Xen = Xen 3.0
OS = Sles 10.1
NICs = 2, Broadcom''s embedded and 2-quad port Intel nics, total of 10
on the machine. In YAST I selected NONE for each of the Intel NIC''s.
This was so domO would not see it. Was this correct?
1) I would like to use the Intel nics for my domU''s.
2) below is a copy of my wrapper file:
# cat /etc/xen/scripts/multi-network-bridge
#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" start vifnum=0 netdev=eth0 bridge=xenbr0
"$dir/network-bridge" start vifnum=1 netdev=eth1 bridge=xenbr1
"$dir/network-bridge" start vifnum=2 netdev=eth2 bridge=xenbr2
"$dir/network-bridge" start vifnum=3 netdev=eth3 bridge=xenbr3
"$dir/network-bridge" start vifnum=4 netdev=eth4 bridge=xenbr4
"$dir/network-bridge" start vifnum=5 netdev=eth5 bridge=xenbr5
"$dir/network-bridge" start vifnum=6 netdev=eth6 bridge=xenbr6
"$dir/network-bridge" start vifnum=7 netdev=eth7 bridge=xenbr7
"$dir/network-bridge" start vifnum=8 netdev=eth8 bridge=xenbr8
3) below is what I get when I type brctl show
# brctl show
bridge name bridge id STP enabled interfaces
xenbr0 8000.000000000000 no
xenbr1 8000.feffffffffff no vif0.1
peth1
xenbr2 8000.000000000000 no
xenbr3 8000.000000000000 no
4) below is the notification I''m receiving: notice after xenbr3 the
errors regarding line 225 and the missing veth''s. Not sure where to go
from here. Is my wrapper file correct?
eth1 Link encap:Ethernet HWaddr 00:1E:C9:AD:77:08
inet addr:xxxxxxx Bcast:xxxxxxxxxx Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1063 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:124554 (121.6 Kb) TX bytes:0 (0.0 b)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:428 errors:0 dropped:0 overruns:0 frame:0
TX packets:428 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:27293 (26.6 Kb) TX bytes:27293 (26.6 Kb)
peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:1063 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:128806 (125.7 Kb) TX bytes:0 (0.0 b)
Interrupt:16 Memory:da000000-da012100
vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:1063 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:124554 (121.6 Kb)
xenbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
UP BROADCAST RUNNING NOARP 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
xenbr1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:1063 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:109672 (107.1 Kb) TX bytes:0 (0.0 b)
xenbr2 Link encap:Ethernet HWaddr 00:00:00:00:00:00
UP BROADCAST RUNNING NOARP 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
xenbr3 Link encap:Ethernet HWaddr 00:00:00:00:00:00
UP BROADCAST RUNNING NOARP 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
~ # sh /etc/xen/scripts/multi-network-bridge start
/etc/xen/scripts/network-bridge: line 226: /etc/sysconfig/network/ifcfg-: No
such file or directory
/etc/xen/scripts/network-bridge: line 226: /etc/sysconfig/network/ifcfg-: No
such file or directory
/etc/xen/scripts/network-bridge: line 226: /etc/sysconfig/network/ifcfg-: No
such file or directory
Link veth4 is missing.
This may be because you have reached the limit of the number of interfaces
that the loopback driver supports. If the loopback driver is a module, you
may raise this limit by passing it as a parameter (nloopbacks=<N>); if the
driver is compiled statically into the kernel, then you may set the parameter
using loopback.nloopbacks=<N> on the domain 0 kernel command line.
Link veth5 is missing.
This may be because you have reached the limit of the number of interfaces
that the loopback driver supports. If the loopback driver is a module, you
may raise this limit by passing it as a parameter (nloopbacks=<N>); if the
driver is compiled statically into the kernel, then you may set the parameter
using loopback.nloopbacks=<N> on the domain 0 kernel command line.
Link veth6 is missing.
This may be because you have reached the limit of the number of interfaces
that the loopback driver supports. If the loopback driver is a module, you
may raise this limit by passing it as a parameter (nloopbacks=<N>); if the
driver is compiled statically into the kernel, then you may set the parameter
using loopback.nloopbacks=<N> on the domain 0 kernel command line.
Link veth7 is missing.
This may be because you have reached the limit of the number of interfaces
that the loopback driver supports. If the loopback driver is a module, you
may raise this limit by passing it as a parameter (nloopbacks=<N>); if the
driver is compiled statically into the kernel, then you may set the parameter
using loopback.nloopbacks=<N> on the domain 0 kernel command line.
Link veth8 is missing.
This may be because you have reached the limit of the number of interfaces
that the loopback driver supports. If the loopback driver is a module, you
may raise this limit by passing it as a parameter (nloopbacks=<N>); if the
driver is compiled statically into the kernel, then you may set the parameter
using loopback.nloopbacks=<N> on the domain 0 kernel command line.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Wednesday June 18 2008 03:36:28 pm Hans Pfeil wrote:> Xen = Xen 3.0 > OS = Sles 10.1 > NICs = 2, Broadcom''s embedded and 2-quad port Intel nics, total of 10 on > the machine. In YAST I selected NONE for each of the Intel NIC''s. This > was so domO would not see it. Was this correct?No. If you were doing PCI passthrough, it would be correct. The devices should not be initialized or kernel modules loaded for passthrough. You are just doing xen bridging. All your eth{n} devices should be initialized before xend starts, so it can use them in your wrapper scripts.> # brctl show > bridge name bridge id STP enabled interfaces > xenbr0 8000.000000000000 no > xenbr1 8000.feffffffffff no vif0.1 > peth1 > xenbr2 8000.000000000000 no > xenbr3 8000.000000000000 noAs you can see, the only bridge with a physical nic on it is xenbr1 - it has peth1 - and will be the only bridge that can talk to the outside world, or wherever that card is cable to. Your wrapper script is correct for xen 3.0. The problem is device initialization before the xend service starts. Go back to YaST and set everything up. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Jim, thanks for your reply. I have found that XEN is not initializing the extra
Intel nic''s. I get "failed to initialize". When I reboot to
just SLES the nic''s are initialized. Upon rebooting back to XEN
"failed to initialize in the boot sequence. I checked the boot log in the
var/log/boot.msg file and sure enough they "failed to initialize".
Here is the ifconfig for both modes.
1) How do you initialize these nic''s under XEN mode??
2) Here is the ifconfig for SLES Mode: They all initialize
3) At the bottom of this ifconfig file for when I reboot to XEN Mode they
don''t intialize.
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:1E:C9:AD:77:0A
inet addr:xxxxxxxxxxxx Bcast:xxxxxxxxxx Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:367 errors:0 dropped:0 overruns:0 frame:0
TX packets:303 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:105287 (102.8 Kb) TX bytes:39920 (38.9 Kb)
Interrupt:169 Memory:d6000000-d6012100
eth1 Link encap:Ethernet HWaddr 00:1E:C9:AD:77:08
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:169 Memory:da000000-da012100
eth2 Link encap:Ethernet HWaddr 00:1B:21:17:EE:30
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)
eth3 Link encap:Ethernet HWaddr 00:1B:21:17:EE:31
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)
eth4 Link encap:Ethernet HWaddr 00:1B:21:17:EE:34
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)
eth5 Link encap:Ethernet HWaddr 00:1B:21:17:EE:35
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)
eth6 Link encap:Ethernet HWaddr 00:1B:21:17:F8:20
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)
eth7 Link encap:Ethernet HWaddr 00:1B:21:17:F8:21
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)
eth8 Link encap:Ethernet HWaddr 00:1B:21:17:F8:24
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)
eth9 Link encap:Ethernet HWaddr 00:1B:21:17:F8:25
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)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:126 errors:0 dropped:0 overruns:0 frame:0
TX packets:126 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7656 (7.4 Kb) TX bytes:7656 (7.4 Kb)
XEN Mode ifconfig
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:1E:C9:AD:77:0A
inet addr:xxxxxxxxxxx Bcast:xxxxxxxxxxxxx Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:430 errors:0 dropped:0 overruns:0 frame:0
TX packets:253 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:106606 (104.1 Kb) TX bytes:34605 (33.7 Kb)
eth1 Link encap:Ethernet HWaddr 00:1E:C9:AD:77:08
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:16 Memory:da000000-da012100
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:94 errors:0 dropped:0 overruns:0 frame:0
TX packets:94 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5600 (5.4 Kb) TX bytes:5600 (5.4 Kb)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:429 errors:0 dropped:0 overruns:0 frame:0
TX packets:253 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:108728 (106.1 Kb) TX bytes:35635 (34.7 Kb)
Interrupt:16 Memory:d6000000-d6012100
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:253 errors:0 dropped:0 overruns:0 frame:0
TX packets:430 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:34605 (33.7 Kb) TX bytes:106606 (104.1 Kb)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:128 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7205 (7.0 Kb) TX bytes:0 (0.0 b)
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Thursday June 19 2008 03:17:06 pm Hans Pfeil wrote:> Jim, thanks for your reply. I have found that XEN is not initializing the > extra Intel nic''s. I get "failed to initialize". When I reboot to just > SLES the nic''s are initialized. Upon rebooting back to XEN "failed to > initialize in the boot sequence. I checked the boot log in the > var/log/boot.msg file and sure enough they "failed to initialize". Here > is the ifconfig for both modes. > > 1) How do you initialize these nic''s under XEN mode??That''s puzzling. Once YaST sets up your nics, it should work in either vanilla SuSE or xen SuSE. I assume your vanilla & xen kernel versions are exactly the same, as is usual for SuSE (and I assume for SLES). Whatever kernel module you are using for the Intel nics in vanilla SLES (say e1000?), should show up when you do ''modinfo e1000'' in xen SLES. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Jim, thanks for helping me with this. Anybody and everybody please chime in.
My last posting was a bit confusing. I was trying to do it from memory and
messed it up. Here is an excerpt from my boot log file. I totally wiped the
server and started from scratch. No wrapper file, no nothing. Just a clean
install of SLES10.1 with XEN3.0. I did setup each NIC with a static IP address.
I think the problem is at boot time. For some reason when I boot to XEN, it
cannot find these extra nics. It will see the two embedded Broadcom''s
but not the 8 Intel nics. The intel nics are: Intel gigabit VT Quad Port
Server Adapters, using the Intel 82575 chipset on a Dell 1950 server. When you
boot to normal SLES it will see ALL the nics. Seems to me there is something to
setup somewhere so XEN can see these cards??
Thanks all,
-Hans
doneSetting up network interfaces:
lo
lo IP address: 127.0.0.1/8
done eth0 device: Broadcom Corporation NetXtreme II BCM5708 Gigabit
Ethernet (rev 12)
eth0 configuration: eth-id-00:1e:c9:ad:77:0a
eth0 IP address: xxx.xxx.xxx.xxx
done eth1 device: Broadcom Corporation NetXtreme II BCM5708 Gigabit
Ethernet (rev 12)
eth1 configuration: eth-id-00:1e:c9:ad:77:08
eth1 IP address: xxx.xxx.xxx.xxx
doneWaiting for mandatory devices: eth-id-00:1b:21:17:ee:30
eth-id-00:1b:21:17:ee:31 eth-id-00:1b:21:17:ee:34 eth-id-00:1b:21:17:ee:35
eth-id-00:1b:21:17:f8:20 eth-id-00:1b:21:17:f8:21 eth-id-00:1b:21:17:f8:24
eth-id-00:1b:21:17:f8:25 __NSC__
19 18 17 16 15 14 13 12 11 10 8 7 6 5 4 3 2 1 0
eth-id-00:1b:21:17:ee:30 No interface found
failed eth-id-00:1b:21:17:ee:31 No interface found
failed eth-id-00:1b:21:17:ee:34 No interface found
failed eth-id-00:1b:21:17:ee:35 No interface found
failed eth-id-00:1b:21:17:f8:20 No interface found
failed eth-id-00:1b:21:17:f8:21 No interface found
failed eth-id-00:1b:21:17:f8:24 No interface found
failed eth-id-00:1b:21:17:f8:25 No interface found
failedSetting up service network . . . . . . . . . . . . . . .
.failed
>>> jim burns <jim_burn@bellsouth.net> 6/19/2008 9:44 PM
>>>
On Thursday June 19 2008 03:17:06 pm Hans Pfeil wrote:> Jim, thanks for your reply. I have found that XEN is not initializing the
> extra Intel nic''s. I get "failed to initialize". When
I reboot to just
> SLES the nic''s are initialized. Upon rebooting back to XEN
"failed to
> initialize in the boot sequence. I checked the boot log in the
> var/log/boot.msg file and sure enough they "failed to
initialize". Here
> is the ifconfig for both modes.
>
> 1) How do you initialize these nic''s under XEN mode??
That''s puzzling. Once YaST sets up your nics, it should work in either
vanilla
SuSE or xen SuSE. I assume your vanilla & xen kernel versions are exactly
the
same, as is usual for SuSE (and I assume for SLES). Whatever kernel module
you are using for the Intel nics in vanilla SLES (say e1000?), should show up
when you do ''modinfo e1000'' in xen SLES.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hey Jim, forgot to answer your question regarding running modinfo e1000 from previous post. I ran modinfo e1000. Here is what came up: modinfo e1000 filename: /lib/modules/2.6.16.54-0.2.5-xen/kernel/drivers/net/e1000/e1000.ko version: 7.3.15-k3-NAPI license: GPL description: Intel(R) PRO/1000 Network Driver author: Intel Corporation, <linux.nics@intel.com> srcversion: 87BB4B8A5724E0032B5AC06 alias: pci:v00008086d000010C5sv*sd*bc*sc*i* alias: pci:v00008086d000010C4sv*sd*bc*sc*i* alias: pci:v00008086d000010BCsv*sd*bc*sc*i* alias: pci:v00008086d000010BBsv*sd*bc*sc*i* alias: pci:v00008086d000010BAsv*sd*bc*sc*i* alias: pci:v00008086d000010B9sv*sd*bc*sc*i* alias: pci:v00008086d000010B5sv*sd*bc*sc*i* alias: pci:v00008086d000010A4sv*sd*bc*sc*i* alias: pci:v00008086d0000109Asv*sd*bc*sc*i* alias: pci:v00008086d00001099sv*sd*bc*sc*i* alias: pci:v00008086d00001098sv*sd*bc*sc*i* alias: pci:v00008086d00001096sv*sd*bc*sc*i* alias: pci:v00008086d0000108Csv*sd*bc*sc*i* alias: pci:v00008086d0000108Bsv*sd*bc*sc*i* alias: pci:v00008086d0000108Asv*sd*bc*sc*i* alias: pci:v00008086d0000107Fsv*sd*bc*sc*i* alias: pci:v00008086d0000107Esv*sd*bc*sc*i* alias: pci:v00008086d0000107Dsv*sd*bc*sc*i* alias: pci:v00008086d0000107Csv*sd*bc*sc*i* alias: pci:v00008086d0000107Bsv*sd*bc*sc*i* alias: pci:v00008086d0000107Asv*sd*bc*sc*i* alias: pci:v00008086d00001079sv*sd*bc*sc*i* alias: pci:v00008086d00001078sv*sd*bc*sc*i* alias: pci:v00008086d00001077sv*sd*bc*sc*i* alias: pci:v00008086d00001076sv*sd*bc*sc*i* alias: pci:v00008086d00001075sv*sd*bc*sc*i* alias: pci:v00008086d00001060sv*sd*bc*sc*i* alias: pci:v00008086d0000105Fsv*sd*bc*sc*i* alias: pci:v00008086d0000105Esv*sd*bc*sc*i* alias: pci:v00008086d0000104Dsv*sd*bc*sc*i* alias: pci:v00008086d0000104Csv*sd*bc*sc*i* alias: pci:v00008086d0000104Bsv*sd*bc*sc*i* alias: pci:v00008086d0000104Asv*sd*bc*sc*i* alias: pci:v00008086d00001049sv*sd*bc*sc*i* alias: pci:v00008086d00001028sv*sd*bc*sc*i* alias: pci:v00008086d00001027sv*sd*bc*sc*i* alias: pci:v00008086d00001026sv*sd*bc*sc*i* alias: pci:v00008086d0000101Esv*sd*bc*sc*i* alias: pci:v00008086d0000101Dsv*sd*bc*sc*i* alias: pci:v00008086d0000101Asv*sd*bc*sc*i* alias: pci:v00008086d00001019sv*sd*bc*sc*i* alias: pci:v00008086d00001018sv*sd*bc*sc*i* alias: pci:v00008086d00001017sv*sd*bc*sc*i* alias: pci:v00008086d00001016sv*sd*bc*sc*i* alias: pci:v00008086d00001015sv*sd*bc*sc*i* alias: pci:v00008086d00001014sv*sd*bc*sc*i* alias: pci:v00008086d00001013sv*sd*bc*sc*i* alias: pci:v00008086d00001012sv*sd*bc*sc*i* alias: pci:v00008086d00001011sv*sd*bc*sc*i* alias: pci:v00008086d00001010sv*sd*bc*sc*i* alias: pci:v00008086d0000100Fsv*sd*bc*sc*i* alias: pci:v00008086d0000100Esv*sd*bc*sc*i* alias: pci:v00008086d0000100Dsv*sd*bc*sc*i* alias: pci:v00008086d0000100Csv*sd*bc*sc*i* alias: pci:v00008086d00001009sv*sd*bc*sc*i* alias: pci:v00008086d00001008sv*sd*bc*sc*i* alias: pci:v00008086d00001004sv*sd*bc*sc*i* alias: pci:v00008086d00001001sv*sd*bc*sc*i* alias: pci:v00008086d00001000sv*sd*bc*sc*i* depends: supported: yes vermagic: 2.6.16.54-0.2.5-xen SMP gcc-4.1 parm: TxDescriptors:Number of transmit descriptors (array of int) parm: RxDescriptors:Number of receive descriptors (array of int) parm: Speed:Speed setting (array of int) parm: Duplex:Duplex setting (array of int) parm: AutoNeg:Advertised auto-negotiation setting (array of int) parm: FlowControl:Flow Control setting (array of int) parm: XsumRX:Disable or enable Receive Checksum offload (array of int)parm: TxIntDelay:Transmit Interrupt Delay (array of int) parm: TxAbsIntDelay:Transmit Absolute Interrupt Delay (array of int) parm: RxIntDelay:Receive Interrupt Delay (array of int) parm: RxAbsIntDelay:Receive Absolute Interrupt Delay (array of int) parm: InterruptThrottleRate:Interrupt Throttling Rate (array of int) parm: SmartPowerDownEnable:Enable PHY smart power down (array of int) parm: KumeranLockLoss:Enable Kumeran lock loss workaround (array of int) parm: debug:Debug level (0=none,...,16=all) (int) owl:~ # http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Friday June 20 2008 09:33:31 am Hans Pfeil wrote:> doneSetting up network interfaces: > lo > lo IP address: 127.0.0.1/8 > done eth0 device: Broadcom Corporation NetXtreme II BCM5708 Gigabit > Ethernet (rev 12) eth0 configuration: eth-id-00:1e:c9:ad:77:0a > eth0 IP address: xxx.xxx.xxx.xxx > done eth1 device: Broadcom Corporation NetXtreme II BCM5708 Gigabit > Ethernet (rev 12) eth1 configuration: eth-id-00:1e:c9:ad:77:08 > eth1 IP address: xxx.xxx.xxx.xxx > > doneWaiting for mandatory devices: eth-id-00:1b:21:17:ee:30 > eth-id-00:1b:21:17:ee:31 eth-id-00:1b:21:17:ee:34 eth-id-00:1b:21:17:ee:35 > eth-id-00:1b:21:17:f8:20 eth-id-00:1b:21:17:f8:21 eth-id-00:1b:21:17:f8:24 > eth-id-00:1b:21:17:f8:25 __NSC__ 19 18 17 16 15 14 13 12 11 10 8 7 6 5 4 3 > 2 1 0 > eth-id-00:1b:21:17:ee:30 No interface foundHmm - post the following outputs: 1) cat /etc/sysconfig/network/ifcfg-eth-id-00:1e:c9:ad:77:0a (that is eth0) 2) cat /etc/sysconfig/network/ifcfg-eth-id-00:1b:21:17:ee:30 (that is eth2) 3) grep eth /etc/modprobe.conf* /etc/modprobe.d/* 4) ls -alF /lib/modules 5) uname -a (when booted into kernel-default and kernel-xen/xenpae) 6) hwinfo --netcard (in both kernel-default and kernel-xen/xenpae) 7) #6 will tell you the kernel module name under ''Driver:'', in kernel-xen/xenpae, give me the output of ''modinfo kernel-module-driver-name-from-Driver:'' _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hey Jim, thanks for all your help. Being a Linux newbie that was a tall order, but I think I got through it OK :)) At the bottom are the outputs: -Hans>>> jim burns <jim_burn@bellsouth.net> 6/20/2008 7:27 PM >>>On Friday June 20 2008 09:33:31 am Hans Pfeil wrote:> doneSetting up network interfaces: > lo > lo IP address: 127.0.0.1/8 > done eth0 device: Broadcom Corporation NetXtreme II BCM5708 Gigabit > Ethernet (rev 12) eth0 configuration: eth-id-00:1e:c9:ad:77:0a > eth0 IP address: xxx.xxx.xxx.xxx > done eth1 device: Broadcom Corporation NetXtreme II BCM5708 Gigabit > Ethernet (rev 12) eth1 configuration: eth-id-00:1e:c9:ad:77:08 > eth1 IP address: xxx.xxx.xxx.xxx > > doneWaiting for mandatory devices: eth-id-00:1b:21:17:ee:30 > eth-id-00:1b:21:17:ee:31 eth-id-00:1b:21:17:ee:34 eth-id-00:1b:21:17:ee:35 > eth-id-00:1b:21:17:f8:20 eth-id-00:1b:21:17:f8:21 eth-id-00:1b:21:17:f8:24 > eth-id-00:1b:21:17:f8:25 __NSC__ 19 18 17 16 15 14 13 12 11 10 8 7 6 5 4 3 > 2 1 0 > eth-id-00:1b:21:17:ee:30 No interface foundHmm - post the following outputs: 1) cat /etc/sysconfig/network/ifcfg-eth-id-00:1e:c9:ad:77:0a (that is eth0) 2) cat /etc/sysconfig/network/ifcfg-eth-id-00:1b:21:17:ee:30 (that is eth2) 3) grep eth /etc/modprobe.conf* /etc/modprobe.d/* 4) ls -alF /lib/modules 5) uname -a (when booted into kernel-default and kernel-xen/xenpae) 6) hwinfo --netcard (in both kernel-default and kernel-xen/xenpae) 7) #6 will tell you the kernel module name under ''Driver:'', in kernel-xen/xenpae, give me the output of ''modinfo kernel-module-driver-name-from-Driver:'' SLES MODE: # cat /etc/sysconfig/network/ifcfg-eth-id-00:1e:c9:ad:77:0a BOOTPROTO=''static'' BROADCAST='''' ETHTOOL_OPTIONS='''' IPADDR=''xxx.xxx.xxx.201'' MTU='''' NAME=''Dell NetXtreme II BCM5708 Gigabit Ethernet'' NETMASK=''255.255.255.0'' NETWORK='''' REMOTE_IPADDR='''' STARTMODE=''auto'' UNIQUE=''rBUF.swy66v437tA'' USERCONTROL=''no'' _nm_name=''bus-pci-0000:07:00.0'' PREFIXLEN='''' # cat /etc/sysconfig/network/ifcfg-eth-id-00:1b:21:17:ee:30 BOOTPROTO=''static'' BROADCAST='''' ETHTOOL_OPTIONS='''' IPADDR=''xxx.xxx.xxx.202'' MTU='''' NAME=''Intel Ethernet controller'' NETMASK=''255.255.255.0'' NETWORK='''' REMOTE_IPADDR='''' STARTMODE=''auto'' UNIQUE=''mY_N.efaZKna8EY8'' USERCONTROL=''no'' _nm_name=''bus-pci-0000:0c:00.0'' # grep eth /etc/modprobe.conf*/etc/modprobe.d/* grep: /etc/modprobe.conf*/etc/modprobe.d/*: No such file or directory # ls -alF /lib/modules total 4 drwxr-xr-x 4 root root 128 Jun 19 12:06 ./ drwxr-xr-x 9 root root 3528 Jun 19 12:05 ../ drwxr-xr-x 3 root root 528 Jun 19 12:27 2.6.16.54-0.2.5-smp/ drwxr-xr-x 3 root root 528 Jun 19 12:06 2.6.16.54-0.2.5-xen/ # uname -a Linux xxxx 2.6.16.54-0.2.5-smp #1 SMP Mon Jan 21 13:29:51 UTC 2008 x86_64 x86_64 x86_64 GNU/Linux # hwinfo --netcard 34: PCI 300.0: 0200 Ethernet controller [Created at pci.312] UDI: /org/freedesktop/Hal/devices/pci_14e4_164c Unique ID: JNkJ.swy66v437tA Parent ID: B35A.w3JJhplF_tC SysFS ID: /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0 SysFS BusID: 0000:03:00.0 Hardware Class: network Model: "Dell NetXtreme II BCM5708 Gigabit Ethernet" Vendor: pci 0x14e4 "Broadcom" Device: pci 0x164c "NetXtreme II BCM5708 Gigabit Ethernet" SubVendor: pci 0x1028 "Dell" SubDevice: pci 0x01b3 Revision: 0x12 Driver: "bnx2" Device File: eth1 Memory Range: 0xda000000-0xdbffffff (rw,non-prefetchable) IRQ: 83 (3 events) HW Address: 00:1e:c9:ad:77:08 Link detected: no Module Alias: "pci:v000014E4d0000164Csv00001028sd000001B3bc02sc00i00" Driver Info #0: Driver Status: bnx2 is active Driver Activation Cmd: "modprobe bnx2" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #33 (PCI bridge) 40: PCI 700.0: 0200 Ethernet controller [Created at pci.312] UDI: /org/freedesktop/Hal/devices/pci_14e4_164c_0 Unique ID: rBUF.swy66v437tA Parent ID: vTuk.w3JJhplF_tC SysFS ID: /devices/pci0000:00/0000:00:02.0/0000:04:00.0/0000:05:00.0/0000:06:00.0/0000:07:00.0 SysFS BusID: 0000:07:00.0 Hardware Class: network Model: "Dell NetXtreme II BCM5708 Gigabit Ethernet" Vendor: pci 0x14e4 "Broadcom" Device: pci 0x164c "NetXtreme II BCM5708 Gigabit Ethernet" SubVendor: pci 0x1028 "Dell" SubDevice: pci 0x01b3 Revision: 0x12 Driver: "bnx2" Device File: eth0 Memory Range: 0xd6000000-0xd7ffffff (rw,non-prefetchable) IRQ: 75 (192 events) HW Address: 00:1e:c9:ad:77:0a Link detected: yes Module Alias: "pci:v000014E4d0000164Csv00001028sd000001B3bc02sc00i00" Driver Info #0: Driver Status: bnx2 is active Driver Activation Cmd: "modprobe bnx2" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #39 (PCI bridge) 44: PCI c00.0: 0200 Ethernet controller [Created at pci.312] UDI: /org/freedesktop/Hal/devices/pci_8086_10d6_6 Unique ID: mY_N.efaZKna8EY8 Parent ID: Sz_O.e6pgl_MbRFD SysFS ID: /devices/pci0000:00/0000:00:04.0/0000:0a:00.0/0000:0b:02.0/0000:0c:00.0 SysFS BusID: 0000:0c:00.0 Hardware Class: network Model: "Intel Ethernet controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x10d6 SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x147a Revision: 0x02 Driver: "igb" Device File: eth2 Memory Range: 0xd3ee0000-0xd3efffff (rw,non-prefetchable) Memory Range: 0xd3c00000-0xd3dfffff (rw,non-prefetchable) I/O Ports: 0xdce0-0xdcff (rw) Memory Range: 0xd3edc000-0xd3edffff (rw,non-prefetchable) IRQ: 98 (no events) HW Address: 00:1b:21:17:ee:30 Link detected: no Module Alias: "pci:v00008086d000010D6sv00008086sd0000147Abc02sc00i00" Driver Info #0: Driver Status: igb is active Driver Activation Cmd: "modprobe igb" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #42 (PCI bridge) 45: PCI c00.1: 0200 Ethernet controller [Created at pci.312] UDI: /org/freedesktop/Hal/devices/pci_8086_10d6_5 Unique ID: DkES.efaZKna8EY8 Parent ID: Sz_O.e6pgl_MbRFD SysFS ID: /devices/pci0000:00/0000:00:04.0/0000:0a:00.0/0000:0b:02.0/0000:0c:00.1 SysFS BusID: 0000:0c:00.1 Hardware Class: network Model: "Intel Ethernet controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x10d6 SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x147a Revision: 0x02 Driver: "igb" Device File: eth3 Memory Range: 0xd3ea0000-0xd3ebffff (rw,non-prefetchable) Memory Range: 0xd3a00000-0xd3bfffff (rw,non-prefetchable) I/O Ports: 0xdcc0-0xdcdf (rw) Memory Range: 0xd3ed8000-0xd3edbfff (rw,non-prefetchable) IRQ: 130 (no events) HW Address: 00:1b:21:17:ee:31 Link detected: no Module Alias: "pci:v00008086d000010D6sv00008086sd0000147Abc02sc00i00" Driver Info #0: Driver Status: igb is active Driver Activation Cmd: "modprobe igb" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #42 (PCI bridge) 46: PCI d00.0: 0200 Ethernet controller [Created at pci.312] UDI: /org/freedesktop/Hal/devices/pci_8086_10d6_4 Unique ID: gvUW.efaZKna8EY8 Parent ID: cB5L.e6pgl_MbRFD SysFS ID: /devices/pci0000:00/0000:00:04.0/0000:0a:00.0/0000:0b:04.0/0000:0d:00.0 SysFS BusID: 0000:0d:00.0 Hardware Class: network Model: "Intel Ethernet controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x10d6 SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x147a Revision: 0x02 Driver: "igb" Device File: eth4 Memory Range: 0xd38e0000-0xd38fffff (rw,non-prefetchable) Memory Range: 0xd3600000-0xd37fffff (rw,non-prefetchable) I/O Ports: 0xcce0-0xccff (rw) Memory Range: 0xd38dc000-0xd38dffff (rw,non-prefetchable) IRQ: 169 (17095 events) HW Address: 00:1b:21:17:ee:34 Link detected: no Module Alias: "pci:v00008086d000010D6sv00008086sd0000147Abc02sc00i00" Driver Info #0: Driver Status: igb is active Driver Activation Cmd: "modprobe igb" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #43 (PCI bridge) 47: PCI d00.1: 0200 Ethernet controller [Created at pci.312] UDI: /org/freedesktop/Hal/devices/pci_8086_10d6_3 Unique ID: 75la.efaZKna8EY8 Parent ID: cB5L.e6pgl_MbRFD SysFS ID: /devices/pci0000:00/0000:00:04.0/0000:0a:00.0/0000:0b:04.0/0000:0d:00.1 SysFS BusID: 0000:0d:00.1 Hardware Class: network Model: "Intel Ethernet controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x10d6 SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x147a Revision: 0x02 Driver: "igb" Device File: eth5 Memory Range: 0xd38a0000-0xd38bffff (rw,non-prefetchable) Memory Range: 0xd3400000-0xd35fffff (rw,non-prefetchable) I/O Ports: 0xccc0-0xccdf (rw) Memory Range: 0xd38d8000-0xd38dbfff (rw,non-prefetchable) IRQ: 170 (no events) HW Address: 00:1b:21:17:ee:35 Link detected: no Module Alias: "pci:v00008086d000010D6sv00008086sd0000147Abc02sc00i00" Driver Info #0: Driver Status: igb is active Driver Activation Cmd: "modprobe igb" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #43 (PCI bridge) 51: PCI 1100.0: 0200 Ethernet controller [Created at pci.312] UDI: /org/freedesktop/Hal/devices/pci_8086_10d6_2 Unique ID: aG+e.efaZKna8EY8 Parent ID: rE+6.e6pgl_MbRFD SysFS ID: /devices/pci0000:00/0000:00:06.0/0000:0f:00.0/0000:10:02.0/0000:11:00.0 SysFS BusID: 0000:11:00.0 Hardware Class: network Model: "Intel Ethernet controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x10d6 SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x147a Revision: 0x02 Driver: "igb" Device File: eth6 Memory Range: 0xd2ee0000-0xd2efffff (rw,non-prefetchable) Memory Range: 0xd2c00000-0xd2dfffff (rw,non-prefetchable) I/O Ports: 0xbce0-0xbcff (rw) Memory Range: 0xd2edc000-0xd2edffff (rw,non-prefetchable) IRQ: 98 (no events) HW Address: 00:1b:21:17:f8:20 Link detected: no Module Alias: "pci:v00008086d000010D6sv00008086sd0000147Abc02sc00i00" Driver Info #0: Driver Status: igb is active Driver Activation Cmd: "modprobe igb" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #49 (PCI bridge) 52: PCI 1100.1: 0200 Ethernet controller [Created at pci.312] UDI: /org/freedesktop/Hal/devices/pci_8086_10d6_1 Unique ID: GjA8.efaZKna8EY8 Parent ID: rE+6.e6pgl_MbRFD SysFS ID: /devices/pci0000:00/0000:00:06.0/0000:0f:00.0/0000:10:02.0/0000:11:00.1 SysFS BusID: 0000:11:00.1 Hardware Class: network Model: "Intel Ethernet controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x10d6 SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x147a Revision: 0x02 Driver: "igb" Device File: eth7 Memory Range: 0xd2ea0000-0xd2ebffff (rw,non-prefetchable) Memory Range: 0xd2a00000-0xd2bfffff (rw,non-prefetchable) I/O Ports: 0xbcc0-0xbcdf (rw) Memory Range: 0xd2ed8000-0xd2edbfff (rw,non-prefetchable) IRQ: 130 (no events) HW Address: 00:1b:21:17:f8:21 Link detected: no Module Alias: "pci:v00008086d000010D6sv00008086sd0000147Abc02sc00i00" Driver Info #0: Driver Status: igb is active Driver Activation Cmd: "modprobe igb" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #49 (PCI bridge) 53: PCI 1200.0: 0200 Ethernet controller [Created at pci.312] UDI: /org/freedesktop/Hal/devices/pci_8086_10d6_0 Unique ID: juQC.efaZKna8EY8 Parent ID: +S53.e6pgl_MbRFD SysFS ID: /devices/pci0000:00/0000:00:06.0/0000:0f:00.0/0000:10:04.0/0000:12:00.0 SysFS BusID: 0000:12:00.0 Hardware Class: network Model: "Intel Ethernet controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x10d6 SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x147a Revision: 0x02 Driver: "igb" Device File: eth8 Memory Range: 0xd28e0000-0xd28fffff (rw,non-prefetchable) Memory Range: 0xd2600000-0xd27fffff (rw,non-prefetchable) I/O Ports: 0xace0-0xacff (rw) Memory Range: 0xd28dc000-0xd28dffff (rw,non-prefetchable) IRQ: 169 (17095 events) HW Address: 00:1b:21:17:f8:24 Link detected: no Module Alias: "pci:v00008086d000010D6sv00008086sd0000147Abc02sc00i00" Driver Info #0: Driver Status: igb is active Driver Activation Cmd: "modprobe igb" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #50 (PCI bridge) 54: PCI 1200.1: 0200 Ethernet controller [Created at pci.312] UDI: /org/freedesktop/Hal/devices/pci_8086_10d6 Unique ID: A4hG.efaZKna8EY8 Parent ID: +S53.e6pgl_MbRFD SysFS ID: /devices/pci0000:00/0000:00:06.0/0000:0f:00.0/0000:10:04.0/0000:12:00.1 SysFS BusID: 0000:12:00.1 Hardware Class: network Model: "Intel Ethernet controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x10d6 SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x147a Revision: 0x02 Driver: "igb" Device File: eth9 Memory Range: 0xd28a0000-0xd28bffff (rw,non-prefetchable) Memory Range: 0xd2400000-0xd25fffff (rw,non-prefetchable) I/O Ports: 0xacc0-0xacdf (rw) Memory Range: 0xd28d8000-0xd28dbfff (rw,non-prefetchable) IRQ: 170 (no events) HW Address: 00:1b:21:17:f8:25 Link detected: no Module Alias: "pci:v00008086d000010D6sv00008086sd0000147Abc02sc00i00" Driver Info #0: Driver Status: igb is active Driver Activation Cmd: "modprobe igb" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #50 (PCI bridge) XEN MODE: # cat /etc/sysconfig/network/ifcfg-eth-id-00:1e:c9:ad:77:0a BOOTPROTO=''static'' BROADCAST='''' ETHTOOL_OPTIONS='''' IPADDR=''xxx.xxx.xxx.201'' MTU='''' NAME=''Dell NetXtreme II BCM5708 Gigabit Ethernet'' NETMASK=''255.255.255.0'' NETWORK='''' REMOTE_IPADDR='''' STARTMODE=''auto'' UNIQUE=''rBUF.swy66v437tA'' USERCONTROL=''no'' _nm_name=''bus-pci-0000:07:00.0'' PREFIXLEN='''' # cat /etc/sysconfig/network/ifcfg-eth-id-00:1b:21:17:ee:30 BOOTPROTO=''static'' BROADCAST='''' ETHTOOL_OPTIONS='''' IPADDR=''xxx.xxx.xxx.202'' MTU='''' NAME=''Intel Ethernet controller'' NETMASK=''255.255.255.0'' NETWORK='''' REMOTE_IPADDR='''' STARTMODE=''auto'' UNIQUE=''mY_N.efaZKna8EY8'' USERCONTROL=''no'' _nm_name=''bus-pci-0000:0c:00.0'' # grep eth /etc/modprobe.conf* /etc/modprobe.d/* /etc/modprobe.conf:install eth0 /bin/true /etc/modprobe.conf:install eth1 /bin/true /etc/modprobe.conf:# options eth16i io=0x2a0 irq=10 /etc/modprobe.conf:# ppp over ethernet /etc/modprobe.conf:alias tap0 ethertap /etc/modprobe.conf:alias tap1 ethertap /etc/modprobe.conf:alias tap2 ethertap /etc/modprobe.conf:alias tap3 ethertap /etc/modprobe.conf:alias tap4 ethertap /etc/modprobe.conf:alias tap5 ethertap /etc/modprobe.conf:alias tap6 ethertap /etc/modprobe.conf:alias tap7 ethertap /etc/modprobe.conf:alias tap8 ethertap /etc/modprobe.conf:alias tap9 ethertap /etc/modprobe.conf:alias tap10 ethertap /etc/modprobe.conf:alias tap11 ethertap /etc/modprobe.conf:alias tap12 ethertap /etc/modprobe.conf:alias tap13 ethertap /etc/modprobe.conf:alias tap14 ethertap /etc/modprobe.conf:alias tap15 ethertap /etc/modprobe.d/blacklist:blacklist eth1394 # ls -alF /lib/modules total 4 drwxr-xr-x 4 root root 128 Jun 19 12:06 ./ drwxr-xr-x 9 root root 3528 Jun 19 12:05 ../ drwxr-xr-x 3 root root 528 Jun 19 12:27 2.6.16.54-0.2.5-smp/ drwxr-xr-x 3 root root 528 Jun 19 12:06 2.6.16.54-0.2.5-xen/ # uname -a Linux xxxxx 2.6.16.54-0.2.5-xen #1 SMP Mon Jan 21 13:29:51 UTC 2008 x86_64 x86_64 x86_64 GNU/Linux # hwinfo --netcard 33: PCI 300.0: 0200 Ethernet controller [Created at pci.312] UDI: /org/freedesktop/Hal/devices/pci_14e4_164c Unique ID: nl78.swy66v437tA Parent ID: B35A.w3JJhplF_tC SysFS ID: /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0 SysFS BusID: 0000:03:00.0 Hardware Class: network Model: "Dell NetXtreme II BCM5708 Gigabit Ethernet" Vendor: pci 0x14e4 "Broadcom" Device: pci 0x164c "NetXtreme II BCM5708 Gigabit Ethernet" SubVendor: pci 0x1028 "Dell" SubDevice: pci 0x01b3 Revision: 0x12 Driver: "bnx2" Device File: peth1 Memory Range: 0xda000000-0xdbffffff (rw,non-prefetchable) IRQ: 16 (12504 events) HW Address: fe:ff:ff:ff:ff:ff Link detected: no Module Alias: "pci:v000014E4d0000164Csv00001028sd000001B3bc02sc00i00" Driver Info #0: Driver Status: bnx2 is active Driver Activation Cmd: "modprobe bnx2" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #32 (PCI bridge) 39: PCI 700.0: 0200 Ethernet controller [Created at pci.312] UDI: /org/freedesktop/Hal/devices/pci_14e4_164c_0 Unique ID: rBUF.swy66v437tA Parent ID: vTuk.w3JJhplF_tC SysFS ID: /devices/pci0000:00/0000:00:02.0/0000:04:00.0/0000:05:00.0/0000:06:00.0/0000:07:00.0 SysFS BusID: 0000:07:00.0 Hardware Class: network Model: "Dell NetXtreme II BCM5708 Gigabit Ethernet" Vendor: pci 0x14e4 "Broadcom" Device: pci 0x164c "NetXtreme II BCM5708 Gigabit Ethernet" SubVendor: pci 0x1028 "Dell" SubDevice: pci 0x01b3 Revision: 0x12 Driver: "bnx2" Device File: eth0 Memory Range: 0xd6000000-0xd7ffffff (rw,non-prefetchable) IRQ: 16 (12504 events) HW Address: 00:1e:c9:ad:77:0a Link detected: yes Module Alias: "pci:v000014E4d0000164Csv00001028sd000001B3bc02sc00i00" Driver Info #0: Driver Status: bnx2 is active Driver Activation Cmd: "modprobe bnx2" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #38 (PCI bridge) 43: PCI c00.0: 0200 Ethernet controller [Created at pci.312] UDI: /org/freedesktop/Hal/devices/pci_8086_10d6_6 Unique ID: zb5c.efaZKna8EY8 Parent ID: Sz_O.e6pgl_MbRFD SysFS ID: /devices/pci0000:00/0000:00:04.0/0000:0a:00.0/0000:0b:02.0/0000:0c:00.0 SysFS BusID: 0000:0c:00.0 Hardware Class: network Model: "Intel Ethernet controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x10d6 SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x147a Revision: 0x02 Memory Range: 0xd3ee0000-0xd3efffff (rw,non-prefetchable) Memory Range: 0xd3c00000-0xd3dfffff (rw,non-prefetchable) I/O Ports: 0xdce0-0xdcff (rw) Memory Range: 0xd3edc000-0xd3edffff (rw,non-prefetchable) IRQ: 11 (no events) Module Alias: "pci:v00008086d000010D6sv00008086sd0000147Abc02sc00i00" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #41 (PCI bridge) 44: PCI c00.1: 0200 Ethernet controller [Created at pci.312] UDI: /org/freedesktop/Hal/devices/pci_8086_10d6_5 Unique ID: rwaR.efaZKna8EY8 Parent ID: Sz_O.e6pgl_MbRFD SysFS ID: /devices/pci0000:00/0000:00:04.0/0000:0a:00.0/0000:0b:02.0/0000:0c:00.1 SysFS BusID: 0000:0c:00.1 Hardware Class: network Model: "Intel Ethernet controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x10d6 SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x147a Revision: 0x02 Memory Range: 0xd3ea0000-0xd3ebffff (rw,non-prefetchable) Memory Range: 0xd3a00000-0xd3bfffff (rw,non-prefetchable) I/O Ports: 0xdcc0-0xdcdf (rw) Memory Range: 0xd3ed8000-0xd3edbfff (rw,non-prefetchable) IRQ: 10 (no events) Module Alias: "pci:v00008086d000010D6sv00008086sd0000147Abc02sc00i00" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #41 (PCI bridge) 45: PCI d00.0: 0200 Ethernet controller [Created at pci.312] UDI: /org/freedesktop/Hal/devices/pci_8086_10d6_4 Unique ID: fSIl.efaZKna8EY8 Parent ID: cB5L.e6pgl_MbRFD SysFS ID: /devices/pci0000:00/0000:00:04.0/0000:0a:00.0/0000:0b:04.0/0000:0d:00.0 SysFS BusID: 0000:0d:00.0 Hardware Class: network Model: "Intel Ethernet controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x10d6 SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x147a Revision: 0x02 Memory Range: 0xd38e0000-0xd38fffff (rw,non-prefetchable) Memory Range: 0xd3600000-0xd37fffff (rw,non-prefetchable) I/O Ports: 0xcce0-0xccff (rw) Memory Range: 0xd38dc000-0xd38dffff (rw,non-prefetchable) IRQ: 5 (no events) Module Alias: "pci:v00008086d000010D6sv00008086sd0000147Abc02sc00i00" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #42 (PCI bridge) 46: PCI d00.1: 0200 Ethernet controller [Created at pci.312] UDI: /org/freedesktop/Hal/devices/pci_8086_10d6_3 Unique ID: Wnna.efaZKna8EY8 Parent ID: cB5L.e6pgl_MbRFD SysFS ID: /devices/pci0000:00/0000:00:04.0/0000:0a:00.0/0000:0b:04.0/0000:0d:00.1 SysFS BusID: 0000:0d:00.1 Hardware Class: network Model: "Intel Ethernet controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x10d6 SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x147a Revision: 0x02 Memory Range: 0xd38a0000-0xd38bffff (rw,non-prefetchable) Memory Range: 0xd3400000-0xd35fffff (rw,non-prefetchable) I/O Ports: 0xccc0-0xccdf (rw) Memory Range: 0xd38d8000-0xd38dbfff (rw,non-prefetchable) IRQ: 6 (no events) Module Alias: "pci:v00008086d000010D6sv00008086sd0000147Abc02sc00i00" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #42 (PCI bridge) 50: PCI 1100.0: 0200 Ethernet controller [Created at pci.312] UDI: /org/freedesktop/Hal/devices/pci_8086_10d6_2 Unique ID: Nt5K.efaZKna8EY8 Parent ID: rE+6.e6pgl_MbRFD SysFS ID: /devices/pci0000:00/0000:00:06.0/0000:0f:00.0/0000:10:02.0/0000:11:00.0 SysFS BusID: 0000:11:00.0 Hardware Class: network Model: "Intel Ethernet controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x10d6 SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x147a Revision: 0x02 Memory Range: 0xd2ee0000-0xd2efffff (rw,non-prefetchable) Memory Range: 0xd2c00000-0xd2dfffff (rw,non-prefetchable) I/O Ports: 0xbce0-0xbcff (rw) Memory Range: 0xd2edc000-0xd2edffff (rw,non-prefetchable) IRQ: 11 (no events) Module Alias: "pci:v00008086d000010D6sv00008086sd0000147Abc02sc00i00" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #48 (PCI bridge) 51: PCI 1100.1: 0200 Ethernet controller [Created at pci.312] UDI: /org/freedesktop/Hal/devices/pci_8086_10d6_1 Unique ID: ECb9.efaZKna8EY8 Parent ID: rE+6.e6pgl_MbRFD SysFS ID: /devices/pci0000:00/0000:00:06.0/0000:0f:00.0/0000:10:02.0/0000:11:00.1 SysFS BusID: 0000:11:00.1 Hardware Class: network Model: "Intel Ethernet controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x10d6 SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x147a Revision: 0x02 Memory Range: 0xd2ea0000-0xd2ebffff (rw,non-prefetchable) Memory Range: 0xd2a00000-0xd2bfffff (rw,non-prefetchable) I/O Ports: 0xbcc0-0xbcdf (rw) Memory Range: 0xd2ed8000-0xd2edbfff (rw,non-prefetchable) IRQ: 10 (no events) Module Alias: "pci:v00008086d000010D6sv00008086sd0000147Abc02sc00i00" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #48 (PCI bridge) 52: PCI 1200.0: 0200 Ethernet controller [Created at pci.312] UDI: /org/freedesktop/Hal/devices/pci_8086_10d6_0 Unique ID: 2kIT.efaZKna8EY8 Parent ID: +S53.e6pgl_MbRFD SysFS ID: /devices/pci0000:00/0000:00:06.0/0000:0f:00.0/0000:10:04.0/0000:12:00.0 SysFS BusID: 0000:12:00.0 Hardware Class: network Model: "Intel Ethernet controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x10d6 SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x147a Revision: 0x02 Memory Range: 0xd28e0000-0xd28fffff (rw,non-prefetchable) Memory Range: 0xd2600000-0xd27fffff (rw,non-prefetchable) I/O Ports: 0xace0-0xacff (rw) Memory Range: 0xd28dc000-0xd28dffff (rw,non-prefetchable) IRQ: 5 (no events) Module Alias: "pci:v00008086d000010D6sv00008086sd0000147Abc02sc00i00" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #49 (PCI bridge) 53: PCI 1200.1: 0200 Ethernet controller [Created at pci.312] UDI: /org/freedesktop/Hal/devices/pci_8086_10d6 Unique ID: v2oI.efaZKna8EY8 Parent ID: +S53.e6pgl_MbRFD SysFS ID: /devices/pci0000:00/0000:00:06.0/0000:0f:00.0/0000:10:04.0/0000:12:00.1 SysFS BusID: 0000:12:00.1 Hardware Class: network Model: "Intel Ethernet controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x10d6 SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x147a Revision: 0x02 Memory Range: 0xd28a0000-0xd28bffff (rw,non-prefetchable) Memory Range: 0xd2400000-0xd25fffff (rw,non-prefetchable) I/O Ports: 0xacc0-0xacdf (rw) Memory Range: 0xd28d8000-0xd28dbfff (rw,non-prefetchable) IRQ: 6 (no events) Module Alias: "pci:v00008086d000010D6sv00008086sd0000147Abc02sc00i00" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #49 (PCI bridge) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Jim, Thanks so much. I would have never thought of this. A coworker suggested to INSTALL the drivers in XEN mode. Didn''t think I would have to install them twice, once in normal SLES mode and then again in XEN mode. That did the trick. All is up and running. -Hans>>> jim burns <jim_burn@bellsouth.net> 6/20/2008 7:27 PM >>>On Friday June 20 2008 09:33:31 am Hans Pfeil wrote:> doneSetting up network interfaces: > lo > lo IP address: 127.0.0.1/8 > done eth0 device: Broadcom Corporation NetXtreme II BCM5708 Gigabit > Ethernet (rev 12) eth0 configuration: eth-id-00:1e:c9:ad:77:0a > eth0 IP address: xxx.xxx.xxx.xxx > done eth1 device: Broadcom Corporation NetXtreme II BCM5708 Gigabit > Ethernet (rev 12) eth1 configuration: eth-id-00:1e:c9:ad:77:08 > eth1 IP address: xxx.xxx.xxx.xxx > > doneWaiting for mandatory devices: eth-id-00:1b:21:17:ee:30 > eth-id-00:1b:21:17:ee:31 eth-id-00:1b:21:17:ee:34 eth-id-00:1b:21:17:ee:35 > eth-id-00:1b:21:17:f8:20 eth-id-00:1b:21:17:f8:21 eth-id-00:1b:21:17:f8:24 > eth-id-00:1b:21:17:f8:25 __NSC__ 19 18 17 16 15 14 13 12 11 10 8 7 6 5 4 3 > 2 1 0 > eth-id-00:1b:21:17:ee:30 No interface foundHmm - post the following outputs: 1) cat /etc/sysconfig/network/ifcfg-eth-id-00:1e:c9:ad:77:0a (that is eth0) 2) cat /etc/sysconfig/network/ifcfg-eth-id-00:1b:21:17:ee:30 (that is eth2) 3) grep eth /etc/modprobe.conf* /etc/modprobe.d/* 4) ls -alF /lib/modules 5) uname -a (when booted into kernel-default and kernel-xen/xenpae) 6) hwinfo --netcard (in both kernel-default and kernel-xen/xenpae) 7) #6 will tell you the kernel module name under ''Driver:'', in kernel-xen/xenpae, give me the output of ''modinfo kernel-module-driver-name-from-Driver:'' _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wednesday June 25 2008 05:20:35 pm Hans Pfeil wrote:> Thanks so much. I would have never thought of this. A coworker suggested > to INSTALL the drivers in XEN mode. Didn''t think I would have to install > them twice, once in normal SLES mode and then again in XEN mode. That did > the trick. All is up and running.Sorry, I never thought that it wasn''t a standard SLES kernel module that''s automatically present. Unlike userland, non-standard kernel modules have to be installed for each kernel you have. It was obvious from your hwinfo output that the module wasn''t being loaded. My next suggestion would have been to do a ''modprobe igb'' in xen mode. For future debugging methodology reference: 1. boot into xen 2. ''/etc/xen/scripts/network-bridge stop'' (The above is done because changes to networking have to be done with xen networking down, so that when xen networking restarts, xen picks up the changes and creates the proper ethn/pethn pairs.) 3. ''modprobe igb'' 4. if 3. errrors, do ''modinfo igb'' 5. if 4. also errors, do ''find /lib/modules -name igb.ko'' to find out which kernels have the igb driver installed. Since in your case, it was installed in 2.6.16.54-0.2.5-smp, but wasn''t installed in 2.6.16.54-0.2.5-xen, you could have taken it from there, and installed it in xen, and rebooted. 3a. if 3. succeeded, you just needed to do ''/etc/xen/scripts/network-bridge start'' to get xen networking back, and find out why the module wasn''t loaded automatically. This all assumes that you are using bridging in your xen network. That can be double-checked by looking at /etc/xen/xend-config.sxp: "grep network-script /etc/xen/xend-config.sxp|grep -v ''#''". For me, I get: (network-script network-bridge) If you get network-nat or network-route, you would substitute that above. Glad you are up. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users