thr3ads.net - Xen users - [Xen-users] netbsd/amd64 5.1rc4 domU network on XEN4 and current dom0 [Sep 2010]

If this information is useful, please help other people find it:
Share via:

Pierre-Philipp Braun

2010-Sep-23 10:42 UTC

[Xen-users] netbsd/amd64 5.1rc4 domU network on XEN4 and current dom0

Hi,

I''m running a Slackware64 dom0 on top of XEN 4.0.1.  I tryed both
xen/next
and xen/master kernel repositories, same problem : the NetBSD guest sees
its network interface (xennet0) but it''s unusable.  It doesn''t
ping nor
responds to ping.  Another guest, RHEL5 (2.6.18) network works fine.  I
tryed both -bridge and -route configurations (I would like to keep the
latter), no changes.

Although the dom0 shows fe:ff:ff:ff:ff:ff for the virtual interfaces, and
show dom0''s IP instead of the guests'' one, the guest (both
rhel and
netbsd)
do have the right MAC addresses and IP (rhel:192.168.0.11,
netbsd:192.168.0.12).

dom0 network (ifconfig) :

eth0      Link encap:Ethernet  HWaddr 90:e6:ba:a6:51:c7
          inet addr:192.168.0.10  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::92e6:baff:fea6:51c7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5969 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5284 errors:0 dropped:0 overruns:0 carrier:1
          collisions:0 txqueuelen:1000
          RX bytes:1112951 (1.0 MiB)  TX bytes:898875 (877.8 KiB)
          Interrupt:239

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:28 errors:0 dropped:0 overruns:0 frame:0
          TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2384 (2.3 KiB)  TX bytes:2384 (2.3 KiB)

veth1     Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
          inet addr:192.168.0.10  Bcast:192.168.0.255 
Mask:255.255.255.255
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:613 errors:0 dropped:0 overruns:0 frame:0
          TX packets:704 errors:0 dropped:16 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:48061 (46.9 KiB)  TX bytes:647065 (631.8 KiB)

veth2     Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
          inet addr:192.168.0.10  Bcast:192.168.0.255 
Mask:255.255.255.255
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:1198 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


NetBSD domU details (xm li -l):

(domain
    (domid 5)
    (cpu_weight 256)
    (cpu_cap 0)
    (bootloader )
    (on_crash restart)
    (uuid 0f5c77cf-bff6-dedf-0354-de123a69f583)
    (bootloader_args )
    (vcpus 1)
    (description )
    (name bsd)
    (cpus (()))
    (on_reboot restart)
    (on_poweroff destroy)
    (maxmem 512)
    (memory 512)
    (shadow_memory 0)
    (features )
    (on_xend_start ignore)
    (on_xend_stop ignore)
    (start_time 1285236882.6)
    (cpu_time 1.950968696)
    (online_vcpus 1)
    (image
        (linux
            (kernel /data/_shared/netbsd-XEN3_DOMU.gz)
            (superpages 0)
            (videoram 4)
            (pci ())
            (nomigrate 0)
            (tsc_mode 0)
            (notes)
        )
    )
    (status 2)
    (state -b----)
    (store_mfn 721859)
    (console_mfn 721858)
    (device
        (vif
            (uuid b13a1a04-aa56-a141-c781-5682be2521d2)
            (script /etc/xen/scripts/vif-route)
            (ip 192.168.0.12)
            (mac 00:16:3e:7b:bb:a4)
            (vifname veth2)
            (backend 0)
        )
    )
    (device
        (console
            (protocol vt100)
            (location 2)
            (uuid 4434c7a5-1170-f780-b959-a337866c4d52)
        )
    )
    (device
        (vbd
            (protocol x86_64-abi)
            (uuid 9ed2debb-3fcf-906d-4a77-289215c87a1a)
            (bootable 1)
            (dev xvda:disk)
            (uname file:/data/bsd/bsd.disk)
            (mode w)
            (backend 0)
            (VDI )
        )
    )
)


Help would be greatly appreciated :-)

Thanks
//Pierre-Philipp

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

Christopher R. K.

2010-Sep-23 11:15 UTC

head link

Re: [Xen-users] netbsd/amd64 5.1rc4 domU network on XEN4 and current dom0

The "new" netBSD kernels don''t work with Xen4 and some Xen3
versions. (network unavailable, bad disk performance)

Try using a older XEN kernel of netBSD (not the recent ones), then
it''ll work. I haven''t managed to boot a new kernel, you may
need to try to compile one yourself. It does run with Xen4 and 3 alike if you
use a old kernel. That''s at least my experience. (32 bit and 64 bit
alike)

-------- Original-Nachricht --------> Datum: Thu, 23 Sep 2010 12:42:39 +0200
> Von: Pierre-Philipp Braun <pbraun@nethence.com>
> An: xen-users@lists.xensource.com
> CC: port-xen@netbsd.org
> Betreff: [Xen-users] netbsd/amd64 5.1rc4 domU network on XEN4 and current
dom0
> 
> Hi,
> 
> I''m running a Slackware64 dom0 on top of XEN 4.0.1.  I tryed both
xen/next
> and xen/master kernel repositories, same problem : the NetBSD guest sees
> its network interface (xennet0) but it''s unusable.  It
doesn''t ping nor
> responds to ping.  Another guest, RHEL5 (2.6.18) network works fine.  I
> tryed both -bridge and -route configurations (I would like to keep the
> latter), no changes.
> 
> Although the dom0 shows fe:ff:ff:ff:ff:ff for the virtual interfaces, and
> show dom0''s IP instead of the guests'' one, the guest
(both rhel and
> netbsd)
> do have the right MAC addresses and IP (rhel:192.168.0.11,
> netbsd:192.168.0.12).
> 
> dom0 network (ifconfig) :
> 
> eth0      Link encap:Ethernet  HWaddr 90:e6:ba:a6:51:c7
>           inet addr:192.168.0.10  Bcast:192.168.0.255  Mask:255.255.255.0
>           inet6 addr: fe80::92e6:baff:fea6:51c7/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:5969 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:5284 errors:0 dropped:0 overruns:0 carrier:1
>           collisions:0 txqueuelen:1000
>           RX bytes:1112951 (1.0 MiB)  TX bytes:898875 (877.8 KiB)
>           Interrupt:239
> 
> 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:28 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:2384 (2.3 KiB)  TX bytes:2384 (2.3 KiB)
> 
> veth1     Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
>           inet addr:192.168.0.10  Bcast:192.168.0.255 
> Mask:255.255.255.255
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:613 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:704 errors:0 dropped:16 overruns:0 carrier:0
>           collisions:0 txqueuelen:32
>           RX bytes:48061 (46.9 KiB)  TX bytes:647065 (631.8 KiB)
> 
> veth2     Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
>           inet addr:192.168.0.10  Bcast:192.168.0.255 
> Mask:255.255.255.255
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:1198 overruns:0 carrier:0
>           collisions:0 txqueuelen:32
>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
> 
> 
> NetBSD domU details (xm li -l):
> 
> (domain
>     (domid 5)
>     (cpu_weight 256)
>     (cpu_cap 0)
>     (bootloader )
>     (on_crash restart)
>     (uuid 0f5c77cf-bff6-dedf-0354-de123a69f583)
>     (bootloader_args )
>     (vcpus 1)
>     (description )
>     (name bsd)
>     (cpus (()))
>     (on_reboot restart)
>     (on_poweroff destroy)
>     (maxmem 512)
>     (memory 512)
>     (shadow_memory 0)
>     (features )
>     (on_xend_start ignore)
>     (on_xend_stop ignore)
>     (start_time 1285236882.6)
>     (cpu_time 1.950968696)
>     (online_vcpus 1)
>     (image
>         (linux
>             (kernel /data/_shared/netbsd-XEN3_DOMU.gz)
>             (superpages 0)
>             (videoram 4)
>             (pci ())
>             (nomigrate 0)
>             (tsc_mode 0)
>             (notes)
>         )
>     )
>     (status 2)
>     (state -b----)
>     (store_mfn 721859)
>     (console_mfn 721858)
>     (device
>         (vif
>             (uuid b13a1a04-aa56-a141-c781-5682be2521d2)
>             (script /etc/xen/scripts/vif-route)
>             (ip 192.168.0.12)
>             (mac 00:16:3e:7b:bb:a4)
>             (vifname veth2)
>             (backend 0)
>         )
>     )
>     (device
>         (console
>             (protocol vt100)
>             (location 2)
>             (uuid 4434c7a5-1170-f780-b959-a337866c4d52)
>         )
>     )
>     (device
>         (vbd
>             (protocol x86_64-abi)
>             (uuid 9ed2debb-3fcf-906d-4a77-289215c87a1a)
>             (bootable 1)
>             (dev xvda:disk)
>             (uname file:/data/bsd/bsd.disk)
>             (mode w)
>             (backend 0)
>             (VDI )
>         )
>     )
> )
> 
> 
> Help would be greatly appreciated :-)
> 
> Thanks
> //Pierre-Philipp
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
-- 
Mit freundlichen Grüßen,

SpiegelEiXXL

GRATIS: Spider-Man 1-3 sowie 300 weitere Videos!
Jetzt freischalten! http://portal.gmx.net/de/go/maxdome

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

Pierre-Philipp Braun

2010-Sep-23 19:05 UTC

head link

Re: [Xen-users] netbsd/amd64 5.1rc4 domU network on XEN4 and current dom0

Hi Christopher,

On Thu, 23 Sep 2010 13:15:11 +0200, "Christopher R. K."
<Feuerball_@gmx.net> wrote:> The "new" netBSD kernels don''t work with Xen4 and some
Xen3 versions.
> (network unavailable, bad disk performance)
> 
> Try using a older XEN kernel of netBSD (not the recent ones), then
it''ll
> work. I haven''t managed to boot a new kernel, you may need to try
to
> compile one yourself. It does run with Xen4 and 3 alike if you use a old
> kernel. That''s at least my experience. (32 bit and 64 bit alike)
Ok I compiled netbsd/amd64 current@20071231-UTC (gives NetBSD-4.99.46) but
it resumes the same issue: everything looks fine but the network.  I can
see xennet0, attribute an IP to it, but nothing pings.  Maybe it''s the
copy vs flip support issue discussed elsewhere in this thread.

But thanks anyway :-)

//Pierre-Philipp


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

Xen users - Sep 2010 - netbsd/amd64 5.1rc4 domU network on XEN4 and current dom0

[Xen-users] netbsd/amd64 5.1rc4 domU network on XEN4 and current dom0

Re: [Xen-users] netbsd/amd64 5.1rc4 domU network on XEN4 and current dom0

Re: [Xen-users] netbsd/amd64 5.1rc4 domU network on XEN4 and current dom0