From owner-freebsd-current@freebsd.org Tue Jan 12 13:23:44 2016 Return-Path: Delivered-To: freebsd-current@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 2BE92A6C9EF; Tue, 12 Jan 2016 13:23:44 +0000 (UTC) (envelope-from royger@gmail.com) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BD40915CB; Tue, 12 Jan 2016 13:23:43 +0000 (UTC) (envelope-from royger@gmail.com) Received: by mail-wm0-x236.google.com with SMTP id f206so253768630wmf.0; Tue, 12 Jan 2016 05:23:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=ZvAkXy8AXP2HQYwLa3gsfLBqfEG2xareYs2l5fj8aos=; b=vJHwKzyNfZmaHD4h0DYJAKTOBG6X5Un7u9hePIQrO9pWIzRl2sNCi7JpqU6UWLLqb9 jiK0ewPjz7tPHZWSk3jE9EiTas/tYYhOGJ+pBabee7V1sfJqKgklD2s1euzYu/ZayQs+ p1DbDduHbi83CnFKXfS/XBxqRG4VWxXLKj0r2zrQkWAnPeZAPANif2JWqb9bkDdAreQt E4eYHr3pnQgSHFysPMOSxPF4k62MQYolaOoWxQ8i61agZdXdT9CXyjJz/PGLndKCqlWO rbgM5T3B7hO/vVHMioS1waK3LN1aMcxBPhOmAiMnzRobgb3a63Usdu7VaZt4YJ7vDbdu iYBQ== X-Received: by 10.28.17.8 with SMTP id 8mr18239078wmr.65.1452605022262; Tue, 12 Jan 2016 05:23:42 -0800 (PST) Received: from [172.16.1.30] (178.Red-79-152-19.dynamicIP.rima-tde.net. [79.152.19.178]) by smtp.gmail.com with ESMTPSA id f205sm17582264wme.4.2016.01.12.05.23.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Jan 2016 05:23:41 -0800 (PST) Sender: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= Subject: Re: Xen/dom0/FreeBSD + NAS4Free WebGUI. To: Daisuke Aoyama , freebsd-xen@freebsd.org References: <86DF039090BD474AA2CB2795F6C7A0C7@ad.peach.ne.jp> <5681371F.6090007@FreeBSD.org> Cc: freebsd-current@freebsd.org, Wei Liu From: =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= Message-ID: <5694FE5B.2070509@FreeBSD.org> Date: Tue, 12 Jan 2016 14:23:39 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jan 2016 13:23:44 -0000 El 29/12/15 a les 7.27, Daisuke Aoyama ha escrit: > 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. Hello, Could you please test the following patch, it should fix UUID: https://people.freebsd.org/~royger/0001-libxl-fix-UUID-usage-on-FreeBSD.patch I understand that the netback performance issue is a big handicap, I will try to find some time to look into it, but I have to admit my plate is quite full at the moment and it doesn't look like a trivial issue (like the UUID one). I'm adding Wei to the Cc, he has been working on netfront improvements, so maybe he also wants to take a stab at netback ;). Roger.