From owner-freebsd-xen@FreeBSD.ORG Mon Dec 17 11:06:55 2012 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7FF56A03 for ; Mon, 17 Dec 2012 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 637B08FC1A for ; Mon, 17 Dec 2012 11:06:55 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qBHB6tGX023686 for ; Mon, 17 Dec 2012 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qBHB6sLD023684 for freebsd-xen@FreeBSD.org; Mon, 17 Dec 2012 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 17 Dec 2012 11:06:54 GMT Message-Id: <201212171106.qBHB6sLD023684@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, 17 Dec 2012 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/171873 xen [xen] xn network device floods warning in dmesg o kern/171138 xen [xen] [panic] Deactivating network interface produces 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 31 problems total. From owner-freebsd-xen@FreeBSD.ORG Thu Dec 20 23:37:41 2012 Return-Path: Delivered-To: xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DB2C581A for ; Thu, 20 Dec 2012 23:37:41 +0000 (UTC) (envelope-from itetcu@FreeBSD.org) Received: from mx.tetcu.info (mx.tetcu.info [217.19.15.179]) by mx1.freebsd.org (Postfix) with ESMTP id 8F05D8FC0A for ; Thu, 20 Dec 2012 23:37:41 +0000 (UTC) Received: from it.tim.tetcu.info (unknown [188.26.250.213]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx.tetcu.info (Postfix) with ESMTPSA id A3ABA2563F6 for ; Fri, 21 Dec 2012 01:31:38 +0200 (EET) Date: Fri, 21 Dec 2012 01:31:38 +0200 From: Ion-Mihai Tetcu To: xen@freebsd.org Subject: XENHVM ada -> ad ? Message-ID: <20121221013138.7a428448@it.tim.tetcu.info> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.6; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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: Thu, 20 Dec 2012 23:37:41 -0000 Hi, I have the feeling I'm missing something very basic here: I have a 9-STABLE-amd64 (as of a few minutes ago, but I see the same thing with older versions) running as guest on Xen HVM (APIC, ACPI on). I can boot the GENERIC kernel, but trying to boot the XENHVM kernel results in trying to mount root from ufs: /dev/ada0p2 [rw] ... mountroot: waiting for device /dev/ada0p2 ... Mounting from ufs:/dev/ada0p2 failed with error 19. I can: mountroot> ufs:ad0p2 and it breaks there, of course. Do I need to translate from 'ada' back to 'ad' if I use XENHVM? Why? Thanks, -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID F0808380 From owner-freebsd-xen@FreeBSD.ORG Fri Dec 21 02:29:49 2012 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 000BE35D for ; Fri, 21 Dec 2012 02:29:48 +0000 (UTC) (envelope-from mikekaganski@mail.ru) Received: from fallback1.mail.ru (fallback1.mail.ru [94.100.176.18]) by mx1.freebsd.org (Postfix) with ESMTP id 9ACB68FC13 for ; Fri, 21 Dec 2012 02:29:48 +0000 (UTC) Received: from smtp24.mail.ru (smtp24.mail.ru [94.100.176.177]) by fallback1.mail.ru (mPOP.Fallback_MX) with ESMTP id E88C3D2ECBF for ; Fri, 21 Dec 2012 06:00:12 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:To:MIME-Version:From:Date:Message-ID; bh=3PlANm8yKMpqmMgYSZp5f8SKcI/hq5K7HYeLh1iVqg0=; b=BUfd+qBqxIhtf35zwi1+gEmdGAuW1SyRDHbMn9zjgWAYqpA7AOvIe5HUoV4LJ4CmZyW/5tnEj2/p5R8VoN0GK90bc9yUDm0KdvS0SjoBME7IFInJD50O9AIIu0lMAJW0; Received: from [212.19.9.88] (port=12357 helo=[192.168.1.10]) by smtp24.mail.ru with esmtpa (envelope-from ) id 1Tlru9-0007fm-HH for freebsd-xen@freebsd.org; Fri, 21 Dec 2012 06:00:05 +0400 Message-ID: <50D3C2A4.2020103@mail.ru> Date: Fri, 21 Dec 2012 13:00:04 +1100 From: Mike Kaganski User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: freebsd-xen@freebsd.org Subject: Re: XENHVM ada -> ad ? References: <20121221013138.7a428448@it.tim.tetcu.info> In-Reply-To: <20121221013138.7a428448@it.tim.tetcu.info> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam: Not detected X-Mras: Ok 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: Fri, 21 Dec 2012 02:29:49 -0000 On 12/21/2012 10:31 AM, Ion-Mihai Tetcu wrote: > Do I need to translate from 'ada' back to 'ad' if I use XENHVM? Why? Yes, because the FreeBSD's XEN ata driver has not been moved to new naming scheme yet. -- Best regards, Mike Kaganski From owner-freebsd-xen@FreeBSD.ORG Fri Dec 21 16:05:33 2012 Return-Path: Delivered-To: xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1732529C; Fri, 21 Dec 2012 16:05:33 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout2.yahoo.com (mrout2.yahoo.com [216.145.54.172]) by mx1.freebsd.org (Postfix) with ESMTP id E90F58FC13; Fri, 21 Dec 2012 16:05:29 +0000 (UTC) Received: from [127.0.0.1] (proxy6.corp.yahoo.com [216.145.48.19]) by mrout2.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id qBLG5AoT059039; Fri, 21 Dec 2012 08:05:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1356105910; bh=XR6oaUD8Ov4saQ0wfXHFP8jRORpnxgwrPAP2Ubv4B5I=; h=Subject:From:Reply-To:To:Cc:In-Reply-To:References:Content-Type: Date:Message-ID:Mime-Version:Content-Transfer-Encoding; b=DTK2tDWPWxCXZqELBbfkTCy9UP/cXU8zPTuVyvuPYNNy3M6SqSlKcoRkjv0kk9VSv E5ZzsxxMA/8Mx82w2QV5N7LqnuDd56QEnCauSaXj/iEbuIxep440BAh3LRVrlgpLLq gyaDxEqpXo869wyuV7iC20CRUIroUfhKi9L2cttA= Subject: Re: XENHVM ada -> ad ? From: Sean Bruno To: Ion-Mihai Tetcu In-Reply-To: <20121221013138.7a428448@it.tim.tetcu.info> References: <20121221013138.7a428448@it.tim.tetcu.info> Content-Type: text/plain; charset="UTF-8" Date: Fri, 21 Dec 2012 08:05:09 -0800 Message-ID: <1356105909.3022.3.camel@powernoodle.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Milter-Version: master.31+4-gbc07cd5+ X-CLX-ID: 105910000 Cc: xen@FreeBSD.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: sbruno@FreeBSD.org 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: Fri, 21 Dec 2012 16:05:33 -0000 On Fri, 2012-12-21 at 01:31 +0200, Ion-Mihai Tetcu wrote: > Hi, > > > I have the feeling I'm missing something very basic here: > > I have a 9-STABLE-amd64 (as of a few minutes ago, but I see the same > thing with older versions) running as guest on Xen HVM (APIC, ACPI on). > > I can boot the GENERIC kernel, but trying to boot the XENHVM kernel > results in > trying to mount root from ufs: /dev/ada0p2 [rw] ... > mountroot: waiting for device /dev/ada0p2 ... > Mounting from ufs:/dev/ada0p2 failed with error 19. > > I can: > mountroot> ufs:ad0p2 > and it breaks there, of course. > > Do I need to translate from 'ada' back to 'ad' if I use XENHVM? Why? > > > Thanks, > Yes. adaX-->adX. Look at the dmesg on bootup. Sean From owner-freebsd-xen@FreeBSD.ORG Fri Dec 21 16:19:30 2012 Return-Path: Delivered-To: xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 899B178A; Fri, 21 Dec 2012 16:19:30 +0000 (UTC) (envelope-from feld@feld.me) Received: from feld.me (feld.me [66.170.3.2]) by mx1.freebsd.org (Postfix) with ESMTP id 567E58FC13; Fri, 21 Dec 2012 16:19:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=feld.me; s=blargle; h=Content-Transfer-Encoding:Content-Type:Mime-Version:References:In-Reply-To:Message-Id:Subject:Cc:To:From:Date; bh=7OZT2FFaa8rf+6U7/+syk0KVrQlYWXd4ps+DKIeBwHw=; b=Dw3dTHocoHi+0UmV1cWhkgXZPrmvv/gF/nUWnp6a3XzLqviGOz3iJOcf3OhTgUarUHyZkQx/cT7dfKXoo4IoXAZdNpniqVfniwrt9XU/n8ecdlrZ+3RBNGAuXK3XEbTm; Received: from localhost ([127.0.0.1] helo=mwi1.coffeenet.org) by feld.me with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1Tm5Jo-0003Ty-0u; Fri, 21 Dec 2012 10:19:29 -0600 Received: from feld@feld.me by mwi1.coffeenet.org (Archiveopteryx 3.1.4) with esmtpa id 1356106762-2688-2687/5/28; Fri, 21 Dec 2012 16:19:22 +0000 Date: Fri, 21 Dec 2012 10:19:22 -0600 From: Mark Felder To: Ion-Mihai Tetcu Subject: Re: XENHVM ada -> ad ? Message-Id: <20121221101922.0e87fac1@tech304> In-Reply-To: <20121221013138.7a428448@it.tim.tetcu.info> References: <20121221013138.7a428448@it.tim.tetcu.info> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.6; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable X-SA-Report: ALL_TRUSTED=-1, KHOP_THREADED=-0.5 X-SA-Score: -1.5 Cc: 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: Fri, 21 Dec 2012 16:19:30 -0000 On this topic, is there any way to *definitively* know which Xen block = device corresponds to which adaX device? The guys at Citrix really want = to know instead of just assuming that xbd.0 is ada0. Perhaps adding a = sysctl value like "dev.xbd.0.%block: /dev/ada0" would be nice... Who = would I talk to about this? Hint: they're adding official tools support for FreeBSD soon. fake edit: perhaps they can work with the "dev.xbd.0.%parent: xenbusb_fro= nt0" type output. I'll see... From owner-freebsd-xen@FreeBSD.ORG Fri Dec 21 18:27:24 2012 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 19C9770C for ; Fri, 21 Dec 2012 18:27:24 +0000 (UTC) (envelope-from jwest@ezwind.net) Received: from ezwind.net (bobby.ezwind.net [209.145.140.14]) by mx1.freebsd.org (Postfix) with ESMTP id CC8B68FC15 for ; Fri, 21 Dec 2012 18:27:23 +0000 (UTC) Received: from LENOVOD6B52A6B by ezwind.net (MDaemon.PRO.v8.1.3.R) with ESMTP id 33-md50000140484.msg for ; Fri, 21 Dec 2012 12:26:38 -0600 From: "Jay West" To: Subject: 9.1R? Date: Fri, 21 Dec 2012 12:26:36 -0600 Message-ID: <000301cddfa8$b6af8b70$240ea250$@ezwind.net> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac3fpuggz8tkgTNvRDuDC8Rq8gBy+Q== Content-Language: en-us X-Authenticated-Sender: jwest@ezwind.net X-Spam-Processed: gateway.ezwind.net, Fri, 21 Dec 2012 12:26:38 -0600 (not processed: message from valid local sender) X-MDRemoteIP: 199.188.211.132 X-Return-Path: jwest@ezwind.net X-MDaemon-Deliver-To: freebsd-xen@freebsd.org X-MDAV-Processed: gateway.ezwind.net, Fri, 21 Dec 2012 12:26:41 -0600 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Fri, 21 Dec 2012 18:27:24 -0000 As one of the many that have been delaying a major production rollout in anticipation of the release of 9.1, I've been anxiously awaiting. No announcement yet, but I did notice ftp.freebsd.org has an amd64 9.1-Release iso for download. Given the date of the file as 12/4 I'm a little hesitant to just jump on it and start building VM's.. Anyone else notice/use this yet? All our FreeBSD use is now under Xenserver 6.1. I was curious, given the port of xe-guest-utilities that allows online migrations and such. after installing those tools (thus PVM/64), should we be changing our mount points to refer to the xen hd device (xbdX) or continue to use adX inside the VM for filesystem mounts (kinda like we need to change the network device {ex. bgeX} to xnX)? Just looking for a sanity check J Jay West EZwind.net PO Box 460474 Saint Louis, MO 63146 Voice: (314) 262-4143 ext 1000 Toll Free: (866) 343-2589 Fax: (314) 558-9284 jwest@ezwind.net -------------------------------------------- This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you are not the intended recipient or their designee, please notify the sender immediately by return e-mail and delete all copies. From owner-freebsd-xen@FreeBSD.ORG Sat Dec 22 07:29:44 2012 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B58CC491 for ; Sat, 22 Dec 2012 07:29:44 +0000 (UTC) (envelope-from feld@feld.me) Received: from feld.me (feld.me [66.170.3.2]) by mx1.freebsd.org (Postfix) with ESMTP id 835158FC0C for ; Sat, 22 Dec 2012 07:29:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=feld.me; s=blargle; h=Content-Transfer-Encoding:Content-Type:Mime-Version:References:In-Reply-To:Message-Id:Subject:Cc:To:From:Date; bh=gyMiKzolyZAXyRg3m8uKt49fAuEvcV0ySGSkuAduz1A=; b=KeX9s2I+iG8MwiAGDpiAGwHcmeH+4DkdoLlUr2XRZ8JYfiGKTrVIj3qQlzhWA+MGmgLvU1EcTpWvfsJk1B2/+cm5Gb5j7OULc6a5/peJ930OTBlpf+7mmBFykO/8Va9g; Received: from localhost ([127.0.0.1] helo=mwi1.coffeenet.org) by feld.me with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1TmJWe-000CTF-6B; Sat, 22 Dec 2012 01:29:43 -0600 Received: from feld@feld.me by mwi1.coffeenet.org (Archiveopteryx 3.1.4) with esmtpa id 1356161374-2688-2687/5/30; Sat, 22 Dec 2012 07:29:34 +0000 Date: Sat, 22 Dec 2012 01:29:33 -0600 From: Mark Felder To: Jay West Subject: Re: 9.1R? Message-Id: <20121222012933.5694d482@tech304> In-Reply-To: <000301cddfa8$b6af8b70$240ea250$@ezwind.net> References: <000301cddfa8$b6af8b70$240ea250$@ezwind.net> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.6; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable X-SA-Report: ALL_TRUSTED=-1, KHOP_THREADED=-0.5 X-SA-Score: -1.5 Cc: 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: Sat, 22 Dec 2012 07:29:44 -0000 On Fri, 21 Dec 2012 12:26:36 -0600 Jay West wrote: > All our FreeBSD use is now under Xenserver 6.1. I was curious, given = the > port of xe-guest-utilities that allows online migrations and such. = after > installing those tools (thus PVM/64), should we be changing our mount = points > to refer to the xen hd device (xbdX) or continue to use adX inside the = VM > for filesystem mounts (kinda like we need to change the network device = {ex. > bgeX} to xnX)? Just looking for a sanity check J You'll notice that /dev/xbd* doesn't actually exist :-) Also, if you aren't aware, here is my personal list of Xen bugs: - Shutdown via Xen fails to poweroff. It doesn't issue any normal = shutdown commands, but tells the Xen code in the kernel to start a shutdown. It's broken = on the kernel side. kern/171118=20 Also, NetBSD's workaround for this is to enable powerd, but we can't when we're running XENHVM and I suspect their powerd is a completely = different beast. - If you use PF with Xen HVM your performance will suck. Known bug. kern/154428 Set net.inet.tcp.tso=3D0 as a workaround. - "Deactivating" a network interface is an option after enabling the = xe-guest-utilities scripts. Please don't do that. It seems to cause a panic every time. kern/171138 Also, this happens when you try to change the VLAN assigned to an interface. From owner-freebsd-xen@FreeBSD.ORG Sat Dec 22 16:51:04 2012 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E77873A2 for ; Sat, 22 Dec 2012 16:51:04 +0000 (UTC) (envelope-from hugo@barafranca.com) Received: from mail.barafranca.com (mail.barafranca.com [67.213.67.47]) by mx1.freebsd.org (Postfix) with ESMTP id A33798FC0C for ; Sat, 22 Dec 2012 16:51:04 +0000 (UTC) Received: from localhost (unknown [172.16.100.24]) by mail.barafranca.com (Postfix) with ESMTP id 44C1AF91; Sat, 22 Dec 2012 16:50:58 +0000 (UTC) X-Virus-Scanned: amavisd-new at barafranca.com Received: from mail.barafranca.com ([172.16.100.24]) by localhost (mail.barafranca.com [172.16.100.24]) (amavisd-new, port 10024) with ESMTP id qf+Dry4J4HW5; Sat, 22 Dec 2012 16:50:15 +0000 (UTC) Received: from [192.168.1.1] (a89-152-58-56.cpe.netcabo.pt [89.152.58.56]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.barafranca.com (Postfix) with ESMTPSA id 61B1CF8B; Sat, 22 Dec 2012 16:50:13 +0000 (UTC) Message-ID: <50D5E4B4.2000408@barafranca.com> Date: Sat, 22 Dec 2012 16:49:56 +0000 From: Hugo Silva User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: Mark Felder Subject: Re: 9.1R? References: <000301cddfa8$b6af8b70$240ea250$@ezwind.net> <20121222012933.5694d482@tech304> In-Reply-To: <20121222012933.5694d482@tech304> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: 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: Sat, 22 Dec 2012 16:51:05 -0000 On 12/22/12 07:29, Mark Felder wrote: > On Fri, 21 Dec 2012 12:26:36 -0600 > Jay West wrote: > >> All our FreeBSD use is now under Xenserver 6.1. I was curious, given the >> port of xe-guest-utilities that allows online migrations and such. after >> installing those tools (thus PVM/64), should we be changing our mount points >> to refer to the xen hd device (xbdX) or continue to use adX inside the VM >> for filesystem mounts (kinda like we need to change the network device {ex. >> bgeX} to xnX)? Just looking for a sanity check J > > You'll notice that /dev/xbd* doesn't actually exist :-) > FWIW: > Also, if you aren't aware, here is my personal list of Xen bugs: > > - Shutdown via Xen fails to poweroff. It doesn't issue any normal shutdown commands, > but tells the Xen code in the kernel to start a shutdown. It's broken on the kernel > side. kern/171118 > Also, NetBSD's workaround for this is to enable powerd, but we can't > when we're running XENHVM and I suspect their powerd is a completely different beast. > netbsd-dom0# xm shutdown firewall-2 (xm console firewall-2) FreeBSD/amd64 (firewall-2.xxx.local) (cuau0) login: pflog0: promiscuous mode disabled Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...4 4 3 1 1 0 0 done All buffers synced. Uptime: 2d13h50m8s acpi0: Powering system off root@netbsd-dom0:/usr/pkg/etc/xen/conf# Works here. But that FreeBSD domU is 10-CURRENT.. 9.1-PRERELEASE also works though: FreeBSD/amd64 (haproxy-2.xxx.local) (cuau0) login: pflog0: promiscuous mode disabled Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...9 9 7 6 1 1 1 0 0 0 done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done All buffers synced. Uptime: 2d13h50m0s acpi0: Powering system off root@netbsd-dom0:/usr/pkg/etc/xen/conf# > - If you use PF with Xen HVM your performance will suck. Known bug. > kern/154428 > Set net.inet.tcp.tso=0 as a workaround. > Hmm. I'm running PF on all the FreeBSD domUs and notice no slowdown. The traffic isn't that much, 1000 states and 300 searches/s (pfctl -si) on the application servers. The load balancers are slightly higher, 4000 states and 900 searches/s. Still nothing spectacular but again, no problems. I do remember this being an issue at some point in the past though. > - "Deactivating" a network interface is an option after enabling the xe-guest-utilities scripts. > Please don't do that. It seems to cause a panic every time. kern/171138 > Also, this happens when you try to change the VLAN assigned to an > interface. No idea about this. From owner-freebsd-xen@FreeBSD.ORG Sat Dec 22 18:37:23 2012 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AF08D9FE for ; Sat, 22 Dec 2012 18:37:23 +0000 (UTC) (envelope-from feld@feld.me) Received: from feld.me (feld.me [66.170.3.2]) by mx1.freebsd.org (Postfix) with ESMTP id 7D6A18FC12 for ; Sat, 22 Dec 2012 18:37:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=feld.me; s=blargle; h=Message-Id:Cc:To:Date:From:Subject:Content-Type:Mime-Version:References:In-Reply-To; bh=LdnKcCUOXLZ92bLprUCMbFfQSoex6kvH3uv+l0ZRaJ8=; b=IkW3xXqpEUAQQjsbr93O0UUaSpfpFeEXo5FePhehyvr5KOBacx8dtd2xBzDo4TRHxlnSm2NQWD0FD5ge5dzpwmgyw/UUfcKxrFet1C6+HeLGDHpbtj0cRp7JfLpanbLR; Received: from localhost ([127.0.0.1] helo=mwi1.coffeenet.org) by feld.me with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1TmTwd-0007A8-DU; Sat, 22 Dec 2012 12:37:16 -0600 Received: from feld@feld.me by mwi1.coffeenet.org (Archiveopteryx 3.1.4) with esmtpa id 1356201425-2688-2687/5/33; Sat, 22 Dec 2012 18:37:05 +0000 User-Agent: K-9 Mail for Android In-Reply-To: <50D5E4B4.2000408@barafranca.com> References: <000301cddfa8$b6af8b70$240ea250$@ezwind.net> <20121222012933.5694d482@tech304> <50D5E4B4.2000408@barafranca.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Subject: Re: 9.1R? From: Mark Felder Date: Sat, 22 Dec 2012 12:36:12 -0600 To: Hugo Silva Message-Id: <52cd7e14-c855-46ce-813d-84e46ccd88dc@email.android.com> X-SA-Report: ALL_TRUSTED=-1, KHOP_THREADED=-0.5 X-SA-Score: -1.5 Cc: 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: Sat, 22 Dec 2012 18:37:23 -0000 You're not running XCP or XenServer. That's why you don't have those bugs.