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
On Thu, 23 Sep 2010, Pierre-Philipp Braun wrote:> 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.Stab in the dark: lack of copy support in the network frontend? NetBSD currently only has flip support and when attempting to get NetBSD running as PV guest in XenServer, Citrix said that flip support is deprecated. Symptoms on XenServer were that not only did the guest not have network access, it also stopped all other domUs (and meant the XenServer dom0 had to be powercycled). -- Stephen _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, 23 Sep 2010 11:53:33 +0100 (BST), Stephen Borrill <netbsd@precedence.co.uk> wrote:> On Thu, 23 Sep 2010, Pierre-Philipp Braun wrote: >> 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 guestsees>> 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. > > Stab in the dark: lack of copy support in the network frontend? NetBSD > currently only has flip support and when attempting to get NetBSDrunning> as PV guest in XenServer, Citrix said that flip support is deprecated. > Symptoms on XenServer were that not only did the guest not have network > access, it also stopped all other domUs (and meant the XenServer dom0had> to be powercycled).Copy support was pulled-up by Manuel about a year ago (see PR/40650): http://releng.netbsd.org/cgi-bin/req-5.cgi?show=1030 -- Jean-Yves Migeon jeanyves.migeon@free.fr _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, 23 Sep 2010, Jean-Yves Migeon wrote:>> Stab in the dark: lack of copy support in the network frontend? NetBSD >> currently only has flip support and when attempting to get NetBSD > running >> as PV guest in XenServer, Citrix said that flip support is deprecated. >> Symptoms on XenServer were that not only did the guest not have network >> access, it also stopped all other domUs (and meant the XenServer dom0 > had >> to be powercycled). > > Copy support was pulled-up by Manuel about a year ago (see PR/40650): > > http://releng.netbsd.org/cgi-bin/req-5.cgi?show=1030That''s backend only. I''m talking about frontend, i.e. xennet in the domU -- Stephen _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thor Lancelot Simon
2010-Sep-23 12:14 UTC
[Xen-users] Re: netbsd/amd64 5.1rc4 domU network
On Thu, Sep 23, 2010 at 01:02:08PM +0100, Stephen Borrill wrote:> On Thu, 23 Sep 2010, Jean-Yves Migeon wrote: >>> Stab in the dark: lack of copy support in the network frontend? NetBSD >>> currently only has flip support and when attempting to get NetBSD >> running >>> as PV guest in XenServer, Citrix said that flip support is deprecated. >>> Symptoms on XenServer were that not only did the guest not have network >>> access, it also stopped all other domUs (and meant the XenServer dom0 >> had >>> to be powercycled). >> >> Copy support was pulled-up by Manuel about a year ago (see PR/40650): >> >> http://releng.netbsd.org/cgi-bin/req-5.cgi?show=1030 > > That''s backend only. I''m talking about frontend, i.e. xennet in the domUI''d love to understand how their response to a bug that hangs the hypervisor itself is that unprivileged domains should not be doing such operations. Sigh. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, 23 Sep 2010 13:02:08 +0100 (BST), Stephen Borrill <netbsd@precedence.co.uk> wrote:> On Thu, 23 Sep 2010, Jean-Yves Migeon wrote: >>> Stab in the dark: lack of copy support in the network frontend? NetBSD >>> currently only has flip support and when attempting to get NetBSD >> running >>> as PV guest in XenServer, Citrix said that flip support is deprecated. >>> Symptoms on XenServer were that not only did the guest not havenetwork>>> access, it also stopped all other domUs (and meant the XenServer dom0 >> had >>> to be powercycled). >> >> Copy support was pulled-up by Manuel about a year ago (see PR/40650): >> >> http://releng.netbsd.org/cgi-bin/req-5.cgi?show=1030 > > That''s backend only. I''m talking about frontend, i.e. xennet in the domUOopsie, sorry; should have read your mail slower -- Jean-Yves Migeon jeanyves.migeon@free.fr _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Pierre-Philipp Braun
2010-Sep-23 19:29 UTC
[Xen-users] Re: netbsd/amd64 5.1rc4 domU network
On Thu, 23 Sep 2010 14:29:11 +0200, Jean-Yves Migeon <jeanyves.migeon@free.fr> wrote:> On Thu, 23 Sep 2010 13:02:08 +0100 (BST), Stephen Borrill > <netbsd@precedence.co.uk> wrote: >> On Thu, 23 Sep 2010, Jean-Yves Migeon wrote: >>>> Stab in the dark: lack of copy support in the network frontend?NetBSD>>>> currently only has flip support and when attempting to get NetBSD >>> running >>>> as PV guest in XenServer, Citrix said that flip support isdeprecated.>>>> Symptoms on XenServer were that not only did the guest not have > network >>>> access, it also stopped all other domUs (and meant the XenServer dom0 >>> had >>>> to be powercycled). >>> >>> Copy support was pulled-up by Manuel about a year ago (see PR/40650): >>> >>> http://releng.netbsd.org/cgi-bin/req-5.cgi?show=1030 >> >> That''s backend only. I''m talking about frontend, i.e. xennet in thedomU> > Oopsie, sorry; should have read your mail slowerThanks for your inputs to you all. Is that the issue (copy support missing in the frontend) ? Besides, since which versions of XEN and/or linux dom0 is flip deprecated ? (I tryed netbsd domU on RHEL5 some day but I don''t remember the result) Thanks //Pierre-Philipp _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 23.09.2010 21:29, Pierre-Philipp Braun wrote:> > On Thu, 23 Sep 2010 14:29:11 +0200, Jean-Yves Migeon > <jeanyves.migeon@free.fr> wrote: >> Oopsie, sorry; should have read your mail slower > > Thanks for your inputs to you all. Is that the issue (copy support > missing in the frontend) ?Yes, Stephen is correct> Besides, since which versions of XEN and/or linux dom0 is flip deprecated > ? (I tryed netbsd domU on RHEL5 some day but I don''t remember the result)Well, it is hard to follow -- especially when you consider the different Linux versions that exist/ed for Xen. IIRC, copy was introduced with Xen 3.0, and became the default option for 3.1 with the Linux of XenSource (2.6.18). For the pv_ops Linux (default dom0 with Xen 4 and up), I guess that flipping was never supported, hence copy is the only possibility with the pv_ops kernel. This requires confirmation by someone that follows the Linux pv_ops kernel closer. A quick look at the git branch (jeremy''s) seems to confirm this. -- Jean-Yves Migeon jeanyves.migeon@free.fr _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, I wrote a xenfront-copy patch for NetBSD DomU. http://blog.yellowback.net/uploads/netbsd-5.99.27-xenfront-rx-copy.patch Networking works in my environment: Xen: xen-4.0.2-rc1-pre (64bit) Dom0: Linux 2.6.32.21(pvops) (64bit) + Ubuntu 9.04 DomU: NetBSD 5.99.39 (64bit) http://blog.yellowback.net/archives/454-20100710.html (in Japanese) On Fri, Sep 24, 2010 at 5:38 AM, Jean-Yves Migeon <jeanyves.migeon@free.fr> wrote:> On 23.09.2010 21:29, Pierre-Philipp Braun wrote: >> >> On Thu, 23 Sep 2010 14:29:11 +0200, Jean-Yves Migeon >> <jeanyves.migeon@free.fr> wrote: >>> Oopsie, sorry; should have read your mail slower >> >> Thanks for your inputs to you all. Is that the issue (copy support >> missing in the frontend) ? > > Yes, Stephen is correct > >> Besides, since which versions of XEN and/or linux dom0 is flip deprecated >> ? (I tryed netbsd domU on RHEL5 some day but I don''t remember the result) > > Well, it is hard to follow -- especially when you consider the different > Linux versions that exist/ed for Xen. > > IIRC, copy was introduced with Xen 3.0, and became the default option > for 3.1 with the Linux of XenSource (2.6.18). > > For the pv_ops Linux (default dom0 with Xen 4 and up), I guess that > flipping was never supported, hence copy is the only possibility with > the pv_ops kernel. > > This requires confirmation by someone that follows the Linux pv_ops > kernel closer. A quick look at the git branch (jeremy''s) seems to > confirm this. > > -- > Jean-Yves Migeon > jeanyves.migeon@free.fr > >-- Hideki ONO _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Pierre-Philipp Braun
2010-Sep-24 15:43 UTC
[Xen-users] Re: netbsd/amd64 5.1rc4 domU network
On Fri, 24 Sep 2010 10:54:06 +0900, Hideki ONO <ono@ono.org> wrote:> I wrote a xenfront-copy patch for NetBSD DomU. > > http://blog.yellowback.net/uploads/netbsd-5.99.27-xenfront-rx-copy.patchI applied your patch to current (NetBSD-5.99.39) and it works. Thanks a lot ! (someones review and pull it up please) //Pierre-Philipp _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 24.09.2010 03:54, Hideki ONO wrote:> Hi, > > I wrote a xenfront-copy patch for NetBSD DomU. > > http://blog.yellowback.net/uploads/netbsd-5.99.27-xenfront-rx-copy.patch > > Networking works in my environment: > Xen: xen-4.0.2-rc1-pre (64bit) > Dom0: Linux 2.6.32.21(pvops) (64bit) + Ubuntu 9.04 > DomU: NetBSD 5.99.39 (64bit) > > http://blog.yellowback.net/archives/454-20100710.html (in Japanese)Very interesting. I will have a look at it, and see if I can commit it (and ask for a pull-up eventually). Thanks a bunch for this patch; it is really helpful. Cheers, -- Jean-Yves Migeon jeanyves.migeon@free.fr _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Pierre-Philipp Braun
2010-Sep-24 15:59 UTC
[Xen-users] Re: netbsd/amd64 5.1rc4 domU network
On Fri, 24 Sep 2010 17:43:22 +0200, Pierre-Philipp Braun <pbraun@wda-fr.org> wrote:> On Fri, 24 Sep 2010 10:54:06 +0900, Hideki ONO <ono@ono.org> wrote: >> I wrote a xenfront-copy patch for NetBSD DomU. >> >>http://blog.yellowback.net/uploads/netbsd-5.99.27-xenfront-rx-copy.patch> > I applied your patch to current (NetBSD-5.99.39) and it works.addon: it worked once. when I try to boot the installer (netbsd-INSTALL_XEN3_DOMU.gz) again, it stucks there, even after a dom0 reboot. I really don''t get why your patch successfully worked only once ! # xm cr bsd -c Using config file "./bsd". Started domain bsd (id=15) Loaded initial symtab at 0xffffffff80b541c4, strtab at 0xffffffff80ba5390, # entries 13746 Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD 5.99.39 (INSTALL_XEN3_DOMU) #0: Fri Sep 24 17:24:34 CEST 2010 root@amd1:/data/tproot/compile/obj/sys/arch/amd64/compile/INSTALL_XEN3_DOMU total memory = 512 MB avail memory = 481 MB mainbus0 (root) hypervisor0 at mainbus0: Xen version 4.0 vcpu0 at hypervisor0: AMD 686-class, 3113MHz, id 0x100f42 xenbus0 at hypervisor0: Xen Virtual Bus Interface xencons0 at hypervisor0: Xen Virtual Console Driver xencons0: using event channel 2 xbd0 at xenbus0 id 51712: Xen Virtual Block Device Interface xennet0 at xenbus0 id 0: Xen Virtual Network Interface xennet0: MAC address 00:16:3e:3c:fe:81 thanks //Pierre-Philipp _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Pierre-Philipp Braun
2010-Sep-24 16:52 UTC
[Xen-users] Re: netbsd/amd64 5.1rc4 domU network
On Fri, 24 Sep 2010 17:59:37 +0200, Pierre-Philipp Braun <pbraun@nethence.com> wrote:> On Fri, 24 Sep 2010 17:43:22 +0200, Pierre-Philipp Braun > <pbraun@wda-fr.org> wrote: >> On Fri, 24 Sep 2010 10:54:06 +0900, Hideki ONO <ono@ono.org> wrote: >>> I wrote a xenfront-copy patch for NetBSD DomU. >>> >>> > http://blog.yellowback.net/uploads/netbsd-5.99.27-xenfront-rx-copy.patch >> >> I applied your patch to current (NetBSD-5.99.39) and it works. > > addon: it worked once. when I try to boot the installer > (netbsd-INSTALL_XEN3_DOMU.gz) again, it stucks there, even after a dom0 > reboot. I really don''t get why your patch successfully worked only once!> > # xm cr bsd -c > Using config file "./bsd". > Started domain bsd (id=15) > Loaded initial symtab at 0xffffffff80b541c4, strtab at0xffffffff80ba5390,> # entries 13746 > Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004,2005,> 2006, 2007, 2008, 2009, 2010 > The NetBSD Foundation, Inc. All rights reserved. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > > NetBSD 5.99.39 (INSTALL_XEN3_DOMU) #0: Fri Sep 24 17:24:34 CEST 2010 > >root@amd1:/data/tproot/compile/obj/sys/arch/amd64/compile/INSTALL_XEN3_DOMU> total memory = 512 MB > avail memory = 481 MB > mainbus0 (root) > hypervisor0 at mainbus0: Xen version 4.0 > vcpu0 at hypervisor0: AMD 686-class, 3113MHz, id 0x100f42 > xenbus0 at hypervisor0: Xen Virtual Bus Interface > xencons0 at hypervisor0: Xen Virtual Console Driver > xencons0: using event channel 2 > xbd0 at xenbus0 id 51712: Xen Virtual Block Device Interface > xennet0 at xenbus0 id 0: Xen Virtual Network Interface > xennet0: MAC address 00:16:3e:3c:fe:81my mistake I was trying tap:aio instead of file: so it stucked AFTER xennet0 :-) Hideki''s patch really helps no doubt there. Thanks //Pierre-Philipp _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>On Fri, 24 Sep 2010 17:59:37 +0200, Pierre-Philipp Braun><pbraun%nethence.com@localhost> wrote: >> On Fri, 24 Sep 2010 17:43:22 +0200, Pierre-Philipp Braun >> <pbraun%wda-fr.org@localhost> wrote: >>> On Fri, 24 Sep 2010 10:54:06 +0900, Hideki ONO <ono%ono.org@localhost> wrote: >>>> I wrote a xenfront-copy patch for NetBSD DomU. >>>> >>>> >> http://blog.yellowback.net/uploads/netbsd-5.99.27-xenfront-rx-copy.patch >>> >>> I applied your patch to current (NetBSD-5.99.39) and it works. >> >> addon: it worked once. when I try to boot the installer >> (netbsd-INSTALL_XEN3_DOMU.gz) again, it stucks there, even after a dom0 >> reboot. I really don''t get why your patch successfully worked only once ! >> >> # xm cr bsd -c >> Using config file "./bsd". >> Started domain bsd (id=15) >> Loaded initial symtab at 0xffffffff80b541c4, strtab at0xffffffff80ba5390, >> # entries 13746 >> Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, >> 2006, 2007, 2008, 2009, 2010 >> The NetBSD Foundation, Inc. All rights reserved. >> Copyright (c) 1982, 1986, 1989, 1991, 1993 >> The Regents of the University of California. All rights reserved. >> >> NetBSD 5.99.39 (INSTALL_XEN3_DOMU) #0: Fri Sep 24 17:24:34 CEST 2010 >> >> >root@amd1:/data/tproot/compile/obj/sys/arch/amd64/compile/INSTALL_XEN3_DOMU >> total memory = 512 MB >> avail memory = 481 MB >> mainbus0 (root) >> hypervisor0 at mainbus0: Xen version 4.0 >> vcpu0 at hypervisor0: AMD 686-class, 3113MHz, id 0x100f42 >> xenbus0 at hypervisor0: Xen Virtual Bus Interface >> xencons0 at hypervisor0: Xen Virtual Console Driver >> xencons0: using event channel 2 >> xbd0 at xenbus0 id 51712: Xen Virtual Block Device Interface >> xennet0 at xenbus0 id 0: Xen Virtual Network Interface >> xennet0: MAC address 00:16:3e:3c:fe:81 > >my mistake I was trying tap:aio instead of file: so it stucked AFTER >xennet0 :-) Hideki''s patch really helps no doubt there. > >Thanks>//Pierre-PhilippThanks for the patch Hideki! I made a INSTALL and regular DOMU kernel for everyone who wants to test or use it without having to compile the kernel on his own. http://spiegeleixxl.de/builds/netbsd-280910/i386/binary/kernel/netbsd-INSTALL_XEN3PAE_DOMU.gz http://spiegeleixxl.de/builds/netbsd-280910/i386/binary/kernel/netbsd-XEN3PAE_DOMU.gz (there is also a ISO for netbsd-current http://spiegeleixxl.de/builds/netbsd-280910/iso/i386cd.iso if you want to install using the -current tree) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, 24 Sep 2010, Hideki ONO wrote:> > I wrote a xenfront-copy patch for NetBSD DomU. > > http://blog.yellowback.net/uploads/netbsd-5.99.27-xenfront-rx-copy.patch > > Networking works in my environment: > Xen: xen-4.0.2-rc1-pre (64bit) > Dom0: Linux 2.6.32.21(pvops) (64bit) + Ubuntu 9.04 > DomU: NetBSD 5.99.39 (64bit)I''m pleased to confirm that this works with XenServer 5.6. I''ve not yet got my backport to netbsd-5 to work (I just applied the -current patch and fixed up one section that didn''t apply - I''ve not looked at the patch in detail yet); it booted without messing up the dom0, but then panicked. My ftp speeds (i.e. testing both network and storage speeds) have gone up from around 50kB/s to 51MB/s. :-) Jean-Yves, can you cast your eye over the patch and commit it to -current? Are you aware of any changes in that area which might affect a backport to netbsd-5? -- Stephen _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, 1 Oct 2010 14:39:28 +0100 (BST), Stephen Borrill <netbsd@precedence.co.uk> wrote:> On Fri, 24 Sep 2010, Hideki ONO wrote: >> >> I wrote a xenfront-copy patch for NetBSD DomU. >> >>http://blog.yellowback.net/uploads/netbsd-5.99.27-xenfront-rx-copy.patch>> >> Networking works in my environment: >> Xen: xen-4.0.2-rc1-pre (64bit) >> Dom0: Linux 2.6.32.21(pvops) (64bit) + Ubuntu 9.04 >> DomU: NetBSD 5.99.39 (64bit) > > I''m pleased to confirm that this works with XenServer 5.6. I''ve not yet > got my backport to netbsd-5 to work (I just applied the -current patchand> fixed up one section that didn''t apply - I''ve not looked at the patch in> detail yet); it booted without messing up the dom0, but then panicked. > > My ftp speeds (i.e. testing both network and storage speeds) have goneup> from around 50kB/s to 51MB/s. :-) > > Jean-Yves, can you cast your eye over the patch and commit it to-current? I was planning to commit it on -current this saturday or sunday (I still ahve to check for membar_ops, it is vital there).> Are you aware of any changes in that area which might affect a backportto> netbsd-5?Not that I know of; however, it may be a bit late for 5.1, it should be discussed with releng@. -- Jean-Yves Migeon jeanyves.migeon@free.fr _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, 1 Oct 2010, Jean-Yves Migeon wrote:>> Jean-Yves, can you cast your eye over the patch and commit it to > -current? > > I was planning to commit it on -current this saturday or sunday (I still > ahve to check for membar_ops, it is vital there).Great.>> Are you aware of any changes in that area which might affect a backport >> to netbsd-5? > > Not that I know of; however, it may be a bit late for 5.1, it should be > discussed with releng@.As a member of releng@, I can assure you it is too late :-) I''ll have another look at the patch in more detail and try to do a more intelligent backport. -- Stephen _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, 24 Sep 2010, Hideki ONO wrote:> I wrote a xenfront-copy patch for NetBSD DomU. > > http://blog.yellowback.net/uploads/netbsd-5.99.27-xenfront-rx-copy.patch > > Networking works in my environment: > Xen: xen-4.0.2-rc1-pre (64bit) > Dom0: Linux 2.6.32.21(pvops) (64bit) + Ubuntu 9.04 > DomU: NetBSD 5.99.39 (64bit) > > http://blog.yellowback.net/archives/454-20100710.html (in Japanese)A tested (on amd64 and i386) patch against netbsd-5 can be found at: http://ftp.netbsd.org/pub/NetBSD/misc/sborrill/netbsd-5.1-xenfront-rx-copy.diff However, there is a small bug with these patches. If the network that the vif is attached to is changed within XenCenter, then it seems to revert to flip mode (with all the problems this causes, i.e. killing the XenServer dom0 network stack and hanging all VMs). During this operation xennet0 detaches and reattaches. -- Stephen _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users