From owner-freebsd-xen@FreeBSD.ORG Mon Jan 21 11:06:57 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 12AB9CC3 for ; Mon, 21 Jan 2013 11:06:57 +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 DFC4A73E for ; Mon, 21 Jan 2013 11:06:56 +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 r0LB6ufI054299 for ; Mon, 21 Jan 2013 11:06:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r0LB6uks054297 for freebsd-xen@FreeBSD.org; Mon, 21 Jan 2013 11:06:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 21 Jan 2013 11:06:56 GMT Message-Id: <201301211106.r0LB6uks054297@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, 21 Jan 2013 11:06:57 -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 Wed Jan 23 13:16:30 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 1F31D1CC for ; Wed, 23 Jan 2013 13:16:30 +0000 (UTC) (envelope-from mailinglists.tech@gmail.com) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by mx1.freebsd.org (Postfix) with ESMTP id B43F2C8 for ; Wed, 23 Jan 2013 13:16:29 +0000 (UTC) Received: by mail-wi0-f178.google.com with SMTP id hn3so695044wib.17 for ; Wed, 23 Jan 2013 05:16:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=JdGQ3SWdq1Kg1SkHVkqF09JZksuTPcnceoZVAzpvqYo=; b=pOi3jF3AseY4AqxB4kHIanS7PT7Q0p6oc4ISYg/wRo2bY9WSgtmiSK7WU7220OQVQT 8UcwMJ8/2ZQRgFcTClI6AAvzSsyAEbvcBAbTreM1v8dhHy5E6k2pHB9q/UOs4C6PCXRX zDevXdGAfzW2raVCV26mRVANQeNx+JfAeHyWzxmldYaBJO6GqPpllHN9G70Xl44lRNwp Y/k8FeBQGiJwX/MuDb5b4s7n4/3BD6O4Qq6b3SbVR2roUFIatFtORK28epnL8/4yP6ED Pt7QnG5VutgSbwwqcDosvEqYSbayKoQHQW3d07Xz4JgBECbQPF+lJbJxDapd6bD/0asN tOgw== MIME-Version: 1.0 X-Received: by 10.194.76.7 with SMTP id g7mr2506061wjw.50.1358946983451; Wed, 23 Jan 2013 05:16:23 -0800 (PST) Received: by 10.227.156.75 with HTTP; Wed, 23 Jan 2013 05:16:23 -0800 (PST) Date: Wed, 23 Jan 2013 14:16:23 +0100 Message-ID: Subject: Install FreeBSD PV DomU without HVM From: tech mailinglists To: freebsd-xen@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 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: Wed, 23 Jan 2013 13:16:30 -0000 Hello all, I have a running Xen 4.2.1 Setup on which Debian Squeeze with Linux 3.7.4 is running as Dom0. On this system I want to install FreeBSD i386 DomUs in PV mode. I searched in the web and only saw methods where first a HVM DomU is created in wiill be converted to a PV DomU. Is there a way to create a FreeBSD PV DomU without the need of a HVM DomU directly from within the Debian Dom0? For the filesystem I thought that it would be good to have ZFS. Would be very great when someone could help me. Best Regards From owner-freebsd-xen@FreeBSD.ORG Wed Jan 23 21:48:35 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 102B78FC for ; Wed, 23 Jan 2013 21:48:35 +0000 (UTC) (envelope-from jeroen@dckd.nl) Received: from positron.soleus.nu (positron.soleus.nu [IPv6:2a02:898:62:f6::63]) by mx1.freebsd.org (Postfix) with ESMTP id CF23B1F3 for ; Wed, 23 Jan 2013 21:48:34 +0000 (UTC) Received: from dyn21.dckd.nl (dyn21.dckd.nl [145.99.178.221]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by positron.soleus.nu (Postfix) with ESMTPSA id 48089F841E for ; Wed, 23 Jan 2013 22:48:32 +0100 (CET) From: Jeroen van der Ham Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Upgrading XENHVM 9.0 to 9.1 Message-Id: Date: Wed, 23 Jan 2013 22:48:29 +0100 To: freebsd-xen@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) 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: Wed, 23 Jan 2013 21:48:35 -0000 Hi, Today I started with an upgrade process of my VPS which has been running = 9.0 XENHVM almost a full year. I followed the process as outlined on the = Handbook[1]. I may have made a mistake in placing back the right old = kernel, but a new GENERIC kernel did not get installed. I was able to boot into the 9.1 system using my old 9.0 XENHVM kernel. I = have been trying to fix this, but I keep running into problems: - I manually downloaded and extracted the 9.1 GENERIC kernel. Booting = from that results in a rootmount mismatch (ada0 vs ad0). Just renaming = it in /etc/fstab does not seem to be enough, what else would I need to = do? - I manually built a new 9.1 XENHVM kernel. Booting from that results in = the message: "pudna: fpcurthread =3D=3D curthread xx times" scrolling = by. What can I do to fix that? Is there a problem in continuing to run the 9.0 XENHVM kernel with the = 9.1 system? Thanks for any help, Jeroen. [1]: = http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgradi= ng-freebsdupdate.html= From owner-freebsd-xen@FreeBSD.ORG Thu Jan 24 13:41:57 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 E616C449 for ; Thu, 24 Jan 2013 13:41:57 +0000 (UTC) (envelope-from feld@feld.me) Received: from feld.me (unknown [IPv6:2607:f4e0:100:300::2]) by mx1.freebsd.org (Postfix) with ESMTP id 525458BF for ; Thu, 24 Jan 2013 13:41:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=feld.me; s=blargle; h=In-Reply-To:Message-Id:From:Mime-Version:Cc:Date:References:Subject:To:Content-Type; bh=vYQdWjfOuUzlUCDyLceOnbp9QDyXpbsliNKmisEjQW0=; b=Ost7vvLUmnZjoH/0ldluY/LKxmhhhE+IiFvUbOrP2oeZ+Zb9f3QkFS9O2gS9/FM1JYU9ZhHUOdSEaCcXdfGUssZzq4j0mHANs51XfJI/wabNNSxWNjQprD0c4G1JKmaK; Received: from localhost ([127.0.0.1] helo=mwi1.coffeenet.org) by feld.me with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1TyN3q-000Oft-A7; Thu, 24 Jan 2013 07:41:46 -0600 Received: from feld@feld.me by mwi1.coffeenet.org (Archiveopteryx 3.1.4) with esmtpsa id 1359034899-44982-64949/5/1; Thu, 24 Jan 2013 13:41:39 +0000 Content-Type: text/plain; format=flowed; delsp=yes To: Jeroen van der Ham Subject: Re: Upgrading XENHVM 9.0 to 9.1 References: Date: Thu, 24 Jan 2013 07:41:39 -0600 Mime-Version: 1.0 From: Mark Felder Message-Id: In-Reply-To: User-Agent: Opera Mail/12.12 (FreeBSD) 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: Thu, 24 Jan 2013 13:41:58 -0000 On Wed, 23 Jan 2013 15:48:29 -0600, Jeroen van der Ham wrote: > Hi, > > Today I started with an upgrade process of my VPS which has been running > 9.0 XENHVM almost a full year. I followed the process as outlined on the > Handbook[1]. I may have made a mistake in placing back the right old > kernel, but a new GENERIC kernel did not get installed. > > I was able to boot into the 9.1 system using my old 9.0 XENHVM kernel. I > have been trying to fix this, but I keep running into problems: > > - I manually downloaded and extracted the 9.1 GENERIC kernel. Booting > from that results in a rootmount mismatch (ada0 vs ad0). Just renaming > it in /etc/fstab does not seem to be enough, what else would I need to > do? Yes, the GENERIC kernel uses adaX and the XENHVM kernel uses adX. It shouldn't be a problem to just change it in the fstab though. I've not yet had problems running 9.1 with XENHVM yet. > > - I manually built a new 9.1 XENHVM kernel. Booting from that results in > the message: "pudna: fpcurthread == curthread xx times" scrolling by. > What can I do to fix that? > I've not seen this message yet either. Can you provide more details of the Xen environment you're hosted on? > Is there a problem in continuing to run the 9.0 XENHVM kernel with the > 9.1 system? > This would not be advised. It *may* work, but be warned that you may run into strange issues. From owner-freebsd-xen@FreeBSD.ORG Thu Jan 24 14:16:33 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 411FF848 for ; Thu, 24 Jan 2013 14:16:33 +0000 (UTC) (envelope-from jeroen@dckd.nl) Received: from positron.soleus.nu (positron.soleus.nu [IPv6:2a02:898:62:f6::63]) by mx1.freebsd.org (Postfix) with ESMTP id F367DA04 for ; Thu, 24 Jan 2013 14:16:32 +0000 (UTC) Received: from u020807.science.uva.nl (u020807.science.uva.nl [146.50.52.180]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by positron.soleus.nu (Postfix) with ESMTPSA id 7F33FF8024; Thu, 24 Jan 2013 15:16:22 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: Upgrading XENHVM 9.0 to 9.1 From: Jeroen van der Ham In-Reply-To: Date: Thu, 24 Jan 2013 15:16:21 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Mark Felder X-Mailer: Apple Mail (2.1499) 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: Thu, 24 Jan 2013 14:16:33 -0000 Hi, On 24 Jan 2013, at 14:41, Mark Felder wrote: >> - I manually downloaded and extracted the 9.1 GENERIC kernel. Booting = from that results in a rootmount mismatch (ada0 vs ad0). Just renaming = it in /etc/fstab does not seem to be enough, what else would I need to = do? >=20 > Yes, the GENERIC kernel uses adaX and the XENHVM kernel uses adX. It = shouldn't be a problem to just change it in the fstab though. I've not = yet had problems running 9.1 with XENHVM yet. I tried this both using the mountroot prompt when booting with an old = fstab and a corrected fstab. In both cases the kernel is not able to = mount the UFS volume. >> - I manually built a new 9.1 XENHVM kernel. Booting from that results = in the message: "pudna: fpcurthread =3D=3D curthread xx times" scrolling = by. What can I do to fix that? >>=20 >=20 > I've not seen this message yet either.=20 I've seen this message also previously when I was toying around with my = 9.0 system. I forget what exactly I did though. There are some references to it in earlier cases, dating back to 2005: http://marc.info/?l=3Dfreebsd-amd64&m=3D112231842214570 Another in 2010: http://forums.freebsd.org/showthread.php?t=3D17979 (I did not try those options yet though) > Can you provide more details of the Xen environment you're hosted on? AMD Opteron system, with kernel 2.6.32 on Dom0, using 4.0.1-2. My VPS is run using Xen qemu. >> Is there a problem in continuing to run the 9.0 XENHVM kernel with = the 9.1 system? >>=20 >=20 > This would not be advised. It *may* work, but be warned that you may = run into strange issues. I noticed that freebsd-update started complaining during its cron-job. = I've since performed a freebsd-update rollback. Jeroen.