From owner-freebsd-xen@freebsd.org Tue Dec 29 06:27:18 2015 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 83734A5525D; Tue, 29 Dec 2015 06:27:18 +0000 (UTC) (envelope-from aoyama@peach.ne.jp) Received: from moon.peach.ne.jp (moon.peach.ne.jp [203.141.148.98]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 377A210B1; Tue, 29 Dec 2015 06:27:17 +0000 (UTC) (envelope-from aoyama@peach.ne.jp) Received: from moon.peach.ne.jp (localhost [127.0.0.1]) by moon.peach.ne.jp (Postfix) with ESMTP id AE37250F2B; Tue, 29 Dec 2015 15:27:08 +0900 (JST) Received: from artemis (unknown [172.18.0.21]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by moon.peach.ne.jp (Postfix) with ESMTPSA id 93FCA50F29; Tue, 29 Dec 2015 15:27:08 +0900 (JST) Message-ID: From: "Daisuke Aoyama" To: , =?windows-1252?Q?Roger_Pau_Monn=E9?= Cc: References: <86DF039090BD474AA2CB2795F6C7A0C7@ad.peach.ne.jp> <5681371F.6090007@FreeBSD.org> In-Reply-To: <5681371F.6090007@FreeBSD.org> Subject: Re: Xen/dom0/FreeBSD + NAS4Free WebGUI. Date: Tue, 29 Dec 2015 15:27:02 +0900 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="windows-1252"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8117.416 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416 X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Dec 2015 06:27:18 -0000 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 Name ID Mem VCPUs State Time(s) UUID Reason-Code Security Label Domain-0 0 4096 4 r----- 202.8 00000000-0000-0000-0000-000000000000 - - nas4free 4 2048 2 -b---- 51.1 00000000-0000-0000-0000-000000000000 - - >> 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