From owner-freebsd-virtualization@FreeBSD.ORG Mon Oct 22 07:50:01 2012 Return-Path: Delivered-To: freebsd-virtualization@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 83BD52C8 for ; Mon, 22 Oct 2012 07:50:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.FreeBSD.org [8.8.178.135]) by mx1.freebsd.org (Postfix) with ESMTP id 500DF8FC08 for ; Mon, 22 Oct 2012 07:50:01 +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 q9M7o18Z023933 for ; Mon, 22 Oct 2012 07:50:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q9M7o1J4023932; Mon, 22 Oct 2012 07:50:01 GMT (envelope-from gnats) Date: Mon, 22 Oct 2012 07:50:01 GMT Message-Id: <201210220750.q9M7o1J4023932@freefall.freebsd.org> To: freebsd-virtualization@FreeBSD.org Cc: From: =?ISO-8859-1?Q?Jean-S=E9bastien_P=E9dron?= Subject: Re: kern/152047: [vimage] [panic] TUN\TAP under jail with vimage crashes system X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: =?ISO-8859-1?Q?Jean-S=E9bastien_P=E9dron?= List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2012 07:50:01 -0000 The following reply was made to PR kern/152047; it has been noted by GNATS. From: =?ISO-8859-1?Q?Jean-S=E9bastien_P=E9dron?= To: bug-followup@FreeBSD.org, x86mail@gmail.com Cc: Subject: Re: kern/152047: [vimage] [panic] TUN\TAP under jail with vimage crashes system Date: Mon, 22 Oct 2012 09:45:29 +0200 I applied the patch to FreeNAS 8.3.0 RC1, based on FreeBSD 8.3-RELEASE-p4 and this fixes the problem for me. Thank you! -- Jean-Sébastien Pédron From owner-freebsd-virtualization@FreeBSD.ORG Mon Oct 22 11:06:42 2012 Return-Path: Delivered-To: freebsd-virtualization@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 46F7A2F0 for ; Mon, 22 Oct 2012 11:06:42 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.FreeBSD.org [8.8.178.135]) by mx1.freebsd.org (Postfix) with ESMTP id 2CDCD8FC19 for ; Mon, 22 Oct 2012 11:06:42 +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 q9MB6gfN044596 for ; Mon, 22 Oct 2012 11:06:42 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q9MB6fj6044594 for freebsd-virtualization@FreeBSD.org; Mon, 22 Oct 2012 11:06:41 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 22 Oct 2012 11:06:41 GMT Message-Id: <201210221106.q9MB6fj6044594@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-virtualization@FreeBSD.org Subject: Current problem reports assigned to freebsd-virtualization@FreeBSD.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2012 11:06:42 -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/170096 virtualization[vimage] Dynamically-attached network interface will c o kern/169991 virtualization[run] [vimage] panic after device plugged in o kern/165252 virtualization[vimage] [pf] [panic] kernel panics with VIMAGE and PF o kern/161094 virtualization[vimage] [pf] [panic] kernel panic with pf + VIMAGE wh o kern/160541 virtualization[vimage][pf][patch] panic: userret: Returning on td 0x o kern/160496 virtualization[vimage] [pf] [patch] kernel panic with pf + VIMAGE o kern/148155 virtualization[vimage] [pf] Kernel panic with PF/IPFilter + VIMAGE k a kern/147950 virtualization[vimage] [carp] VIMAGE + CARP = kernel crash s kern/143808 virtualization[pf] pf does not work inside jail a kern/141696 virtualization[rum] [vimage] [panic] rum(4)+ vimage = kernel panic 10 problems total. From owner-freebsd-virtualization@FreeBSD.ORG Fri Oct 26 03:16:59 2012 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 77B5F4FC; Fri, 26 Oct 2012 03:16:59 +0000 (UTC) (envelope-from neelnatu@gmail.com) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by mx1.freebsd.org (Postfix) with ESMTP id 29AC78FC14; Fri, 26 Oct 2012 03:16:58 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id k10so4178694iea.13 for ; Thu, 25 Oct 2012 20:16:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Ev8C6vtqvy1KSUGdmMbUfX2ypyOKVJ/Hj7yZLLl8o40=; b=TVrdLbnu0bFjRudCSIGaP9O6eLA7S99W70jP4p6ZV3lzJnkjCVc/rXtygqXBRwlHz8 4H7BzJxmzFFZ+K2EyZ2NA1KlpIeuHe0g0AymfxTOJA5XnO/D+9a5TOG0z/UP9Q54GB+Q eBB+f19DPrZmmT96wymKsqrJ7w7qA3iUcory77EjMH3GyBtZQBHTeZCKFmCsH79IEE/B CHF0XAdQ1Df0tbli9fo4HR03R08BOOKJJDCDjt3wQuJGwUUWwD7SoOr/CR2zLfeZDw8m KhPEVk8b84lor36AgKhFCCaDUKqOoFZpOoXIMKwRu0gQrBLBXjgXqYBsdpw5eTrUAD2S aKUg== MIME-Version: 1.0 Received: by 10.50.185.200 with SMTP id fe8mr718588igc.35.1351221418600; Thu, 25 Oct 2012 20:16:58 -0700 (PDT) Received: by 10.64.49.44 with HTTP; Thu, 25 Oct 2012 20:16:58 -0700 (PDT) In-Reply-To: References: Date: Thu, 25 Oct 2012 20:16:58 -0700 Message-ID: Subject: Re: Bhyve: panic: "Unregistered use of FPU in kernel" when starting guest From: Neel Natu To: "sree.openwrk" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Oct 2012 03:16:59 -0000 Hi svas, I just submitted a fix for this: http://svnweb.freebsd.org/base?view=revision&revision=242122 Please let me know if this fixes the panic you reported. best Neel On Sun, Oct 7, 2012 at 11:12 AM, sree.openwrk wrote: > Hey Neel > Sure. I will reproduce the issue and try to narrow down the problem. > Will update you, if I am able to narrow down the problem. > > Thanks > > > On Thu, Oct 4, 2012 at 9:07 PM, Neel Natu wrote: >> >> Hi svas, >> >> On Thu, Oct 4, 2012 at 5:58 PM, sree.openwrk >> wrote: >> > Hi >> > I am seeing frequent kernel panic when I try to run the guest OS. I have >> > the >> > latest Freebsd (I compiled the latest code from >> > svn://svn.freebsd.org/base/projects/bhyve and installed it in my >> > machine). >> > While trying to run the pre-built guest provided at >> > http://people.freebsd.org/~neel/bhyve/vm1.tar.gz I get the kernel panic >> > (panic: Unregistered use of FPU in kernel) >> > I am attaching the core.txt. >> > I also want to mention that I was successfully able to boot in to the >> > guest >> > OS couple of times. But around 7/10 times I get thsi host kernel panic. >> > >> > stack trace: >> > vm_run() at vm_run+0xec >> > vmmdev_ioctl() at vmmdev_ioctl+0x4ea >> > devfs_ioctl_f() at devfs_ioctl_f+0x7a >> > kern_ioctl() at kern_ioctl+0xcd >> > sys_ioctl() at sys_ioctl+0xfd >> > amd64_syscall() at amd64_syscall+0x304 >> > Xfast_syscall() at Xfast_syscall+0xf7 >> > >> >> I am seeing this too but nowhere as frequently as you are. I hit this >> last night for the first time and not since. >> >> There hasn't been any change in this part of the code for quite some time >> now. >> >> Since you can trigger this much more frequently that me, would it be >> possible for you to narrow down which change caused this? It would be >> hugely helpful. >> >> best >> Neel >> >> > >> > regards >> > svas >> > >> > > >