From owner-freebsd-xen@FreeBSD.ORG Mon Aug 15 11:07:17 2011 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2514B106564A for ; Mon, 15 Aug 2011 11:07:17 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id EEB3B8FC21 for ; Mon, 15 Aug 2011 11:07:16 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p7FB7GWR014938 for ; Mon, 15 Aug 2011 11:07:16 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p7FB7Gm6014936 for freebsd-xen@FreeBSD.org; Mon, 15 Aug 2011 11:07:16 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 15 Aug 2011 11:07:16 GMT Message-Id: <201108151107.p7FB7Gm6014936@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-xen@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-xen@FreeBSD.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 15 Aug 2011 11:07:17 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/155468 xen [xen] Xen PV i386 multi-kernel CPU system is not worki o kern/155353 xen [xen] [patch] put "nudging TOD" message under boot_ver o kern/154833 xen [xen]: xen 4.0 - DomU freebsd8.2RC3 i386, XEN kernel. o kern/154473 xen [xen] xen 4.0 - DomU freebsd8.1 i386, XEN kernel. Not o kern/154472 xen [xen] xen 4.0 - DomU freebsd8.1 i386 xen kernel reboot o kern/154428 xen [xen] xn0 network interface and PF - Massive performan o kern/154302 xen [xen] [panic] [patch] xn0: Error 2 parsing device/vif/ o kern/153789 xen [xen] [regression] FreeBSD 8.2-RC1 crashes under Solar o kern/153674 xen [xen] i386/XEN idle thread shows wrong percentages o kern/153672 xen [xen] [panic] i386/XEN panics under heavy fork load o kern/153620 xen [xen] Xen guest system clock drifts in AWS EC2 (FreeBS o kern/153477 xen [xen] XEN pmap code abuses vm page queue lock o kern/153150 xen [xen] xen/ec2: disable checksum offloading on interfac o kern/152228 xen [xen] [panic] Xen/PV panic with machdep.idle_mwait=1 o kern/144629 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143398 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143340 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor f kern/143069 xen [xen] [panic] Xen Kernel Panic - Memory modified after f kern/135667 xen ufs filesystem corruption on XEN DomU system f kern/135421 xen [xen] FreeBSD Xen PVM DomU network failure - netfronc. f kern/135178 xen [xen] Xen domU outgoing data transfer stall when TSO i p kern/135069 xen [xen] FreeBSD-current/Xen SMP doesn't function at all f i386/124516 xen [xen] FreeBSD-CURRENT Xen Kernel Segfaults when config o kern/118734 xen [xen] FreeBSD 6.3-RC1 and FreeBSD 7.0-BETA 4 fail to b 24 problems total. From owner-freebsd-xen@FreeBSD.ORG Mon Aug 15 12:53:02 2011 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CBD161065675 for ; Mon, 15 Aug 2011 12:53:02 +0000 (UTC) (envelope-from deuza@fr.freebsd.org) Received: from smtp.smtpout.orange.fr (smtp01.smtpout.orange.fr [80.12.242.123]) by mx1.freebsd.org (Postfix) with ESMTP id 35E2E8FC20 for ; Mon, 15 Aug 2011 12:53:01 +0000 (UTC) Received: from mbp.maison.com ([81.48.10.211]) by mwinf5d24 with ME id LcNy1h0094ZBwl503cNy8w; Mon, 15 Aug 2011 14:22:59 +0200 X-ME-engine: default From: Alain AUDEBERT aka 2A Date: Mon, 15 Aug 2011 14:22:58 +0200 Message-Id: <42031D84-71AC-419C-A1BE-EF496F3A31CA@fr.freebsd.org> To: freebsd-xen@freebsd.org Mime-Version: 1.0 (Apple Message framework v1244.3) X-Mailer: Apple Mail (2.1244.3) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: tunefs and domU ??? X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 15 Aug 2011 12:53:02 -0000 Hello list, I trying to "tunefs -m 1" a data volume with Xen, but there's no effect Is it possible ? Thanks for your answers Regards, Alain -- -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GIT/MU/S/SS d--(---)@ s++:++>+ a C++>+++ UBLS+++>++++$ P+++ L E--- W++ N++ o+ K- w--(---) O M+(++) V PS++ PE-- Y++ PGP+ !t !5 X++>+ R-- tv- b++ DI++ D+ G++ e+++ h++>+ r y* ------END GEEK CODE BLOCK------ From owner-freebsd-xen@FreeBSD.ORG Mon Aug 15 21:37:08 2011 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A7111106564A for ; Mon, 15 Aug 2011 21:37:08 +0000 (UTC) (envelope-from hoo.mb@web.de) Received: from fmmailgate01.web.de (fmmailgate01.web.de [217.72.192.221]) by mx1.freebsd.org (Postfix) with ESMTP id 4226F8FC17 for ; Mon, 15 Aug 2011 21:37:08 +0000 (UTC) Received: from smtp07.web.de ( [172.20.5.215]) by fmmailgate01.web.de (Postfix) with ESMTP id 6A1201956E264 for ; Mon, 15 Aug 2011 23:20:56 +0200 (CEST) Received: from [91.143.98.16] (helo=[192.168.226.106]) by smtp07.web.de with asmtp (TLSv1:AES256-SHA:256) (WEB.DE 4.110 #2) id 1Qt4ae-0006FZ-00 for freebsd-xen@freebsd.org; Mon, 15 Aug 2011 23:20:56 +0200 Message-ID: <4E498DB5.6030400@web.de> Date: Mon, 15 Aug 2011 23:20:53 +0200 From: Holger Fischer User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20110702 Icedove/3.0.11 MIME-Version: 1.0 To: freebsd-xen@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: hoo.mb@web.de X-Sender: hoo.mb@web.de X-Provags-ID: V01U2FsdGVkX183nqMH3leLjGv8hjvftg9x5t5owwQrzoKoa0Lt B1x9H361xSdNTIZ2BrFLEAS0pTpVv2lmLq+xgcwPIH3NjM8KUi n6wsGa2Dc= Subject: Where to get the latest kernel and world fixes for freebsd8-stable X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 15 Aug 2011 21:37:08 -0000 Hi All, What is the most stable and performant way to run freebsd 8 as xenhvm domu in 64bit. I decided to build my own mfsbsd(with CUSTOM=1 BUILDKERNEL=1 BUILDWORLD=1 KERNCONF=XENHVMHOO) with a fresh cvsup of freebsd-8-stable in /usr/src. I created my own kernel conf file XENHVMHOO in /usr/src/sys/amd64/conf and changed the modules_override option to makeoptions MODULES_OVERRIDE="zfs opensolaris ntfs ext2fs" for zfs-support Any recommendations for other changes in kernel conf file? Are there other patches available which are not in cvs tree of 8-stable? I'd rather use 8.x-release, is there a patchset for 8.x-release containing xen-relevant-patches only? What serious bugs are known and left in 8-stable? Are Patches available? I want to use fbsd-domu to have raidz zpool from 4 dom0 phy: - disks(2tb wd-re4-gp) and do file services and iscsi from that. Iscsi exports are imported in dom0 used for other domu's. At most I need nfsv3-FileService. I'll play around with samba from ports too to test interoperability with a 2008r2 ad at work possibly (including zfsacl/winacl/ricacl - tests). I've seen a bug report back in january somebody having troubles with iet-iscsi-target-port in domu. Is this resolved? Which is the most stable implementation of iscsi-targets(in domu) at the moment iet or istgt? FreeNAS still uses istgt, why? Under Linux People are more convinced with IET (as far as I know, correct me, if I'm wrong) Are there other kernel-based implementations for iscsi-target (planned) - like lio or scst on linux or comstar on solaris-based os's? What about performance of iscsi-target(iet or istgt)(in domu) under fbsd8. I believe it cannot be too bad because freenas provides iscsi-target support. Any counters on that? Again, for this use scenario any known bugs? I'd love to test something making freebsd run more stable as a xen-domu. I have a recent machine running xen at home with a bit free cpu and ram. They run mostly 24/7 so I can do longer tests too. Best regards Holger Fischer