[Xen-users] Re: domU networking problems openSUSE-10.3 x86_64

["Marcel Smeets" <mpgsmeets@xxxxxxxxx>]

Hi,

I solved the problem myself.

In the boot menu /boot/grub.menu.lst I added a parameter max_loop=64
to the vmlinuz module line:

module /vmlinuz-2.6.23.1-900.ccj58-xen
root=/dev/disk/by-id/scsi-SATA_ST3250820AS_5QE2G6DL-part5
resume=/dev/sda10 splash=silent showopts max_loop=64

And also copied all the kernel modules to the domU to avoid messages
about no modules found etc...:

Mount the disk image

mount -o loop /data/xen/domains/disk.img /mnt/tmp

Copy all the modules to the domU

cp -rp /lib/modules/* /mnt/tmp/lib/modules

(In the domU configuration the kernel used is the dom0 kernel : kernel
 = '/boot/vmlinuz-xen' )

Unmount the image umount /mnt/tmp and do this for all your images you use

As I did all these things, I could reboot with all the domU domains
coming up and all the networking necessary! Even the console works: xm
console domU-name gices me access

Hope someone can use this information.

Marcel Smeets

On 10/30/07, Marcel Smeets <mpgsmeets@xxxxxxxxx> wrote:
> Hi,
>
> I upgraded my OS form SUSE 10.1 to 10.2 and then openSUSE 10.3. In
> 10.1 everything worked fine. Tried several xen-kernels but the problem
> perseveres. The dom0 domain is there and working. All the 5 domU
> domains are there but only one has working network connections, so the
> other ones are useless as I can't login anymore to them through the
> console (none of the domU is accessible through the console)
>
> My kernel now is:
>
> 2.6.23.1-900.ccj58-xen #1 SMP 2007/10/26 14:17:15 UTC x86_64 x86_64
> x86_64 GNU/Linux
>
> Also tried this one: 2.6.22.9-0.4-xen and this one 2.6.22.9-ccj56-xen,
> but problem is the same
>
> Installed xen rpm packages:
>
> xen-devel-3.1.0_15042-51
> kernel-xenpae-2.6.22.9-0.4
> xen-doc-pdf-3.1.0_15042-51
> xen-libs-3.1.0_15042-51
> xen-doc-html-3.1.0_15042-51
> xen-tools-3.1.0_15042-51
> xen-3.1.0_15042-51
> kernel-xen-2.6.23.1-900.ccj58
> xen-tools-ioemu-3.1.0_15042-51
> xen-debuginfo-3.1.0_15042-51
>
> - ifconfig output
>
> eth0      Link encap:Ethernet  HWaddr 00:19:D1:43:1D:4A
>           inet addr:192.168.1.12  Bcast:192.168.1.255  Mask:255.255.255.0
>           inet6 addr: fe80::219:d1ff:fe43:1d4a/64 Scope:Link
>           UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:10901 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:9737 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:879289 (858.6 Kb)  TX bytes:2106711 (2.0 Mb)
>
> 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:17 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:1904 (1.8 Kb)  TX bytes:1904 (1.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:15338 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:14012 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           RX bytes:1242170 (1.1 Mb)  TX bytes:2954472 (2.8 Mb)
>           Base address:0xecc0 Memory:dffe0000-e0000000
>
> tap0      Link encap:Ethernet  HWaddr 00:FF:76:5F:AF:F6
>           inet6 addr: fe80::2ff:76ff:fe5f:aff6/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:270 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:903 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:500
>           RX bytes:34565 (33.7 Kb)  TX bytes:90327 (88.2 Kb)
>
> 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:9737 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:10902 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:2106711 (2.0 Mb)  TX bytes:879387 (858.7 Kb)
>
> vif1.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:3902 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:5917 errors:0 dropped:27 overruns:0 carrier:0
>           collisions:0 txqueuelen:32
>           RX bytes:689352 (673.1 Kb)  TX bytes:461052 (450.2 Kb)
>
> vif2.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:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:837 errors:0 dropped:380 overruns:0 carrier:0
>           collisions:0 txqueuelen:32
>           RX bytes:0 (0.0 b)  TX bytes:96397 (94.1 Kb)
>
> vif3.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:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:824 errors:0 dropped:381 overruns:0 carrier:0
>           collisions:0 txqueuelen:32
>           RX bytes:0 (0.0 b)  TX bytes:95169 (92.9 Kb)
>
> vif4.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:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:806 errors:0 dropped:387 overruns:0 carrier:0
>           collisions:0 txqueuelen:32
>           RX bytes:0 (0.0 b)  TX bytes:93511 (91.3 Kb)
>
> vif5.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:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:1173 overruns:0 carrier:0
>           collisions:0 txqueuelen:32
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>
> xenbr0    Link encap:Ethernet  HWaddr 00:FF:76:5F:AF:F6
>           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
>           RX packets:717 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:58363 (56.9 Kb)  TX bytes:0 (0.0 b)
>
> As you can see, the vif0.0 and vif1.0 do work, the others don't.
>
> only possible "errors" I see in my /var/log/messages are:
>
> Oct 30 09:43:37 kernel: [   66.621808] device vif4.0 entered promiscuous mode
> Oct 30 09:43:37 kernel: [   66.627246] xenbr0: port 6(vif4.0) entering
> learning state
> Oct 30 09:43:37 kernel: [   66.634953] xenbr0: port 6(vif4.0) entering
> forwarding state
>
> Oct 30 09:43:37 ifup:     vif4.0
> Oct 30 09:43:37 ifup:               No configuration found for vif4.0
>
> But I do not hink this is wrong, because I get the same messages for
> the working vif0.0 and vif1.0
>
> What can be wrong?
>
> Regards Marcel Smeets
>
>
>
>
>
> --
> ----------------------
> http://yahoo--swicki.eurekster.com
> http://booksonline-swicki.eurekster.com/
> http://uol--swicki.eurekster.com/
> http://live--swicki.eurekster.com/
> http://my-space-swicki--swicki.eurekster.com/
> http://chathalal-swicki.eurekster.com/
> http://webyahoo-swicki.eurekster.com/
>


-- 
----------------------
http://yahoo--swicki.eurekster.com
http://booksonline-swicki.eurekster.com/
http://uol--swicki.eurekster.com/
http://live--swicki.eurekster.com/
http://my-space-swicki--swicki.eurekster.com/
http://chathalal-swicki.eurekster.com/
http://webyahoo-swicki.eurekster.com/

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users