Hello again
I have a working test server with Xen 3.0.4 on Slackware 11. Everything
seems to be ok.
Now there''s the production server, which has 3 network cards. This is
not ok
with my Xen setup. I copied the complete Xen installation to the new server.
It boots, it detects all network cards (eth0, eth1, eth2).
But when I do xend start it goes wrong. I can do the xend start, but it
takes a bit longer than on the other system.
But I cannot start any domU''s.
I get the following error:
root@vm01:~# xm create -c vm_base.cfg
Using config file "/etc/xen/vm_base.cfg".
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
Configuration file /etc/xen/vm_base.cfg
kernel = "/boot/vmlinuz-2.6-xenU"
memory = 256
name = "vm_base"
vif = [ '''' ]
dhcp = "off"
ip = "10.200.1.101"
netmask = "255.255.255.0"
gateway = "10.200.1.1"
disk =
[''file:/xen/vm_base.img,sda1,w'',''file:/xen/vm_base.swap,sda2,w'']
root = "/dev/sda1 ro"
Changing the vif = [''''] line to vif0 or something, or remove
it, as
suggested in this mailing list, doesn''t work.
It has something to do with the multiple network cards, that''s for
sure.
When I start the system (without Xen), everything''s ok, I can connect
to it,
and the system can connect to anything.
When I start xend, it removes my default route to internet (why would it do
that), and creates the following network interfaces:
eth0 Link encap:Ethernet HWaddr 00:30:48:33:3B:74
inet addr:10.200.1.100 Bcast:10.200.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:140 errors:0 dropped:0 overruns:0 frame:0
TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:11774 (11.4 KiB) TX bytes:5008 (4.8 KiB)
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: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)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:1453 errors:0 dropped:0 overruns:0 frame:0
TX packets:250 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:119040 (116.2 KiB) TX bytes:42201 (41.2 KiB)
Base address:0x2000 Memory:da000000-da020000
vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:252 errors:0 dropped:0 overruns:0 frame:0
TX packets:1438 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:41418 (40.4 KiB) TX bytes:111587 (108.9 KiB)
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:1184 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:67438 (65.8 KiB) TX bytes:0 (0.0 b)
... with the known results (xm cannot start).
When I do a xend stop, that''s ok.
But when I do a xend start afterwards, it just deletes all my network cards,
making it impossible to connect to it!
Maybe there''s somethin gwrong with the network scripts, I hope someone
can
point me into the right direction?
Regards
Peter
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi Peter On Fri, Mar 16, 2007 at 07:33:31PM +0100, Peter Fastré wrote:> > I have a working test server with Xen 3.0.4 on Slackware 11. Everything > seems to be ok. > > Now there''s the production server, which has 3 network cards. This is not ok > with my Xen setup. I copied the complete Xen installation to the new server. > It boots, it detects all network cards (eth0, eth1, eth2). > But when I do xend start it goes wrong. I can do the xend start, but it > takes a bit longer than on the other system. > But I cannot start any domU''s. >What is the output of ifconfig and "route -n" before you start xend? What is it that you actually want xen to do with these three cards?> I get the following error: > root@vm01:~# xm create -c vm_base.cfg > Using config file "/etc/xen/vm_base.cfg". > Error: Device 0 (vif) could not be connected. Hotplug scripts not working. > > Configuration file /etc/xen/vm_base.cfg > kernel = "/boot/vmlinuz-2.6-xenU" > memory = 256 > name = "vm_base" > vif = [ '''' ] > dhcp = "off" > ip = "10.200.1.101" > netmask = "255.255.255.0" > gateway = "10.200.1.1" > > disk = [''file:/xen/vm_base.img,sda1,w'',''file:/xen/vm_base.swap,sda2,w''] > root = "/dev/sda1 ro" >Okay, this is not the cause of your problem, but I suggest that you don''t use dhcp, ip, netmask, and gateway settings in your configuration file. AFAIK this puts all your networking configuration on the kernel command line. It doesn''t belong there - you should configure your DomUs through their normal networking configuration files.> > Changing the vif = [''''] line to vif0 or something, or remove it, as > suggested in this mailing list, doesn''t work. > > It has something to do with the multiple network cards, that''s for sure. > When I start the system (without Xen), everything''s ok, I can connect to it, > and the system can connect to anything. > When I start xend, it removes my default route to internet (why would it do > that), and creates the following network interfaces: > eth0 Link encap:Ethernet HWaddr 00:30:48:33:3B:74 > inet addr:10.200.1.100 Bcast:10.200.1.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:140 errors:0 dropped:0 overruns:0 frame:0 > TX packets:30 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:11774 (11.4 KiB) TX bytes:5008 (4.8 KiB) > > 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: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) > > peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:1453 errors:0 dropped:0 overruns:0 frame:0 > TX packets:250 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:119040 (116.2 KiB) TX bytes:42201 (41.2 KiB) > Base address:0x2000 Memory:da000000-da020000 > > vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:252 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1438 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:41418 (40.4 KiB) TX bytes:111587 (108.9 KiB) > > 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:1184 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:67438 (65.8 KiB) TX bytes:0 (0.0 b) > > ... with the known results (xm cannot start). >Are you missing output here or have eth1 and eth2 already disappeared by this point? Also, what is the output of "brctl show" and the output of "route -n"?> When I do a xend stop, that''s ok. > But when I do a xend start afterwards, it just deletes all my network cards, > making it impossible to connect to it! > > Maybe there''s somethin gwrong with the network scripts, I hope someone can > point me into the right direction? > > Regards > > Peter> _______________________________________________ > 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
On 3/16/07, jez <jez@jinsky.com> wrote:> > > Hi Peter > > On Fri, Mar 16, 2007 at 07:33:31PM +0100, Peter Fastré wrote: > > > > I have a working test server with Xen 3.0.4 on Slackware 11. Everything > > seems to be ok. > > > > Now there''s the production server, which has 3 network cards. This is > not ok > > with my Xen setup. I copied the complete Xen installation to the new > server. > > It boots, it detects all network cards (eth0, eth1, eth2). > > But when I do xend start it goes wrong. I can do the xend start, but it > > takes a bit longer than on the other system. > > But I cannot start any domU''s. > > > > What is the output of ifconfig and "route -n" before you start xend?before start: Destination Gateway Genmask Flags Metric Ref Use Iface 10.200.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 10.200.1.1 0.0.0.0 UG 1 0 0 eth0 after start: Destination Gateway Genmask Flags Metric Ref Use Iface 10.200.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo What is it that you actually want xen to do with these three cards? The server has 3 intel cards. For the moment, I just want to use two of them, one for the public addresses (195.x.x.x) which is different for each vm, and one for a private network which would be used to mirror some things between servers.> I get the following error: > > root@vm01:~# xm create -c vm_base.cfg > > Using config file "/etc/xen/vm_base.cfg". > > Error: Device 0 (vif) could not be connected. Hotplug scripts not > working. > > > > Configuration file /etc/xen/vm_base.cfg > > kernel = "/boot/vmlinuz-2.6-xenU" > > memory = 256 > > name = "vm_base" > > vif = [ '''' ] > > dhcp = "off" > > ip = "10.200.1.101" > > netmask = "255.255.255.0" > > gateway = "10.200.1.1" > > > > disk = [''file:/xen/vm_base.img,sda1,w'',''file:/xen/vm_base.swap,sda2,w''] > > root = "/dev/sda1 ro" > > > > Okay, this is not the cause of your problem, but I suggest that you > don''t use dhcp, ip, netmask, and gateway settings in your configuration > file. AFAIK this puts all your networking configuration on the kernel > command line. It doesn''t belong there - you should configure your DomUs > through their normal networking configuration files.Removed all the ip settings (dhcp/ip/netmask/gateway). Error I get now is: root@vm01:~# xm create vm_base.cfg Using config file "/etc/xen/vm_base.cfg". Error: Device 0 (vif) could not be connected. Hotplug scripts not working. Hotplug -> do they mean udev? Udev is not changed compared to the normal installation, I think it''s working normally as it should. I did disable it for the test domU''s on my test machines (after I succesffully booted them). But on this server I can''t boot any domain.> > > Changing the vif = [''''] line to vif0 or something, or remove it, as > > suggested in this mailing list, doesn''t work. > > > > It has something to do with the multiple network cards, that''s for sure. > > When I start the system (without Xen), everything''s ok, I can connect to > it, > > and the system can connect to anything. > > When I start xend, it removes my default route to internet (why would it > do > > that), and creates the following network interfaces: > > eth0 Link encap:Ethernet HWaddr 00:30:48:33:3B:74 > > inet addr:10.200.1.100 Bcast:10.200.1.255 Mask:255.255.255.0 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:140 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:30 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:11774 (11.4 KiB) TX bytes:5008 (4.8 KiB) > > > > 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: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) > > > > peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > > RX packets:1453 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:250 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:119040 (116.2 KiB) TX bytes:42201 (41.2 KiB) > > Base address:0x2000 Memory:da000000-da020000 > > > > vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > > RX packets:252 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:1438 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:41418 (40.4 KiB) TX bytes:111587 (108.9 KiB) > > > > 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:1184 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:67438 (65.8 KiB) TX bytes:0 (0.0 b) > > > > ... with the known results (xm cannot start). > > > > Are you missing output here or have eth1 and eth2 already disappeared by > this point? > > Also, what is the output of "brctl show" and the output of "route -n"? > > root@vm01:~# brctl show > bridge name bridge id STP enabled interfaces > xenbr1 8000.feffffffffff no vif0.1 > peth0route -n you see above. I hope someone can help, I''m getting more and more desperate about this :( regards peter _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > > > > eth0 Link encap:Ethernet HWaddr 00:30:48:33:3B:74 > > > inet addr:10.200.1.100 Bcast:10.200.1.255 Mask: > > 255.255.255.0 > > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > > RX packets:140 errors:0 dropped:0 overruns:0 frame:0 > > > TX packets:30 errors:0 dropped:0 overruns:0 carrier:0 > > > collisions:0 txqueuelen:0 > > > RX bytes:11774 (11.4 KiB) TX bytes:5008 (4.8 KiB) > > >> .... > > > > > > > Are you missing output here or have eth1 and eth2 already disappeared by > > this point? > > >Forgot to answer this question. Eth1 & eth2 are actually there, but they are not given an ip address yet. Tried doing that, but no difference in the error. I still complains about some weird hotplug error. Peter _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sat, Mar 17, 2007 at 12:32:03AM +0100, Peter Fastré wrote:> On 3/16/07, jez <jez@jinsky.com> wrote: > >On Fri, Mar 16, 2007 at 07:33:31PM +0100, Peter Fastré wrote: > >> > > > >What is the output of ifconfig and "route -n" before you start xend? > > before start: > Destination Gateway Genmask Flags Metric Ref Use > Iface > 10.200.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo > 0.0.0.0 10.200.1.1 0.0.0.0 UG 1 0 0 eth0 > > after start: > Destination Gateway Genmask Flags Metric Ref Use > Iface > 10.200.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo >Re-read Peter. I also asked for the output of *ifconfig* before. Better yet, please post the output of "ip addr list" before starting xend.> > > What is it that you actually want xen to do with these three cards? > > The server has 3 intel cards. For the moment, I just want to use two of > them, one for the public addresses (195.x.x.x) which is different for each > vm, and one for a private network which would be used to mirror some things > between servers. >Are you saying you want each DomU to have two interfaces eth0 and eth1. One of those interfaces, eth0, should be connected to a bridge that contains Dom0''s public nic. The other one, eth1, should be connected to a bridge that contains Dom0s private nic? Or is it that only Dom0 needs to have access to two networks but the DomUs only need to have access to the public network - and so only need one interface each? Also, which nic is which - what do you want to do with eth0? eth1? eth2?> >Okay, this is not the cause of your problem, but I suggest that you > >don''t use dhcp, ip, netmask, and gateway settings in your configuration > >file. AFAIK this puts all your networking configuration on the kernel > >command line. It doesn''t belong there - you should configure your DomUs > >through their normal networking configuration files. > > > Removed all the ip settings (dhcp/ip/netmask/gateway). Error I get now is: > > root@vm01:~# xm create vm_base.cfg > Using config file "/etc/xen/vm_base.cfg". > Error: Device 0 (vif) could not be connected. Hotplug scripts not working. >Yeah, I said this wasn''t going to solve your problem. I was just throwing in some extra advice for free.> Hotplug -> do they mean udev? Udev is not changed compared to the normal > installation, I think it''s working normally as it should. I did disable it > for the test domU''s on my test machines (after I succesffully booted them). > But on this server I can''t boot any domain. >The scripts in /etc/xen/scripts are called via the udev system. When xen is installed it puts a set of rules in /etc/udev/ in a file called xen-backend.rules and then adds a symlink to that file in /etc/udev/rules.d. At least that is how it''s done in the Debian installation. I don''t know how you copied accross your xen system from your test server, but you should probably check that there are some xen rules somewhere under /etc/udev. However, I really doubt this is your problem. TBH I really can''t see how the xen scripts could be expected to do the right thing with your present configuration as it stands. If you can answer my question above about what exactly you want to do with eth0, eth1, and eth2, then we can try and get you a configuration that works.> >> > >> 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:1184 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:67438 (65.8 KiB) TX bytes:0 (0.0 b) > >><snip/>> root@vm01:~# brctl show > bridge name bridge id STP enabled interfaces > xenbr1 8000.feffffffffff no vif0.1 > peth0Your ifconfig says you''ve got two bridges xenbr0 and xenbr1 but the output of ''brctl show'' says you only have one bridge. Can you double check this, thanks. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sat, Mar 17, 2007 at 02:48:18AM +0100, jez wrote:> > >> > > >> 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:1184 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:67438 (65.8 KiB) TX bytes:0 (0.0 b) > > >> > <snip/> > > root@vm01:~# brctl show > > bridge name bridge id STP enabled interfaces > > xenbr1 8000.feffffffffff no vif0.1 > > peth0 > > Your ifconfig says you''ve got two bridges xenbr0 and xenbr1 but the > output of ''brctl show'' says you only have one bridge. Can you double > check this, thanks. >Okay, I should probably have read a little more between the lines from your previous posts and just assumed that all you wanted to do was to have you DomU interfaces bridged with eth0 on Dom0. You don''t care about eth1 or eth2 for the moment right? Well, if that is what you want, the main problem you''ve got at the moment is that there are two bridges and one of them doesn''t even seem to really exist. I honestly don''t have a clue how this could happen, but I can suggest something for you to try. In the file /etc/xen/xend-config.sxp, change: (network-script network-bridge) to (network-script ''network-bridge bridge=xenbr0 netdev=eth0'') Reboot your server to give it a fresh start. Then check ''ifconfig'' and also ''brctl show'' to see that there is only the one bridge, xenbr0. If all looks well, then try to start a DomU. cheers jez _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 3/17/07, jez <jez@jinsky.com> wrote:> > > > Re-read Peter. I also asked for the output of *ifconfig* before. Better > yet, please post the output of "ip addr list" before starting xend.Sorry, I really appreciate your help, and I will try to give you all the information you need. To avoid messing up these mailing list, I''ve put the information in a text file: http://peter.lunatis.be/xen/info.txt (please let me know if I should mail the full info.txt)> > > > What is it that you actually want xen to do with these three cards? > > > > The server has 3 intel cards. For the moment, I just want to use two of > > them, one for the public addresses (195.x.x.x) which is different for > each > > vm, and one for a private network which would be used to mirror some > things > > between servers. > > > > Are you saying you want each DomU to have two interfaces eth0 and eth1. > One of those interfaces, eth0, should be connected to a bridge that > contains Dom0''s public nic. The other one, eth1, should be connected to a > bridge that contains Dom0s private nic?That''s exactly what I want. But as you said in your other mail, for now I would be happy with a functioning eth0 only (on dom0 & domU''s). Yeah, I said this wasn''t going to solve your problem. I was just throwing> in some extra advice for free.I do appreciate your help. The big problem with Xen is (imho) that''s is difficult to setup, because of the very limited documentation. But I''ve come this far (had some other trouble before) and now I don''t want to give up!> Hotplug -> do they mean udev? Udev is not changed compared to the normal > > installation, I think it''s working normally as it should. I did disable > it > > for the test domU''s on my test machines (after I succesffully booted > them). > > But on this server I can''t boot any domain. > > > > The scripts in /etc/xen/scripts are called via the udev system. When xen > is installed it puts a set of rules in /etc/udev/ in a file called > xen-backend.rules and then adds a symlink to that file in > /etc/udev/rules.d. At least that is how it''s done in the Debian > installation. I don''t know how you copied accross your xen system from > your test server, but you should probably check that there are some xen > rules somewhere under /etc/udev.This is exactly how it''s done on my system. There''s a set of rules ( xen-backend.rules) in the directory /etc/udev, and the symlink under rules.d is there. Contents of the file: SUBSYSTEM=="xen-backend", KERNEL=="tap*", RUN+="/etc/xen/scripts/blktap $env{ACTION}" SUBSYSTEM=="xen-backend", KERNEL=="vbd*", RUN+="/etc/xen/scripts/block $env{ACTION}" SUBSYSTEM=="xen-backend", KERNEL=="vtpm*", RUN+="/etc/xen/scripts/vtpm $env{ACTION}" SUBSYSTEM=="xen-backend", KERNEL=="vif*", ACTION=="online", RUN+="$env{script} online" SUBSYSTEM=="xen-backend", KERNEL=="vif*", ACTION=="offline", RUN+="$env{script} offline" SUBSYSTEM=="xen-backend", ACTION=="remove", RUN+="/etc/xen/scripts/xen-hotplug-cleanup" KERNEL=="evtchn", NAME="xen/%k" KERNEL=="blktap[0-9]*", NAME="xen/%k" However, I really doubt this is your problem. TBH I really can''t see how> the xen scripts could be expected to do the right thing with your > present configuration as it stands. If you can answer my question above > about what exactly you want to do with eth0, eth1, and eth2, then we > can try and get you a configuration that works.> >> > > >> 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:1184 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:67438 (65.8 KiB) TX bytes:0 (0.0 b) > > >> > <snip/> > > root@vm01:~# brctl show > > bridge name bridge id STP enabled interfaces > > xenbr1 8000.feffffffffff no vif0.1 > > peth0 > > > Your ifconfig says you''ve got two bridges xenbr0 and xenbr1 but the > output of ''brctl show'' says you only have one bridge. Can you double > check this, thanks.That''s ok now. As you can see in the text file, there''s one bridge in the ifconfig xenbr1. But xenbr1, does this mean this is a bridge to eth1? Probably not, because it seems to work this way on my test machine. Now I will try your suggestions in the other mail! Regards Peter _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 3/17/07, jez <jez@jinsky.com> wrote:> > > Okay, I should probably have read a little more between the lines from > your previous posts and just assumed that all you wanted to do was to > have you DomU interfaces bridged with eth0 on Dom0. You don''t care > about eth1 or eth2 for the moment right? > > Well, if that is what you want, the main problem you''ve got at the > moment is that there are two bridges and one of them doesn''t even seem > to really exist. I honestly don''t have a clue how this could happen, but > I can suggest something for you to try. > > In the file /etc/xen/xend-config.sxp, change: > > (network-script network-bridge) > > to > > (network-script ''network-bridge bridge=xenbr0 netdev=eth0'')I''ve done this. Now my ifconfig output is this: eth0 Link encap:Ethernet HWaddr 00:30:48:33:3B:74 inet addr:10.200.1.100 Bcast:0.0.0.0 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:182 errors:0 dropped:0 overruns:0 frame:0 TX packets:52 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:13024 (12.7 KiB) TX bytes:5656 (5.5 KiB) eth1 Link encap:Ethernet HWaddr 00:30:48:33:3B:75 inet addr:10.201.1.100 Bcast:10.201.1.255 Mask:255.255.255.0 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) Base address:0x2020 Memory:da020000-da040000 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: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) peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:308 errors:0 dropped:0 overruns:0 frame:0 TX packets:94 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:24450 (23.8 KiB) TX bytes:14650 (14.3 KiB) Base address:0x2000 Memory:da000000-da020000 vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:52 errors:0 dropped:0 overruns:0 frame:0 TX packets:182 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:5656 (5.5 KiB) TX bytes:13024 (12.7 KiB) xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:130 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:6246 (6.0 KiB) TX bytes:0 (0.0 b) root@vm01:~# brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no vif0.1 peth0 Seems to be a little better? But the default route is still gone after starting xen. Reboot your server to give it a fresh start. Then check ''ifconfig'' and> also ''brctl show'' to see that there is only the one bridge, xenbr0. If > all looks well, then try to start a DomU.Still no success. I''m doing some research on my own (mailling list/internet/configuration examples), and tried a lot of different values in the .sxp files, in the configuration files. I tried changing the vif section: # By default, no network interfaces are configured. You may have one created # with sensible defaults using an empty vif clause: # # vif = [ '''' ] # # or optionally override backend, bridge, ip, mac, script, type, or vifname: # # vif = [ ''mac=00:16:3e:00:00:11, bridge=xenbr0'' ] # # or more than one interface may be configured: # # vif = [ '''', ''bridge=xenbr1'' ] When I read this, one would think that it''s possible to boot a vm without network interface? I know this wouldn''t make sense, but it could be useful for testing, not? But when I remove the vif option, the vm also doesn''t boot. Another thing I try. I set the line in the config.sxp back to (network-script network-bridge) When I do this, I find something strange too: root@vm01:/etc/xen/scripts# ./network-bridge status ===========================================================5: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue link/ether 00:30:48:33:3b:75 brd ff:ff:ff:ff:ff:ff inet 10.201.1.100/24 scope global eth1 12: xenbr1: <BROADCAST,NOARP,UP> mtu 1500 qdisc noqueue link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff bridge name bridge id STP enabled interfaces xenbr1 8000.feffffffffff no vif0.1 peth1 10.200.1.0/24 dev eth0 proto kernel scope link src 10.200.1.100 10.201.1.0/24 dev eth1 proto kernel scope link src 10.201.1.100 127.0.0.0/8 dev lo scope link default via 10.200.1.1 dev eth0 metric 1 Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.200.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 10.201.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 10.200.1.1 0.0.0.0 UG 1 0 0 eth0 =========================================================== It seems it''s creating a xenbr1 because it thinks that''s my outgoing interface. So I guess your suggestion should be followed, and I have to add something to the xend-config.sxp file to get things right. If this has to do with my distribution (Slackware), please just say that. I don''t like to switch, but if necessary, I''ll do that. I tried ubuntu 6.0664-bit, which worked fine, but not all my machines are 64-bit. With ubuntu 6.06 32-bit I ran into big problems because of the TLS-libs, which should be recompiled with some options (something about no segments). I didn''t succeed doing that. I did succeed recompiling the glibc on my slackware box, so now I''m using this. But if all my problems would be resolved by choosing some other distribution, please let me know. I''m working on this Xen-setup for more than two weeks now, and I just don''t know it anymore. I considered moving to the commercial version of xen, but my server is not supported by them (3ware 9650 controller). I''m also willing to pay someone to get installation support, I just want it to work :( cheers Peter _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sat, Mar 17, 2007 at 11:22:24PM +0100, Peter Fastré wrote:> > root@vm01:~# brctl show > bridge name bridge id STP enabled interfaces > xenbr0 8000.feffffffffff no vif0.1 > peth0 > > Seems to be a little better? But the default route is still gone after > starting xen. >I''m pleased with this part. But the rest is bugging me now.> > Reboot your server to give it a fresh start. Then check ''ifconfig'' and > >also ''brctl show'' to see that there is only the one bridge, xenbr0. If > >all looks well, then try to start a DomU. > > > Still no success. > I''m doing some research on my own (mailling list/internet/configuration > examples), and tried a lot of different values in the .sxp files, in the > configuration files. > I tried changing the vif section: > > # By default, no network interfaces are configured. You may have one > created > # with sensible defaults using an empty vif clause: > # > # vif = [ '''' ] > # > # or optionally override backend, bridge, ip, mac, script, type, or vifname: > # > # vif = [ ''mac=00:16:3e:00:00:11, bridge=xenbr0'' ] > # > # or more than one interface may be configured: > # > # vif = [ '''', ''bridge=xenbr1'' ] > > When I read this, one would think that it''s possible to boot a vm without > network interface? I know this wouldn''t make sense, but it could be useful > for testing, not? But when I remove the vif option, the vm also doesn''t > boot. >I just checked back over previous posts, and I can''t find whether or not I asked you to make certain that: (vif-script vif-bridge) is set in your xend-config.sxp. This is the default setting, but I think you should check just in case. If you wanted to try to test with *no* DomU interfaces, you should set vif as follows: vif = [] This is actually a python script and you want to define an empty list - not no list. If you wanted to tell vif-bridge explicity to use the bridge we created you would do: vif = [ ''bridge=xenbr0'' ] However, if there is only one bridge in existence on your machine, the vif-bridge script will automatically use that. Please note that the vif-bridge script does *not* create bridges - it just adds and removes interfaces from bridges that already exist. The fact that you can''t start a DomU suggests that there is a bug in vif-script as far as Slackware is concerned. And the following is also a worry. It suggests to me that there is a bug in bridge-script as far as Slackware is concerned. It looks to me that your very act of trying to check the status of the bridge with "./network-bridge status" is what is responsible for corrupting the bridge. Any chance you can check the status of the bridge with "brctl show" immediately before you do this other check?> > Another thing I try. > I set the line in the config.sxp back to (network-script network-bridge) > > When I do this, I find something strange too: > root@vm01:/etc/xen/scripts# ./network-bridge status > ===========================================================> 5: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue > link/ether 00:30:48:33:3b:75 brd ff:ff:ff:ff:ff:ff > inet 10.201.1.100/24 scope global eth1 > 12: xenbr1: <BROADCAST,NOARP,UP> mtu 1500 qdisc noqueue > link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff > > bridge name bridge id STP enabled interfaces > xenbr1 8000.feffffffffff no vif0.1 > peth1 > > 10.200.1.0/24 dev eth0 proto kernel scope link src 10.200.1.100 > 10.201.1.0/24 dev eth1 proto kernel scope link src 10.201.1.100 > 127.0.0.0/8 dev lo scope link > default via 10.200.1.1 dev eth0 metric 1 > > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface > 10.200.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 > 10.201.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo > 0.0.0.0 10.200.1.1 0.0.0.0 UG 1 0 0 eth0 > ===========================================================> > > It seems it''s creating a xenbr1 because it thinks that''s my outgoing > interface. So I guess your suggestion should be followed, and I have to add > something to the xend-config.sxp file to get things right. >This stuff is just wierd.> If this has to do with my distribution (Slackware), please just say that. I > don''t like to switch, but if necessary, I''ll do that. I tried ubuntu > 6.0664-bit, which worked fine, but not all my machines are 64-bit. > With ubuntu > 6.06 32-bit I ran into big problems because of the TLS-libs, which should be > recompiled with some options (something about no segments). I didn''t succeed > doing that. I did succeed recompiling the glibc on my slackware box, so now > I''m using this. > But if all my problems would be resolved by choosing some other > distribution, please let me know. I''m working on this Xen-setup for more > than two weeks now, and I just don''t know it anymore. I considered moving to > the commercial version of xen, but my server is not supported by them (3ware > 9650 controller). I''m also willing to pay someone to get installation > support, I just want it to work :( >Okay, I don''t want to start a troll here, but... Ubuntu is great on the desktop - really great. However, if you take Ubuntu off the desktop you are using Debian - and if you''re going to use Debian then do it directly. If I was recommending a distro to you for a production environment, I''d recommend you go with Debian Etch. This said, I think there is a lot to be said for sticking with what you know. Debian has a large learning curve and it''s not one you want to climb in a production enviroment IMO. But whatever you decide to do from here, I certainly think that you should increase you options by learning a second system and learning it well. In answer to your question: Yes, I definitely think that you can get xen working with little or no fuss by switching to another distribution. However, I don''t think that the problems you are having are really that serious. It''s just likely that the shell scripts under /etc/xen/scripts need a bit of tweaking to get things working. In fact, it would be a simple matter to just by-pass the xen scripts altogether and just use your own. This is what I have done on one of my boxes. There are no really serious problems here, just misunderstandings. Anyway, I''ll ping you off-line about taking a closer look at your setup. jez _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users