From owner-freebsd-xen@FreeBSD.ORG Mon Apr 1 11:06:55 2013 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0D54F917 for ; Mon, 1 Apr 2013 11:06:55 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id E4EAC350 for ; Mon, 1 Apr 2013 11:06:54 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r31B6sri033886 for ; Mon, 1 Apr 2013 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r31B6s9E033884 for freebsd-xen@FreeBSD.org; Mon, 1 Apr 2013 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 1 Apr 2013 11:06:54 GMT Message-Id: <201304011106.r31B6s9E033884@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 Subject: Current problem reports assigned to freebsd-xen@FreeBSD.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 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, 01 Apr 2013 11:06:55 -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/176471 xen [xen] xn driver crash on detach o kern/176053 xen [xen] [patch] i386: Correct wrong usage of vsnprintf() o kern/175954 xen [xen] XENHVM xn network driver extreme packet loss dur o kern/175822 xen [xen] FreeBSD 9.1 does not work with Xen 4.0 o kern/175757 xen [xen] [patch] xen pvhvm looses keyboard input from VNC o kern/171873 xen [xen] xn network device floods warning in dmesg o kern/171118 xen [xen] FreeBSD XENHVM guest doesn't shutdown cleanly o kern/166174 xen [xen] Problems ROOT MOUNT ERROR o kern/165418 xen [xen] Problems mounting root filesystem from XENHVM o kern/164630 xen [xen] XEN HVM kernel: run_interrupt_driven_hooks: stil o kern/164450 xen [xen] Failed to install FreeeBSD 9.0-RELEASE from CD i o kern/162677 xen [xen] FreeBSD not compatible with "Current Stable Xen" o kern/161318 xen [xen] sysinstall crashes with floating point exception 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/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 35 problems total. From owner-freebsd-xen@FreeBSD.ORG Mon Apr 1 11:20:02 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7EE4363A for ; Mon, 1 Apr 2013 11:20:02 +0000 (UTC) (envelope-from roger.pau@citrix.com) Received: from SMTP.EU.CITRIX.COM (smtp.eu.citrix.com [46.33.159.39]) by mx1.freebsd.org (Postfix) with ESMTP id 204CD7A3 for ; Mon, 1 Apr 2013 11:20:01 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.87,385,1363132800"; d="scan'208";a="3087147" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 01 Apr 2013 11:18:52 +0000 Received: from [192.168.1.30] (10.30.249.104) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.298.1; Mon, 1 Apr 2013 12:18:52 +0100 Message-ID: <51596D1B.6080209@citrix.com> Date: Mon, 1 Apr 2013 13:18:51 +0200 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Cherry G.Mathew Subject: Re: [Xen-users] Trouble booting FreeBSD i386 PV DomU References: <51516B06.8080704@citrix.com> <87fvzbqx90.fsf@foobar.i-did-not-set--mail-host-address--so-tickle-me> In-Reply-To: <87fvzbqx90.fsf@foobar.i-did-not-set--mail-host-address--so-tickle-me> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Cc: "freebsd-xen@freebsd.org" , xen-users X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 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, 01 Apr 2013 11:20:02 -0000 On 31/03/13 19:45, Cherry G.Mathew wrote: > > On 21/02/13 10:18, tech mailinglists wrote: >> Hello all, >> >> I have created a FreeBSD PV DomU image formatted with ZFS. I compiled >> FreeBSD with KERNCONF=XEN for the kernel and the normal world and >> distribution target. Then I transfered it to a Debian Dom0 with Xen 4.2.1. >> >> I tried to boot the image befor I migrate it to LVM and I now get teh >> following output: >> > > [...] > >> run_interrupt_driven_hooks: still waiting after 300 seconds for >> xenbus_free_evtchn >> panic: run_interrupt_driven_config_hooks: waited too long >> cpuid = 0 >> KDB: enter: panic >> [ thread pid 0 tid 100000 ] >> Stopped at kdb_enter+0x3a: movl $0,kdb_why >> db> > > > Try see if patch below should help the boot a bit along. The problem is already solved, it was crashing because blkback in Dom0 was not correctly working -- nothing to do with FreeBSD. The 9.x releases work correctly, the problem is with HEAD and the backtrace I've posted. BTW, if you wish to try HEAD you will need the ELFNOTE patch I've posted and boot with "hw.mca.enabled=0" to get to the panic I've posted earlier. From owner-freebsd-xen@FreeBSD.ORG Mon Apr 1 21:24:46 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B4F46211 for ; Mon, 1 Apr 2013 21:24:46 +0000 (UTC) (envelope-from knockknock@gmail.com) Received: from mail-ve0-f171.google.com (mail-ve0-f171.google.com [209.85.128.171]) by mx1.freebsd.org (Postfix) with ESMTP id 7D2C81FC for ; Mon, 1 Apr 2013 21:24:46 +0000 (UTC) Received: by mail-ve0-f171.google.com with SMTP id b10so3119436vea.30 for ; Mon, 01 Apr 2013 14:24:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:from:date:x-google-sender-auth :message-id:subject:to:content-type; bh=PHIbkC1o99j9w7qlXjmaODXMphTSsd1hVikSqs+w3wc=; b=TZcqhj+TVTag5pOFOgkKJogBh0VOuAuJgYntss7TxR1oRyVMQAOAWaqBzGr3Mv5pJs SU/1ewdMLYAkgq1+3MsUtHpmxSXy1D4dtPFfbjMSf8wkmoWIvqShXZottgGKEE8LZ+N9 by0IKPokLn/ZdPaMMe24bzWTdZ/m0nrU1w2FHhSOtAZ7YP4CfHt461C8VRbCdtd3MOyW zUQqlj7bV7KDtR6+jdBSQ0bT+FzNAn1unQq8uk9/h8oQBuWO2kce1DZR4R2mxm5rSIkD +Txg+JQWpjNpo/VYOQtvUCQeEAnoTQ8zQ3nHxOheFX+tBkYy+qpbWk2X8dqeG9yspjJA 4ncQ== X-Received: by 10.52.171.193 with SMTP id aw1mr9135141vdc.49.1364851485559; Mon, 01 Apr 2013 14:24:45 -0700 (PDT) MIME-Version: 1.0 Sender: knockknock@gmail.com Received: by 10.52.122.197 with HTTP; Mon, 1 Apr 2013 14:24:25 -0700 (PDT) From: Eric Shelton Date: Mon, 1 Apr 2013 17:24:25 -0400 X-Google-Sender-Auth: pR2A9AQxgQXvpDoi8gr67LzunmU Message-ID: Subject: configuration for FreeBSD as domU "storage domain"? To: freebsd-xen@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 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, 01 Apr 2013 21:24:46 -0000 Dear List, Although I understand it is possible, I have not found any clear examples of xl configs and how to configure FreeBSD to serve up a block device from a FreeBSD domU via blkfront. For example, given the following set of domains: 1: Linux dom0 2: FreeBSD HVM domU (serving up a zvol via blkfront, PCI passthrough of underlying storage devices) 3: Windows 7 HVM domU (using the zvol as its root fs) What needs to be done within FreeBSD to expose the zvol via blkfront? What does the "disks" portion of the xl config file look like for starting up the FreeBSD domain? (What is the format like when a domU is serving up a block device?) What does the "disks" portion of the xl config file look like for starting up the Windows 7 domain? (What is the format like when you wish to attach to block device served up by a domU, not dom0?). Thank you for your help, Eric From owner-freebsd-xen@FreeBSD.ORG Tue Apr 2 13:19:21 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B7D14C37 for ; Tue, 2 Apr 2013 13:19:21 +0000 (UTC) (envelope-from knockknock@gmail.com) Received: from mail-vc0-f177.google.com (mail-vc0-f177.google.com [209.85.220.177]) by mx1.freebsd.org (Postfix) with ESMTP id 810171F8 for ; Tue, 2 Apr 2013 13:19:21 +0000 (UTC) Received: by mail-vc0-f177.google.com with SMTP id ia10so390470vcb.36 for ; Tue, 02 Apr 2013 06:19:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:references:from:in-reply-to:mime-version:date:message-id :subject:to:content-type; bh=v5DPSS52yPEHGLtx6cm0obysLEt9Kc4N0+tBs+7trik=; b=J0s509Wj8BvF+HgP4d+sW1QCNaeqCndgKcg3VgivJZKsXd+LtY3bbVwcYAJFVt2TK2 6hJo43hk2nK1U3SgW0ue6vapegafhgGfmwYpZ2kxJX59eIOyokG5QTEH4fUzOGxexL43 JDgqaDc1g5qG5FsiBiu3IXN52Xt5TsJsOaoYhbdC28e9TD2vDpvBZU24fpV0o0qvT8DS ZtZrlxgtM1wPKUmXMgS1xpp/okXkkyEFUXxlWV4l4UoyVzQsvyy4DAiwxvjHuGeRmQvX bjjyt5KW9+LAWr8hy0F2xv/87dg76V7jzKuLRKASrO6asJf/UzLUJ1yggomvVynCRNn2 FBcw== X-Received: by 10.58.245.40 with SMTP id xl8mr12509580vec.33.1364908760675; Tue, 02 Apr 2013 06:19:20 -0700 (PDT) References: From: Eric Shelton In-Reply-To: Mime-Version: 1.0 (1.0) Date: Tue, 2 Apr 2013 09:19:20 -0400 Message-ID: <-3378255293464856149@unknownmsgid> Subject: Re: configuration for FreeBSD as domU "storage domain"? To: "freebsd-xen@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 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, 02 Apr 2013 13:19:21 -0000 Of course, it is blkback, not blkfront, that I would want to use to serve up block devices... On Apr 1, 2013, at 5:24 PM, Eric Shelton wrote: > Dear List, > > Although I understand it is possible, I have not found any clear > examples of xl configs and how to configure FreeBSD to serve up a > block device from a FreeBSD domU via blkfront. > > For example, given the following set of domains: > 1: Linux dom0 > 2: FreeBSD HVM domU (serving up a zvol via blkfront, PCI passthrough > of underlying storage devices) > 3: Windows 7 HVM domU (using the zvol as its root fs) > > What needs to be done within FreeBSD to expose the zvol via blkfront? > > What does the "disks" portion of the xl config file look like for > starting up the FreeBSD domain? (What is the format like when a domU > is serving up a block device?) > > What does the "disks" portion of the xl config file look like for > starting up the Windows 7 domain? (What is the format like when you > wish to attach to block device served up by a domU, not dom0?). > > Thank you for your help, > Eric