Re: Xen/dom0/FreeBSD + NAS4Free WebGUI.
Hello, -- From: "Roger Pau Monne" Sent: Monday, December 28, 2015 10:20 PM To: "Daisuke Aoyama" ; Cc: Subject: Re: Xen/dom0/FreeBSD + NAS4Free WebGUI. Hello, El 26/12/15 a les 15.26, Daisuke Aoyama ha escrit: Hi all, I'm creating NAS4Free dom0 edition. This is simple wrapper of Xen/dom0/FreeBSD. You can upgrade by same way of NAS4Free. You can manage HDD, ZFS, iSCSI target, NFS share by same way of NAS4Free. You can manage DomU(VM) via WebGUI. Japanese blog: http://shell.peach.ne.jp/aoyama/archives/3149 http://shell.peach.ne.jp/aoyama/archives/3135 NAS4Free dom0 topic in English: http://forums.nas4free.org/viewtopic.php?f=17&t=10028 Latest download: http://www.peach.ne.jp/archives/nas4free/test/2244-dom0/ How to install: 1.Download LiveCD iso image. 2.Burn to CD/DVD-RW blank disc. 3.Boot from it. (if your server don't have an optical drive, please use an external USB optical drive) 4.Install to USB Flash drive (2GB or more) from menu #9. 5.Reboot the server after ejecting CD/DVD media. How to upgrade: 1.Navigate to System|Firmware in global menu from web browser. 2.Click "Enable Firmware Update". 3.Select NAS4Free-dom0-embedded-*.img.xz. (don't decompress the image) 4.Click "Upgrade Firmware". I forget to write. You should backup the config from System|Backup/Restore before upgrading. Note: At least you need a bridge interface before using. Please create it from Network|Interface Management|Bridge. You can change boot parameters from System|Advanced|loader.conf. If you are interested in the xl.cfg, it is created in /usr/local/etc/xen/vm-.cfg. Thanks for doing this, I just gave it a try and it worked out of the box, I was able to create and launch a Windows VM in less than 2min, quite impressive :). Thank you for trying. Known issues: uuid generation of ports/sysutils/xen-tools is broken. You cannot control by UUID. (quick hack patch is attached this mail) I've given a look at the patch, but I have to admit I know very little about UUID, yet it seems like you should not poke directly at the internal uuid_t fields. I've created another patch which I *think* should solve the UUID issues, could you test it please? It should apply cleanly against Xen 4.5. https://people.freebsd.org/~royger/uuid.patch Your patch does not work as expected. You can test it under normal FreeBSD. First create UUID by uuidgen(1): # uuidgen 4c90eb5a-adee-11e5-a747-001b2157b424 Insert the UUID to your VM config (see also /usr/local/etc/xen/vm-.cfg): uuid = "4c90eb5a-adee-11e5-a747-001b2157b424" Run the VM: # xl create name.cfg Check by xl list: # xl list -v # xl list -l Your patched result is here: [root@nas4free-xen ~]# xl list -v NameID Mem VCPUs State Time(s) UUID Reason-Code Security Label Domain-0 0 4096 4 r- 202.8 ------ nas4free 4 2048 2 -b 51.1 ------ xnb device performance is terrible. (it eats 100% CPU on intr while transferring via bridged 10GbE) I haven't seen this, but I'm not surprised (I also don't have a 10GbE card at hand right now). There's a lot of fine tuning and bug fixing to do regarding the backends. I plan to get with this once the PVH implementation is stable. I feel UUID is very small thing than performance 70% drop down via xnb. Regards, -- Daisuke Aoyama ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: clang/3.7.1/include/ does not exist?
> On Dec 28, 2015, at 18:39, Roger Marquis wrote: > > Anyone else seeing these buildworld errors? ... > /usr/obj/usr/src/tmp/usr/lib/clang/3.7.1/include/ > install: target directory > `/usr/obj/usr/src/tmp/usr/lib/clang/3.7.1/include/' does not exist > usage: install [-bCcpSsUv] [-f flags] [-g group] [-m mode] [-o owner] > [-M log] [-D dest] [-h hash] [-T tags] > [-B suffix] [-l linkflags] [-N dbdir] > file1 file2 > install [-bCcpSsUv] [-f flags] [-g group] [-m mode] [-o owner] > [-M log] [-D dest] [-h hash] [-T tags] > [-B suffix] [-l linkflags] [-N dbdir] > file1 ... fileN directory > install -dU [-vU] [-g group] [-m mode] [-N dbdir] [-o owner] > [-M log] [-D dest] [-h hash] [-T tags] > directory ... > *** Error code 64 > Stop. > make[4]: stopped in /usr/src/lib/clang/include > *** Error code 1 Hi Roger, How are you executing buildworld? What’s your revision? Thanks! -NGie ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
second call for 2015Q4 quarterly status reports
Dear FreeBSD Community, There are less than two weeks left before the deadline for the next FreeBSD Quarterly Status update -- submissions are due on January 7, 2016, for work done in October through December. Status report submissions do not have to be very long. They may be about anything happening in the FreeBSD project and community, and provide a great way to inform FreeBSD users and developers about what you're working on. Submission of reports is not restricted to committers. Anyone doing anything interesting and FreeBSD-related can -- and should -- write one! The preferred and easiest submission method is to use the XML generator [1] with the results emailed to the status report team at monthly at freebsd.org . There is also an XML template [2] which can be filled out manually and attached if preferred. For the expected content and style, please study our guidelines on how to write a good status report [3]. You can also review previous issues [4][5] for ideas on the style and format. We are looking forward to all of your 2015Q4 reports! Thanks, Ben (on behalf of monthly@) [1] http://www.freebsd.org/cgi/monthly.cgi [2] http://www.freebsd.org/news/status/report-sample.xml [3] http://www.freebsd.org/news/status/howto.html [4] http://www.freebsd.org/news/status/report-2015-04-2015-06.html [5] http://www.freebsd.org/news/status/report-2015-07-2015-09.html ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
clang/3.7.1/include/ does not exist?
Anyone else seeing these buildworld errors? ===> lib/clang/include (install) sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/__stddef_max_align_t.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/__wmmintrin_aes.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/__wmmintrin_pclmul.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/adxintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/altivec.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/ammintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/arm_acle.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/avx2intrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/avx512bwintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/avx512cdintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/avx512dqintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/avx512erintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/avx512fintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/avx512vlbwintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/avx512vldqintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/avx512vlintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/avxintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/bmi2intrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/bmiintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/cpuid.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/cuda_builtin_vars.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/emmintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/f16cintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/fma4intrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/fmaintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/fxsrintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/htmintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/htmxlintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/ia32intrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/immintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/lzcntintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/mm3dnow.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/mm_malloc.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/mmintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/module.modulemap /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/nmmintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/pmmintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/popcntintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/prfchwintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/rdseedintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/rtmintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/s390intrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/shaintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/smmintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/tbmintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/tmmintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/vadefs.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/vecintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/wmmintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/x86intrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/xmmintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/xopintrin.h /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/xtestintrin.h arm_neon.h /usr/obj/usr/src/tmp/usr/lib/clang/3.7.1/include/ install: target directory `/usr/obj/usr
Re: Aw: Re: make .SUFFIXES bug?
Carsten Kunze wrote: > Thomas Dickey wrote: > > On Tue, Dec 15, 2015 at 04:01:41PM +0100, Carsten Kunze wrote: > > > current groff doesn't build on FreeBSD. I had noticed the same issue some > > > months ago on NetBSD and cross checked on FreeBSD and it had worked on This should be fixed in head, will MFC to stable/10 soon. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: panic while booting the official ISO 11-CUR-amd64-20151217-r292413
On 12/28/15, Matthias Apitz wrote: > El día Monday, December 28, 2015 a las 02:12:29PM +0100, Matthias Apitz > escribió: > >> >> Hello, >> >> I downloaded the ISO for the above version and when I boot it in a >> VMWare it panics reproduceable after trying to mount the root; see the >> message captured in the last screens: >> >> http://www.unixarea.de/panic-01.jpg >> http://www.unixarea.de/panic-02.jpg >> >> Any comments or hints? > > The downloaded VMWare image .vmdk of the same revision r292413 boots > fine; Yes, because the isofs triggers the problem, and the vmdk image don't contains isofs. > > matthias > -- > Matthias Apitz, ✉ g...@unixarea.de, 🌐 http://www.unixarea.de/ ☎ > +49-176-38902045 > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: panic while booting the official ISO 11-CUR-amd64-20151217-r292413
El día Monday, December 28, 2015 a las 02:12:29PM +0100, Matthias Apitz escribió: > > Hello, > > I downloaded the ISO for the above version and when I boot it in a > VMWare it panics reproduceable after trying to mount the root; see the > message captured in the last screens: > > http://www.unixarea.de/panic-01.jpg > http://www.unixarea.de/panic-02.jpg > > Any comments or hints? The downloaded VMWare image .vmdk of the same revision r292413 boots fine; matthias -- Matthias Apitz, ✉ g...@unixarea.de, 🌐 http://www.unixarea.de/ ☎ +49-176-38902045 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Xen/dom0/FreeBSD + NAS4Free WebGUI.
Hello, El 26/12/15 a les 15.26, Daisuke Aoyama ha escrit: > Hi all, > > I'm creating NAS4Free dom0 edition. > This is simple wrapper of Xen/dom0/FreeBSD. > > You can upgrade by same way of NAS4Free. > You can manage HDD, ZFS, iSCSI target, NFS share by same way of NAS4Free. > You can manage DomU(VM) via WebGUI. > > Japanese blog: > http://shell.peach.ne.jp/aoyama/archives/3149 > http://shell.peach.ne.jp/aoyama/archives/3135 > > NAS4Free dom0 topic in English: > http://forums.nas4free.org/viewtopic.php?f=17&t=10028 > > Latest download: > http://www.peach.ne.jp/archives/nas4free/test/2244-dom0/ > > How to install: > 1.Download LiveCD iso image. > 2.Burn to CD/DVD-RW blank disc. > 3.Boot from it. > (if your server don't have an optical drive, please use an external USB > optical drive) > 4.Install to USB Flash drive (2GB or more) from menu #9. > 5.Reboot the server after ejecting CD/DVD media. > > How to upgrade: > 1.Navigate to System|Firmware in global menu from web browser. > 2.Click "Enable Firmware Update". > 3.Select NAS4Free-dom0-embedded-*.img.xz. (don't decompress the image) > 4.Click "Upgrade Firmware". > > Note: > At least you need a bridge interface before using. > Please create it from Network|Interface Management|Bridge. > You can change boot parameters from System|Advanced|loader.conf. > If you are interested in the xl.cfg, it is created in > /usr/local/etc/xen/vm-.cfg. Thanks for doing this, I just gave it a try and it worked out of the box, I was able to create and launch a Windows VM in less than 2min, quite impressive :). > Known issues: > uuid generation of ports/sysutils/xen-tools is broken. You cannot > control by UUID. > (quick hack patch is attached this mail) I've given a look at the patch, but I have to admit I know very little about UUID, yet it seems like you should not poke directly at the internal uuid_t fields. I've created another patch which I *think* should solve the UUID issues, could you test it please? It should apply cleanly against Xen 4.5. https://people.freebsd.org/~royger/uuid.patch > xnb device performance is terrible. > (it eats 100% CPU on intr while transferring via bridged 10GbE) I haven't seen this, but I'm not surprised (I also don't have a 10GbE card at hand right now). There's a lot of fine tuning and bug fixing to do regarding the backends. I plan to get with this once the PVH implementation is stable. Roger. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: panic while booting the official ISO 11-CUR-amd64-20151217-r292413
On Monday, December 28, 2015, Matthias Apitz wrote: > > Hello, > > I downloaded the ISO for the above version and when I boot it in a > VMWare it panics reproduceable after trying to mount the root; see the > message captured in the last screens: > > http://www.unixarea.de/panic-01.jpg > http://www.unixarea.de/panic-02.jpg > > Any comments or hints? Fixed in https://github.com/freebsd/freebsd/commit/6cbc48de82fcf894c69c41588fd14c5c4f410244 commit. > > matthias > -- > Matthias Apitz, ✉ g...@unixarea.de , 🌐 > http://www.unixarea.de/ ☎ +49-176-38902045 > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org > " ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: TCP Stack: Challenge ACKs and Timestamps
On Monday, December 28, 2015, Sam Kumar wrote: > Hello, > I am working with the code for the TCP Stack. I noticed that support for > Challenge Acks have been added since the latest release (10.2.0), and I > think I may have found a bug in how they relate to TCP timestamps. All line > numbers below are those in commit e66e064c45687b5d294565dbd829b419848f7992. > > Looking at tcp_input.c, at lines 1594 to 1604, I see code that expects a > timestamp to be in every segment during the session, if they were > negotiated when the connection was being established. > ( > > https://github.com/freebsd/freebsd/blob/master/sys/netinet/tcp_input.c#L1595 > ) > > Looking at tcp_input.c, at lines 2161 and 2188, I see that Challenge ACKs > are sent via calls to tcp_respond(). > ( > > https://github.com/freebsd/freebsd/blob/master/sys/netinet/tcp_input.c#L2161 > and > > https://github.com/freebsd/freebsd/blob/master/sys/netinet/tcp_input.c#L2188 > ) > > Looking at tcp_subr.c, at line 978, I see that the segment sent by > tcp_respond() never contains TCP options. > ( > https://github.com/freebsd/freebsd/blob/master/sys/netinet/tcp_subr.c#L978 > ) > > Therefore, it seems to me that Challenge ACKs will never contain any TCP > options. This violates the condition that once timestamps are negotiated, > they must be present in every segment. > > Please let me know if I am mistaken, or if this is actually a bug. Cc hiren and gnn > > Sam Kumar > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org > " > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
panic while booting the official ISO 11-CUR-amd64-20151217-r292413
Hello, I downloaded the ISO for the above version and when I boot it in a VMWare it panics reproduceable after trying to mount the root; see the message captured in the last screens: http://www.unixarea.de/panic-01.jpg http://www.unixarea.de/panic-02.jpg Any comments or hints? matthias -- Matthias Apitz, ✉ g...@unixarea.de, 🌐 http://www.unixarea.de/ ☎ +49-176-38902045 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
TCP Stack: Challenge ACKs and Timestamps
Hello, I am working with the code for the TCP Stack. I noticed that support for Challenge Acks have been added since the latest release (10.2.0), and I think I may have found a bug in how they relate to TCP timestamps. All line numbers below are those in commit e66e064c45687b5d294565dbd829b419848f7992. Looking at tcp_input.c, at lines 1594 to 1604, I see code that expects a timestamp to be in every segment during the session, if they were negotiated when the connection was being established. ( https://github.com/freebsd/freebsd/blob/master/sys/netinet/tcp_input.c#L1595 ) Looking at tcp_input.c, at lines 2161 and 2188, I see that Challenge ACKs are sent via calls to tcp_respond(). ( https://github.com/freebsd/freebsd/blob/master/sys/netinet/tcp_input.c#L2161 and https://github.com/freebsd/freebsd/blob/master/sys/netinet/tcp_input.c#L2188 ) Looking at tcp_subr.c, at line 978, I see that the segment sent by tcp_respond() never contains TCP options. (https://github.com/freebsd/freebsd/blob/master/sys/netinet/tcp_subr.c#L978) Therefore, it seems to me that Challenge ACKs will never contain any TCP options. This violates the condition that once timestamps are negotiated, they must be present in every segment. Please let me know if I am mistaken, or if this is actually a bug. Sam Kumar ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
