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@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home