From owner-freebsd-virtualization@FreeBSD.ORG Mon Jul 16 11:09:36 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 D819B106566C for ; Mon, 16 Jul 2012 11:09:36 +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 C232A8FC19 for ; Mon, 16 Jul 2012 11:09:36 +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 q6GB9aam094190 for ; Mon, 16 Jul 2012 11:09:36 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q6GB9ZK8094188 for freebsd-virtualization@FreeBSD.org; Mon, 16 Jul 2012 11:09:35 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 16 Jul 2012 11:09:35 GMT Message-Id: <201207161109.q6GB9ZK8094188@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 Cc: Subject: Current problem reports assigned to freebsd-virtualization@FreeBSD.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Jul 2012 11:09:36 -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/167551 virtualization[vimage] Fatal trap 12 jails, vimage, ifconfig destroy 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 f kern/152047 virtualization[vimage] [panic] TUN\TAP under jail with vimage crashe 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 Wed Jul 18 04:12:50 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 A216C106564A for ; Wed, 18 Jul 2012 04:12:50 +0000 (UTC) (envelope-from sree.openwrk@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 51C718FC17 for ; Wed, 18 Jul 2012 04:12:50 +0000 (UTC) Received: by obbun3 with SMTP id un3so2021467obb.13 for ; Tue, 17 Jul 2012 21:12:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=nbEQFeNXsrERMr0USUPKd0VQ/0Gk6XUcYbOPZiKsx/I=; b=b99kl/eLXdxFEE8ZlwirnJ832bqaRkHOHzA/OAE57TRqzjxduc/QyuNNvMhneMn9oR 5nz4leJGzCxrYpEdO9LAJkHe6cDLOpUI4AhQ7TBX+lw9Fxt12H7tN5gaTG0MvZ4eCfWi IgMlwanx+71XFs5kaEsubGgFnUM4g7RA3sple6v3D+tZItIUgAQH2yK5im5t0Hr0nbDV ga09ax0bnUAHnvoAnSejqUTB4OniYj/gB6jSNxyqBtbykKjKqDX0+9CnggVNUSX+MumO GF1DVybn0YfULq7fIbIwYG5ULdex9K9gC98g0aVu0KbHYAtZglLMGsyNbzufbA12NG1K x6YQ== MIME-Version: 1.0 Received: by 10.182.232.101 with SMTP id tn5mr6995979obc.49.1342584769907; Tue, 17 Jul 2012 21:12:49 -0700 (PDT) Received: by 10.60.147.164 with HTTP; Tue, 17 Jul 2012 21:12:49 -0700 (PDT) Date: Tue, 17 Jul 2012 21:12:49 -0700 Message-ID: From: s vas To: freebsd-virtualization@freebsd.org Content-Type: multipart/mixed; boundary=f46d044517434a8bb904c512e0bb X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Bhyve - Host kernel panic after running 'kldload vmm' X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 18 Jul 2012 04:12:50 -0000 --f46d044517434a8bb904c512e0bb Content-Type: text/plain; charset=ISO-8859-1 Hi I have a kernel panic when loading bhyve hypervisor kernel module. These are the steps I followed 1. First I installed Freebsd 9 on my machine which has Intel-x86_64 and 8Gb Ram 2. The following output from dmesg.boot confirm that vmx is enabled in the machine. PU: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (2394.06-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x20655 Family = 6 Model = 25 Stepping = 5 Features=0xbfebfbff Features2=0x29ae3ff AMD Features=0x28100800 AMD Features2=0x1 TSC: P-state invariant, performance statistics 3. Then I checked out the latest code from svn:// svn.freebsd.org/base/projects/bhyve/ a) I built world and kernel b) Followed the steps in http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html (25.7.1 The Canonical Way to Update Your System) to install the new kernel and to install the new world. c) Rebooted to the newly built kernel. 4. I wanted to give 4gb to the host kernel and the remaining memory for the guest. So I set hw.physmem to "0x100000000". 5. Rebooted the host so that hw.physmem takes effect (Following http://people.freebsd.org/~neel/bhyve/bhyve_instructions.txt) a) This is the sysctl output sysctl -a | grep hw.physmem hw.physmem: 3185545216 cat /boot/loader.conf hw.physmem="0x100000000" 6. Then executed 'kldload vmm'. Got kernel panic with the following trace ----- #0 - #8 is panic related call trace.... ........ #9 0xffffffff8189b91f in vmx_enable (arg=Variable "arg" is not available. ) at vmx_cpufunc.h:65 #10 0xffffffff808b9e5d in smp_rendezvous_action () at /media/fbsd_part2/bhyve/bhyve/ sys/kern/subr_smp.c:381 #11 0xffffffff80b5f0c5 in Xrendezvous () at apic_vector.S:342 #12 0xffffffff80b58e86 in acpi_cpu_c1 () at /media/fbsd_part2/bhyve/bhyve/sys/amd64/acpica/acpi_machdep.c:97 #13 0xffffffff803467ce in acpi_cpu_idle () at /media/fbsd_part2/bhyve/bhyve/sys/dev/acpica/acpi_cpu.c:967 #14 0xffffffff80b622b5 in cpu_idle_acpi (busy=Variable "busy" is not available. ) at /media/fbsd_part2/bhyve/bhyve/sys/amd64/amd64/machdep.c:689 #15 0xffffffff80b64ab8 in cpu_idle (busy=0) at /media/fbsd_part2/bhyve/bhyve/sys/amd64/amd64/machdep.c:843 #16 0xffffffff8089ed21 in sched_idletd (dummy=Variable "dummy" is not available. ) at /media/fbsd_part2/bhyve/bhyve/sys/kern/sched_ule.c:2583 #17 0xffffffff80846835 in fork_exit ( callout=0xffffffff8089eae0 , arg=0x0, frame=0xffffff800023cc40) at /media/fbsd_part2/bhyve/bhyve/sys/kern/kern_fork.c:992 #18 0xffffffff80b5e55e in fork_trampoline () at /media/fbsd_part2/bhyve/bhyve/sys/amd64/amd64/exception.S:602 I am attaching herewith the text core as well as the info. Can someone tell me whats happening? --f46d044517434a8bb904c512e0bb-- From owner-freebsd-virtualization@FreeBSD.ORG Wed Jul 18 05:07: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 26366106564A for ; Wed, 18 Jul 2012 05:07:42 +0000 (UTC) (envelope-from neelnatu@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id D443D8FC0A for ; Wed, 18 Jul 2012 05:07:41 +0000 (UTC) Received: by yhfs35 with SMTP id s35so1419492yhf.13 for ; Tue, 17 Jul 2012 22:07:41 -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=PSFg5QvyJ0xw0bg2UI3JEq4dWHvxamQv2Nxr835wolg=; b=uiSCVDFxHKvgXt3r7DFhQU6mCQtvJZsojmDiHDkngFXBOennDyyvDOP8AYa0geV2NK T9btwBxqiBnTPWgeqU2XPGb2D72Zj32QDupGtkVnX+nSDiYASJJRgt4qj69xACrqAy2q rQzIVoTmPCQ3Zy/ztc0O+zxhW7Y5xLbAMtr/a+9CHCQDCuzcU8ZMlsYgMBl632xr5ngX tGaA7xYTPvt7MzoQmfzJYovox9Y6+0R7zeW5tkUnlqNlnszIBFeDYlFggwyoJfC9lBJx B9mwGNO+o1/ktNP2ETswoAhtPhzoNlCNKGlgCtpiNHn7NvGr58Rq8dFLt8205LY2B171 jnHA== MIME-Version: 1.0 Received: by 10.42.154.199 with SMTP id r7mr2909223icw.55.1342588060607; Tue, 17 Jul 2012 22:07:40 -0700 (PDT) Received: by 10.64.104.234 with HTTP; Tue, 17 Jul 2012 22:07:40 -0700 (PDT) In-Reply-To: References: Date: Tue, 17 Jul 2012 22:07:40 -0700 Message-ID: From: Neel Natu To: s vas Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-virtualization@freebsd.org Subject: Re: Bhyve - Host kernel panic after running 'kldload vmm' X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 18 Jul 2012 05:07:42 -0000 Hi, On Tue, Jul 17, 2012 at 9:12 PM, s vas wrote: > Hi > I have a kernel panic when loading bhyve hypervisor kernel module. > These are the steps I followed > 1. First I installed Freebsd 9 on my machine which has Intel-x86_64 and 8Gb > Ram > 2. The following output from dmesg.boot confirm that vmx is enabled in the > machine. > PU: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (2394.06-MHz K8-class > CPU) > Origin = "GenuineIntel" Id = 0x20655 Family = 6 Model = 25 Stepping = > 5 > > Features=0xbfebfbff > > Features2=0x29ae3ff > AMD Features=0x28100800 > AMD Features2=0x1 > TSC: P-state invariant, performance statistics > > 3. Then I checked out the latest code from svn:// > svn.freebsd.org/base/projects/bhyve/ > a) I built world and kernel > b) Followed the steps in > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html > (25.7.1 > The Canonical Way to Update Your System) to install the new kernel and to > install the new world. > c) Rebooted to the newly built kernel. > 4. I wanted to give 4gb to the host kernel and the remaining memory for the > guest. So I set hw.physmem to "0x100000000". > 5. Rebooted the host so that hw.physmem takes effect (Following > http://people.freebsd.org/~neel/bhyve/bhyve_instructions.txt) > a) This is the sysctl output > sysctl -a | grep hw.physmem > hw.physmem: 3185545216 > cat /boot/loader.conf > hw.physmem="0x100000000" > 6. Then executed 'kldload vmm'. Got kernel panic with the following trace > > ----- > #0 - #8 is panic related call trace.... > ........ Could you provide the stack frames above vmx_enable()? It is unclear from the subset of stack frames provided here as to what the cause of the panic is. best Neel > #9 0xffffffff8189b91f in vmx_enable (arg=Variable "arg" is not available. > ) at vmx_cpufunc.h:65 > #10 0xffffffff808b9e5d in smp_rendezvous_action () > at /media/fbsd_part2/bhyve/bhyve/ > sys/kern/subr_smp.c:381 > #11 0xffffffff80b5f0c5 in Xrendezvous () at apic_vector.S:342 > #12 0xffffffff80b58e86 in acpi_cpu_c1 () > at /media/fbsd_part2/bhyve/bhyve/sys/amd64/acpica/acpi_machdep.c:97 > #13 0xffffffff803467ce in acpi_cpu_idle () > at /media/fbsd_part2/bhyve/bhyve/sys/dev/acpica/acpi_cpu.c:967 > #14 0xffffffff80b622b5 in cpu_idle_acpi (busy=Variable "busy" is not > available. > ) > at /media/fbsd_part2/bhyve/bhyve/sys/amd64/amd64/machdep.c:689 > #15 0xffffffff80b64ab8 in cpu_idle (busy=0) > at /media/fbsd_part2/bhyve/bhyve/sys/amd64/amd64/machdep.c:843 > #16 0xffffffff8089ed21 in sched_idletd (dummy=Variable "dummy" is not > available. > ) > at /media/fbsd_part2/bhyve/bhyve/sys/kern/sched_ule.c:2583 > #17 0xffffffff80846835 in fork_exit ( > callout=0xffffffff8089eae0 , arg=0x0, > frame=0xffffff800023cc40) > at /media/fbsd_part2/bhyve/bhyve/sys/kern/kern_fork.c:992 > #18 0xffffffff80b5e55e in fork_trampoline () > at /media/fbsd_part2/bhyve/bhyve/sys/amd64/amd64/exception.S:602 > > I am attaching herewith the text core as well as the info. Can someone tell > me whats happening? > > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org" > From owner-freebsd-virtualization@FreeBSD.ORG Wed Jul 18 18:17:53 2012 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59E4E106566C for ; Wed, 18 Jul 2012 18:17:53 +0000 (UTC) (envelope-from sree.openwrk@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 195F08FC0A for ; Wed, 18 Jul 2012 18:17:53 +0000 (UTC) Received: by obbun3 with SMTP id un3so3267831obb.13 for ; Wed, 18 Jul 2012 11:17:52 -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=kWLPpMWmlWsEE99jIIzkTHVr8XU1RdEvP/elaSuQOZ0=; b=l07bJDKmFQBVT80rLlCwhTDRRz3y5DpNhQK/ah+OpeLTCI+xYBMwNL0XxaPML2ra6m w1Q926t2S/EyXIl/s8RqnYo7WeFH3TX16ST258QncLZfrTggs6LPc7naNcx2UgxCu93Z YoxPINEjBo3o4J4PlZ5BTkAGE9gNFovBojnKBSjHrD+QKFgPvQMCQeM2sjBMouhzodXu sbgm9B+pEmWlYrRp4URi8MzcQFEDy0K/bsRLJXWHT2162erditORQFGGZKKDgkZV7hHO bUiIgqmau4Lw3KcONe8nNtEAhPE/SCpd+N3Xo9M+NFb8Kk0ogUY9y1CYdDBb2FSjxD3+ mzuA== MIME-Version: 1.0 Received: by 10.182.17.42 with SMTP id l10mr2682724obd.52.1342635472548; Wed, 18 Jul 2012 11:17:52 -0700 (PDT) Received: by 10.60.147.164 with HTTP; Wed, 18 Jul 2012 11:17:52 -0700 (PDT) In-Reply-To: References: Date: Wed, 18 Jul 2012 11:17:52 -0700 Message-ID: From: "sree.openwrk" To: Neel Natu Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-virtualization@freebsd.org Subject: Re: Bhyve - Host kernel panic after running 'kldload vmm' X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 18 Jul 2012 18:17:53 -0000 Hey Neel Thanks for the immediate reply. I found that the BIOS did not have vm-x and vt-d enabled and luckily enabling them fixed the issue. Now I am able to load the vmm module and its not throwing any error as of now. Thanks On Tue, Jul 17, 2012 at 10:07 PM, Neel Natu wrote: > Hi, > > On Tue, Jul 17, 2012 at 9:12 PM, s vas wrote: > > Hi > > I have a kernel panic when loading bhyve hypervisor kernel module. > > These are the steps I followed > > 1. First I installed Freebsd 9 on my machine which has Intel-x86_64 and > 8Gb > > Ram > > 2. The following output from dmesg.boot confirm that vmx is enabled in > the > > machine. > > PU: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (2394.06-MHz K8-class > > CPU) > > Origin = "GenuineIntel" Id = 0x20655 Family = 6 Model = 25 > Stepping = > > 5 > > > > > Features=0xbfebfbff > > > > > Features2=0x29ae3ff > > AMD Features=0x28100800 > > AMD Features2=0x1 > > TSC: P-state invariant, performance statistics > > > > 3. Then I checked out the latest code from svn:// > > svn.freebsd.org/base/projects/bhyve/ > > a) I built world and kernel > > b) Followed the steps in > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html > > (25.7.1 > > The Canonical Way to Update Your System) to install the new kernel and to > > install the new world. > > c) Rebooted to the newly built kernel. > > 4. I wanted to give 4gb to the host kernel and the remaining memory for > the > > guest. So I set hw.physmem to "0x100000000". > > 5. Rebooted the host so that hw.physmem takes effect (Following > > http://people.freebsd.org/~neel/bhyve/bhyve_instructions.txt) > > a) This is the sysctl output > > sysctl -a | grep hw.physmem > > hw.physmem: 3185545216 > > cat /boot/loader.conf > > hw.physmem="0x100000000" > > 6. Then executed 'kldload vmm'. Got kernel panic with the following trace > > > > ----- > > #0 - #8 is panic related call trace.... > > ........ > > Could you provide the stack frames above vmx_enable()? > > It is unclear from the subset of stack frames provided here as to what > the cause of the panic is. > > best > Neel > > > #9 0xffffffff8189b91f in vmx_enable (arg=Variable "arg" is not > available. > > ) at vmx_cpufunc.h:65 > > #10 0xffffffff808b9e5d in smp_rendezvous_action () > > at /media/fbsd_part2/bhyve/bhyve/ > > sys/kern/subr_smp.c:381 > > #11 0xffffffff80b5f0c5 in Xrendezvous () at apic_vector.S:342 > > #12 0xffffffff80b58e86 in acpi_cpu_c1 () > > at /media/fbsd_part2/bhyve/bhyve/sys/amd64/acpica/acpi_machdep.c:97 > > #13 0xffffffff803467ce in acpi_cpu_idle () > > at /media/fbsd_part2/bhyve/bhyve/sys/dev/acpica/acpi_cpu.c:967 > > #14 0xffffffff80b622b5 in cpu_idle_acpi (busy=Variable "busy" is not > > available. > > ) > > at /media/fbsd_part2/bhyve/bhyve/sys/amd64/amd64/machdep.c:689 > > #15 0xffffffff80b64ab8 in cpu_idle (busy=0) > > at /media/fbsd_part2/bhyve/bhyve/sys/amd64/amd64/machdep.c:843 > > #16 0xffffffff8089ed21 in sched_idletd (dummy=Variable "dummy" is not > > available. > > ) > > at /media/fbsd_part2/bhyve/bhyve/sys/kern/sched_ule.c:2583 > > #17 0xffffffff80846835 in fork_exit ( > > callout=0xffffffff8089eae0 , arg=0x0, > > frame=0xffffff800023cc40) > > at /media/fbsd_part2/bhyve/bhyve/sys/kern/kern_fork.c:992 > > #18 0xffffffff80b5e55e in fork_trampoline () > > at /media/fbsd_part2/bhyve/bhyve/sys/amd64/amd64/exception.S:602 > > > > I am attaching herewith the text core as well as the info. Can someone > tell > > me whats happening? > > > > _______________________________________________ > > freebsd-virtualization@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscribe@freebsd.org" > > > From owner-freebsd-virtualization@FreeBSD.ORG Thu Jul 19 23:55:13 2012 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE74D106564A for ; Thu, 19 Jul 2012 23:55:13 +0000 (UTC) (envelope-from sree.openwrk@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 65A5A8FC14 for ; Thu, 19 Jul 2012 23:55:13 +0000 (UTC) Received: by obbun3 with SMTP id un3so5261680obb.13 for ; Thu, 19 Jul 2012 16:55:07 -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=iJMC6UaBbPyEBo6xKpxSlUkon5mjIYI18VKSgpSUQC0=; b=Wzg7npd1yVBHZcW15kyyrKsaqAmd3ml9vfMnkNvg5EUnOw9kgldzLbNvMo+Rwout3V Ap1m8fC9ZLZsPWODKuR1DlBHHXL4QzlImHz4QYSsXIZOe555yLdmM4QvUbguLGJnewph ahVuOatozyy1J/f7Rbk51A0QE7fCjbeFytTyaVfl7PSNNGrp39gizuNVYXp/ztj7dZb5 IwLwHIzeQGvUdpHRlfcQr4q1K4rp0EJedAvHPp/3y/Ac409b8TbTrPUdDvglOC4H1ZHS ON38dPzltPYMl1vWgHnP92E7PjQbSduaoCtcpyTxVxWMuDPmpHXVrzmgB3P/dmffKxsM j9Qg== MIME-Version: 1.0 Received: by 10.60.2.131 with SMTP id 3mr4258889oeu.59.1342742106852; Thu, 19 Jul 2012 16:55:06 -0700 (PDT) Received: by 10.60.147.164 with HTTP; Thu, 19 Jul 2012 16:55:06 -0700 (PDT) In-Reply-To: References: Date: Thu, 19 Jul 2012 16:55:06 -0700 Message-ID: From: "sree.openwrk" To: Neel Natu Content-Type: multipart/mixed; boundary=e89a8f643d9a4dcd2e04c5378234 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-virtualization@freebsd.org Subject: Re: Bhyve - Host kernel panic after running 'kldload vmm' X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 19 Jul 2012 23:55:13 -0000 --e89a8f643d9a4dcd2e04c5378234 Content-Type: text/plain; charset=ISO-8859-1 Hi I have hit another road block while trying to run the guest using bhyve. These are the steps I followed. I have used http://people.freebsd.org/~neel/bhyve/bhyve_instructions.txt as the reference for preparing and running guest. 1. As posted in my previous e-mail, I installed FreeBSD 9 and then checked out /projects/bhyve and installed the world and kernel from that. Later I am going to use the same kernel, (built from /projects/bhyve, thats used to update from Freebsd-9 to latest in /projects/bhyve) for the guest in step 9. Also the virtio kernel modules I use in step 9 are from the ones built from /projects/bhyve. 2. I have 8gb ram and I have set aside 4gb for the vms. sysctl -a | grep hw.physmem hw.physmem: 3185541120 3. I have successfully performed upto step 7 in http://people.freebsd.org/~neel/bhyve/bhyve_instructions.txt. 4. Skipped step 8, as I plan to use virtio built from the latest code from /projects/bhyve (As part of updating the host freebsd to the latest source in /projects/bhyve, as mentioned above, I also made the virtio modules.) 5. Created vm1 directory in /usr/share and created all its sub-directories and their contents. I copied only the mdroot file from http://people.freebsd.org/~neel/bhyve/vm1.tar.gz. (remember that I copied /boot/kernel (i.e. host kernel) as the guest kernel) 6. Then cd to /usr/share/vm1 and execute './vmrun.sh vm1'. After the freebsd boot loader prompy comes up for the guest, after I hit enter, I get segfaulted with core. I am attaching herewith the backtrace of the core. Also I am pasting below the loader.conf file witihn /usr/share/vm1/boot. Any idea what is happening? Also is there any easy way to configure and run the guest, after building the host kernel with bhyve hypervisor? loader.conf ------------------- kernel="/kernel" virtio_load="YES" if_vtnet_load="YES" virtio_pci_load="YES" virtio_blk_load="YES" kern.hz="100" hw.pci.enable_msix="0" hw.pci.honor_msi_blacklist="0" bootverbose="1" mfsroot_load="YES" mfsroot_type="mfs_root" mfsroot_name="mdroot" Thanks On Wed, Jul 18, 2012 at 11:17 AM, sree.openwrk wrote: > Hey Neel > Thanks for the immediate reply. > I found that the BIOS did not have vm-x and vt-d enabled and luckily > enabling them fixed the issue. > Now I am able to load the vmm module and its not throwing any error as of > now. > > Thanks > > > On Tue, Jul 17, 2012 at 10:07 PM, Neel Natu wrote: > >> Hi, >> >> On Tue, Jul 17, 2012 at 9:12 PM, s vas wrote: >> > Hi >> > I have a kernel panic when loading bhyve hypervisor kernel module. >> > These are the steps I followed >> > 1. First I installed Freebsd 9 on my machine which has Intel-x86_64 and >> 8Gb >> > Ram >> > 2. The following output from dmesg.boot confirm that vmx is enabled in >> the >> > machine. >> > PU: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (2394.06-MHz >> K8-class >> > CPU) >> > Origin = "GenuineIntel" Id = 0x20655 Family = 6 Model = 25 >> Stepping = >> > 5 >> > >> > >> Features=0xbfebfbff >> > >> > >> Features2=0x29ae3ff >> > AMD Features=0x28100800 >> > AMD Features2=0x1 >> > TSC: P-state invariant, performance statistics >> > >> > 3. Then I checked out the latest code from svn:// >> > svn.freebsd.org/base/projects/bhyve/ >> > a) I built world and kernel >> > b) Followed the steps in >> > >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html >> > (25.7.1 >> > The Canonical Way to Update Your System) to install the new kernel and >> to >> > install the new world. >> > c) Rebooted to the newly built kernel. >> > 4. I wanted to give 4gb to the host kernel and the remaining memory for >> the >> > guest. So I set hw.physmem to "0x100000000". >> > 5. Rebooted the host so that hw.physmem takes effect (Following >> > http://people.freebsd.org/~neel/bhyve/bhyve_instructions.txt) >> > a) This is the sysctl output >> > sysctl -a | grep hw.physmem >> > hw.physmem: 3185545216 >> > cat /boot/loader.conf >> > hw.physmem="0x100000000" >> > 6. Then executed 'kldload vmm'. Got kernel panic with the following >> trace >> > >> > ----- >> > #0 - #8 is panic related call trace.... >> > ........ >> >> Could you provide the stack frames above vmx_enable()? >> >> It is unclear from the subset of stack frames provided here as to what >> the cause of the panic is. >> >> best >> Neel >> >> > #9 0xffffffff8189b91f in vmx_enable (arg=Variable "arg" is not >> available. >> > ) at vmx_cpufunc.h:65 >> > #10 0xffffffff808b9e5d in smp_rendezvous_action () >> > at /media/fbsd_part2/bhyve/bhyve/ >> > sys/kern/subr_smp.c:381 >> > #11 0xffffffff80b5f0c5 in Xrendezvous () at apic_vector.S:342 >> > #12 0xffffffff80b58e86 in acpi_cpu_c1 () >> > at /media/fbsd_part2/bhyve/bhyve/sys/amd64/acpica/acpi_machdep.c:97 >> > #13 0xffffffff803467ce in acpi_cpu_idle () >> > at /media/fbsd_part2/bhyve/bhyve/sys/dev/acpica/acpi_cpu.c:967 >> > #14 0xffffffff80b622b5 in cpu_idle_acpi (busy=Variable "busy" is not >> > available. >> > ) >> > at /media/fbsd_part2/bhyve/bhyve/sys/amd64/amd64/machdep.c:689 >> > #15 0xffffffff80b64ab8 in cpu_idle (busy=0) >> > at /media/fbsd_part2/bhyve/bhyve/sys/amd64/amd64/machdep.c:843 >> > #16 0xffffffff8089ed21 in sched_idletd (dummy=Variable "dummy" is not >> > available. >> > ) >> > at /media/fbsd_part2/bhyve/bhyve/sys/kern/sched_ule.c:2583 >> > #17 0xffffffff80846835 in fork_exit ( >> > callout=0xffffffff8089eae0 , arg=0x0, >> > frame=0xffffff800023cc40) >> > at /media/fbsd_part2/bhyve/bhyve/sys/kern/kern_fork.c:992 >> > #18 0xffffffff80b5e55e in fork_trampoline () >> > at /media/fbsd_part2/bhyve/bhyve/sys/amd64/amd64/exception.S:602 >> > >> > I am attaching herewith the text core as well as the info. Can someone >> tell >> > me whats happening? >> > >> > _______________________________________________ >> > freebsd-virtualization@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >> > To unsubscribe, send any mail to " >> freebsd-virtualization-unsubscribe@freebsd.org" >> > >> > > --e89a8f643d9a4dcd2e04c5378234 Content-Type: text/plain; charset=US-ASCII; name="bhyveload_core_bt.txt" Content-Disposition: attachment; filename="bhyveload_core_bt.txt" Content-Transfer-Encoding: base64 X-Attachment-Id: f_h4uhua060 IzAgIDB4MDAwMDAwMDgzMTgxMzVhZiBpbiBmaWNsRXhlY0MgKCkgZnJvbSAvYm9vdC91c2VyYm9v dC5zbwojMSAgMHgwMDAwMDAwODMxODFiMWYxIGluIGZpY2xUaWNrICgpIGZyb20gL2Jvb3QvdXNl cmJvb3Quc28KIzIgIDB4MDAwMDAwMDgzMTgxMzVjMSBpbiBmaWNsRXhlY0MgKCkgZnJvbSAvYm9v dC91c2VyYm9vdC5zbwojMyAgMHgwMDAwMDAwODMxODA2YmU5IGluIGJmX3J1biAoKSBmcm9tIC9i b290L3VzZXJib290LnNvCiM0ICAweDAwMDAwMDA4MzE4MGJkNjggaW4gaW5jbHVkZSAoKSBmcm9t IC9ib290L3VzZXJib290LnNvCiM1ICAweDAwMDAwMDA4MzE4MGJmNWIgaW4gaW50ZXJhY3QgKCkg ZnJvbSAvYm9vdC91c2VyYm9vdC5zbwojNiAgMHgwMDAwMDAwODMxODBiYjM4IGluIGxvYWRlcl9t YWluICgpIGZyb20gL2Jvb3QvdXNlcmJvb3Quc28KIzcgIDB4MDAwMDAwMDAwMDQwMTYyMiBpbiA/ PyAoKQojOCAgMHgwMDAwMDAwMDAwNDAxMTRlIGluID8/ICgpCiM5ICAweDAwMDAwMDA4MDA2MWMw MDAgaW4gPz8gKCkKIzEwIDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQojMTEgMHgwMDAwMDAw MDAwMDAwMDAwIGluID8/ICgpCiMxMiAweDAwMDAwMDAwMDAwMDAwMDggaW4gPz8gKCkKIzEzIDB4 MDAwMDdmZmZmZmZmZGUxOCBpbiA/PyAoKQojMTQgMHgwMDAwN2ZmZmZmZmZkZTJjIGluID8/ICgp CiMxNSAweDAwMDA3ZmZmZmZmZmRlMmYgaW4gPz8gKCkKIzE2IDB4MDAwMDdmZmZmZmZmZGUzMyBp biA/PyAoKQojMTcgMHgwMDAwN2ZmZmZmZmZkZTM2IGluID8/ICgpCiMxOCAweDAwMDA3ZmZmZmZm ZmRlM2IgaW4gPz8gKCkKIzE5IDB4MDAwMDdmZmZmZmZmZGUzZSBpbiA/PyAoKQojMjAgMHgwMDAw N2ZmZmZmZmZkZTRkIGluID8/ICgpCiMyMSAweDAwMDAwMDAwMDAwMDAwMDAgaW4gPz8gKCkKIzIy IDB4MDAwMDdmZmZmZmZmZGU1MSBpbiA/PyAoKQojMjMgMHgwMDAwN2ZmZmZmZmZkZTVlIGluID8/ ICgpCiMyNCAweDAwMDA3ZmZmZmZmZmRlNjkgaW4gPz8gKCkKIzI1IDB4MDAwMDdmZmZmZmZmZGU3 ZSBpbiA/PyAoKQojMjYgMHgwMDAwN2ZmZmZmZmZkZTkyIGluID8/ICgpCiMyNyAweDAwMDA3ZmZm ZmZmZmRlZTkgaW4gPz8gKCkKIzI4IDB4MDAwMDdmZmZmZmZmZGVmYiBpbiA/PyAoKQojMjkgMHgw MDAwN2ZmZmZmZmZkZjBlIGluID8/ICgpCiMzMCAweDAwMDA3ZmZmZmZmZmRmMWIgaW4gPz8gKCkK IzMxIDB4MDAwMDdmZmZmZmZmZGYyNiBpbiA/PyAoKQojMzIgMHgwMDAwN2ZmZmZmZmZkZjMxIGlu ID8/ICgpCiMzMyAweDAwMDA3ZmZmZmZmZmRmM2IgaW4gPz8gKCkKIzM0IDB4MDAwMDdmZmZmZmZm ZGY1NSBpbiA/PyAoKQojMzUgMHgwMDAwN2ZmZmZmZmZkZjYxIGluID8/ICgpCiMzNiAweDAwMDAw MDAwMDAwMDAwMDAgaW4gPz8gKCkKIzM3IDB4MDAwMDAwMDAwMDAwMDAwMyBpbiA/PyAoKQojMzgg MHgwMDAwMDAwMDAwNDAwMDQwIGluID8/ICgpCiMzOSAweDAwMDAwMDAwMDAwMDAwMDQgaW4gPz8g KCkKIzQwIDB4MDAwMDAwMDAwMDAwMDAzOCBpbiA/PyAoKQojNDEgMHgwMDAwMDAwMDAwMDAwMDA1 IGluID8/ICgpCiM0MiAweDAwMDAwMDAwMDAwMDAwMDggaW4gPz8gKCkKIzQzIDB4MDAwMDAwMDAw MDAwMDAwNiBpbiA/PyAoKQojNDQgMHgwMDAwMDAwMDAwMDAxMDAwIGluID8/ICgpCiM0NSAweDAw MDAwMDAwMDAwMDAwMDggaW4gPz8gKCkKIzQ2IDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQoj NDcgMHgwMDAwMDAwMDAwMDAwMDA5IGluID8/ICgpCiM0OCAweDAwMDAwMDAwMDA0MDEwYzAgaW4g Pz8gKCkKIzQ5IDB4MDAwMDAwMDAwMDAwMDAwNyBpbiA/PyAoKQojNTAgMHgwMDAwMDAwODAwNjAy MDAwIGluID8/ICgpCiM1MSAweDAwMDAwMDAwMDAwMDAwMGYgaW4gPz8gKCkKIzUyIDxzaWduYWwg aGFuZGxlciBjYWxsZWQ+CiM1MyAweDAwMDAwMDAwMDAwMDAwMDAgaW4gPz8gKCkKUHJldmlvdXMg ZnJhbWUgaW5uZXIgdG8gdGhpcyBmcmFtZSAoY29ycnVwdCBzdGFjaz8pCg== --e89a8f643d9a4dcd2e04c5378234-- From owner-freebsd-virtualization@FreeBSD.ORG Fri Jul 20 18:09:49 2012 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B4591106564A for ; Fri, 20 Jul 2012 18:09:49 +0000 (UTC) (envelope-from sree.openwrk@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 611188FC12 for ; Fri, 20 Jul 2012 18:09:49 +0000 (UTC) Received: by yenl8 with SMTP id l8so5064898yen.13 for ; Fri, 20 Jul 2012 11:09:43 -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=ZwFJm2U8wCCpT6zwaumx0ZY2j4JIDgeNmtjFWgV7l1s=; b=b35E7Ppq8LYj/va+NHAdGUIWhO0zk7lOxfGQp1I3maIhC1CqhoFRHCUL/PI31GbLaq SeNpg3W0zisPULRJ9BWbFVeIrwd5ijYhEn+NzvVKOdlrWh9erA1Q3QvXUPPEraf8cZ9R Za8Mgv4w8M3kRP7Gm5hzri3w087XKlar8l76f97vOz8fwxGrPxPi569Pj/Pi30W5/hm3 xy4DdR+IcJhnfLz3aV4QNJJdSjGS7NAwGDshTxfURdFpK3QNgm1A3d0OXMtC8+ObEVRg 4GixU7x3zbQyADPDuQUokIQrSeeb/0FkJCCTJTzaQ8pTvNsnn49tay49viq3Bnb9WC1o Ineg== MIME-Version: 1.0 Received: by 10.60.7.8 with SMTP id f8mr8207678oea.47.1342807783036; Fri, 20 Jul 2012 11:09:43 -0700 (PDT) Received: by 10.60.147.164 with HTTP; Fri, 20 Jul 2012 11:09:42 -0700 (PDT) In-Reply-To: References: Date: Fri, 20 Jul 2012 11:09:42 -0700 Message-ID: From: "sree.openwrk" To: Neel Natu Content-Type: multipart/mixed; boundary=e89a8f2351f5e8d74a04c546ccdc X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-virtualization@freebsd.org Subject: Re: Bhyve - Host kernel panic after running 'kldload vmm' X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jul 2012 18:09:49 -0000 --e89a8f2351f5e8d74a04c546ccdc Content-Type: text/plain; charset=ISO-8859-1 I tried to use the prebuilt vm1.tar.gz from http://people.freebsd.org/~neel/bhyve/vm1.tar.gz. Rest of the steps are as described in my earlier e-mail thread. When I try to run the vm1, I get kernel panic. I am attaching herewith the backtrace for the kernel panic when I run the prebuilt vm1 (from Neel's home directory). On Thu, Jul 19, 2012 at 4:55 PM, sree.openwrk wrote: > Hi > I have hit another road block while trying to run the guest using bhyve. > These are the steps I followed. I have used > http://people.freebsd.org/~neel/bhyve/bhyve_instructions.txt as the > reference for preparing and running guest. > 1. As posted in my previous e-mail, I installed FreeBSD 9 and then checked > out /projects/bhyve and installed the world and kernel from that. Later I > am going to use the same kernel, (built from /projects/bhyve, thats used to > update from Freebsd-9 to latest in /projects/bhyve) for the guest in step > 9. Also the virtio kernel modules I use in step 9 are from the ones built > from /projects/bhyve. > 2. I have 8gb ram and I have set aside 4gb for the vms. > sysctl -a | grep hw.physmem > hw.physmem: 3185541120 > 3. I have successfully performed upto step 7 in > http://people.freebsd.org/~neel/bhyve/bhyve_instructions.txt. > 4. Skipped step 8, as I plan to use virtio built from the latest code from > /projects/bhyve (As part of updating the host freebsd to the latest source > in /projects/bhyve, as mentioned above, I also made the virtio modules.) > 5. Created vm1 directory in /usr/share and created all its sub-directories > and their contents. I copied only the mdroot file from > http://people.freebsd.org/~neel/bhyve/vm1.tar.gz. (remember that I copied > /boot/kernel (i.e. host kernel) as the guest kernel) > 6. Then cd to /usr/share/vm1 and execute './vmrun.sh vm1'. After the > freebsd boot loader prompy comes up for the guest, after I hit enter, I get > segfaulted with core. > > I am attaching herewith the backtrace of the core. Also I am pasting below > the loader.conf file witihn /usr/share/vm1/boot. Any idea what is > happening? Also is there any easy way to configure and run the guest, after > building the host kernel with bhyve hypervisor? > > loader.conf > ------------------- > kernel="/kernel" > virtio_load="YES" > if_vtnet_load="YES" > virtio_pci_load="YES" > virtio_blk_load="YES" > > kern.hz="100" > hw.pci.enable_msix="0" > hw.pci.honor_msi_blacklist="0" > bootverbose="1" > > mfsroot_load="YES" > mfsroot_type="mfs_root" > mfsroot_name="mdroot" > > Thanks > > > On Wed, Jul 18, 2012 at 11:17 AM, sree.openwrk wrote: > >> Hey Neel >> Thanks for the immediate reply. >> I found that the BIOS did not have vm-x and vt-d enabled and luckily >> enabling them fixed the issue. >> Now I am able to load the vmm module and its not throwing any error as of >> now. >> >> Thanks >> >> >> On Tue, Jul 17, 2012 at 10:07 PM, Neel Natu wrote: >> >>> Hi, >>> >>> On Tue, Jul 17, 2012 at 9:12 PM, s vas wrote: >>> > Hi >>> > I have a kernel panic when loading bhyve hypervisor kernel module. >>> > These are the steps I followed >>> > 1. First I installed Freebsd 9 on my machine which has Intel-x86_64 >>> and 8Gb >>> > Ram >>> > 2. The following output from dmesg.boot confirm that vmx is enabled >>> in the >>> > machine. >>> > PU: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (2394.06-MHz >>> K8-class >>> > CPU) >>> > Origin = "GenuineIntel" Id = 0x20655 Family = 6 Model = 25 >>> Stepping = >>> > 5 >>> > >>> > >>> Features=0xbfebfbff >>> > >>> > >>> Features2=0x29ae3ff >>> > AMD Features=0x28100800 >>> > AMD Features2=0x1 >>> > TSC: P-state invariant, performance statistics >>> > >>> > 3. Then I checked out the latest code from svn:// >>> > svn.freebsd.org/base/projects/bhyve/ >>> > a) I built world and kernel >>> > b) Followed the steps in >>> > >>> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html >>> > (25.7.1 >>> > The Canonical Way to Update Your System) to install the new kernel and >>> to >>> > install the new world. >>> > c) Rebooted to the newly built kernel. >>> > 4. I wanted to give 4gb to the host kernel and the remaining memory >>> for the >>> > guest. So I set hw.physmem to "0x100000000". >>> > 5. Rebooted the host so that hw.physmem takes effect (Following >>> > http://people.freebsd.org/~neel/bhyve/bhyve_instructions.txt) >>> > a) This is the sysctl output >>> > sysctl -a | grep hw.physmem >>> > hw.physmem: 3185545216 >>> > cat /boot/loader.conf >>> > hw.physmem="0x100000000" >>> > 6. Then executed 'kldload vmm'. Got kernel panic with the following >>> trace >>> > >>> > ----- >>> > #0 - #8 is panic related call trace.... >>> > ........ >>> >>> Could you provide the stack frames above vmx_enable()? >>> >>> It is unclear from the subset of stack frames provided here as to what >>> the cause of the panic is. >>> >>> best >>> Neel >>> >>> > #9 0xffffffff8189b91f in vmx_enable (arg=Variable "arg" is not >>> available. >>> > ) at vmx_cpufunc.h:65 >>> > #10 0xffffffff808b9e5d in smp_rendezvous_action () >>> > at /media/fbsd_part2/bhyve/bhyve/ >>> > sys/kern/subr_smp.c:381 >>> > #11 0xffffffff80b5f0c5 in Xrendezvous () at apic_vector.S:342 >>> > #12 0xffffffff80b58e86 in acpi_cpu_c1 () >>> > at /media/fbsd_part2/bhyve/bhyve/sys/amd64/acpica/acpi_machdep.c:97 >>> > #13 0xffffffff803467ce in acpi_cpu_idle () >>> > at /media/fbsd_part2/bhyve/bhyve/sys/dev/acpica/acpi_cpu.c:967 >>> > #14 0xffffffff80b622b5 in cpu_idle_acpi (busy=Variable "busy" is not >>> > available. >>> > ) >>> > at /media/fbsd_part2/bhyve/bhyve/sys/amd64/amd64/machdep.c:689 >>> > #15 0xffffffff80b64ab8 in cpu_idle (busy=0) >>> > at /media/fbsd_part2/bhyve/bhyve/sys/amd64/amd64/machdep.c:843 >>> > #16 0xffffffff8089ed21 in sched_idletd (dummy=Variable "dummy" is not >>> > available. >>> > ) >>> > at /media/fbsd_part2/bhyve/bhyve/sys/kern/sched_ule.c:2583 >>> > #17 0xffffffff80846835 in fork_exit ( >>> > callout=0xffffffff8089eae0 , arg=0x0, >>> > frame=0xffffff800023cc40) >>> > at /media/fbsd_part2/bhyve/bhyve/sys/kern/kern_fork.c:992 >>> > #18 0xffffffff80b5e55e in fork_trampoline () >>> > at /media/fbsd_part2/bhyve/bhyve/sys/amd64/amd64/exception.S:602 >>> > >>> > I am attaching herewith the text core as well as the info. Can someone >>> tell >>> > me whats happening? >>> > >>> > _______________________________________________ >>> > freebsd-virtualization@freebsd.org mailing list >>> > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >>> > To unsubscribe, send any mail to " >>> freebsd-virtualization-unsubscribe@freebsd.org" >>> > >>> >> >> > --e89a8f2351f5e8d74a04c546ccdc Content-Type: application/octet-stream; name="bt_core.1" Content-Disposition: attachment; filename="bt_core.1" Content-Transfer-Encoding: base64 X-Attachment-Id: f_h4vl2b6t1 IzAgIGRvYWR1bXAgKHRleHRkdW1wPTApIGF0IC9tZWRpYS9mYnNkX3BhcnQyL2JoeXZlL2JoeXZl L3N5cy9rZXJuL2tlcm5fc2h1dGRvd24uYzoyNjgKIzEgIDB4ZmZmZmZmZmY4MDMyZTk3MCBpbiBk Yl9kdW1wIChkdW1teT1WYXJpYWJsZSAiZHVtbXkiIGlzIG5vdCBhdmFpbGFibGUuCikgYXQgL21l ZGlhL2Zic2RfcGFydDIvYmh5dmUvYmh5dmUvc3lzL2RkYi9kYl9jb21tYW5kLmM6NTM4CiMyICAw eGZmZmZmZmZmODAzMmRmNjEgaW4gZGJfY29tbWFuZCAobGFzdF9jbWRwPTB4ZmZmZmZmZmY4MTFk MGVlMCwgY21kX3RhYmxlPVZhcmlhYmxlICJjbWRfdGFibGUiIGlzIG5vdCBhdmFpbGFibGUuCikg YXQgL21lZGlhL2Zic2RfcGFydDIvYmh5dmUvYmh5dmUvc3lzL2RkYi9kYl9jb21tYW5kLmM6NDQ5 CiMzICAweGZmZmZmZmZmODAzMmUxYjAgaW4gZGJfY29tbWFuZF9sb29wICgpIGF0IC9tZWRpYS9m YnNkX3BhcnQyL2JoeXZlL2JoeXZlL3N5cy9kZGIvZGJfY29tbWFuZC5jOjUwMgojNCAgMHhmZmZm ZmZmZjgwMzMwMzA5IGluIGRiX3RyYXAgKHR5cGU9VmFyaWFibGUgInR5cGUiIGlzIG5vdCBhdmFp bGFibGUuCikgYXQgL21lZGlhL2Zic2RfcGFydDIvYmh5dmUvYmh5dmUvc3lzL2RkYi9kYl9tYWlu LmM6MjMxCiM1ICAweGZmZmZmZmZmODA4YWRiOTggaW4ga2RiX3RyYXAgKHR5cGU9MywgY29kZT0w LCB0Zj0weGZmZmZmZjgwZDdhZjU1MDApIGF0IC9tZWRpYS9mYnNkX3BhcnQyL2JoeXZlL2JoeXZl L3N5cy9rZXJuL3N1YnJfa2RiLmM6NjU0CiM2ICAweGZmZmZmZmZmODBiNzNiOGQgaW4gdHJhcCAo ZnJhbWU9MHhmZmZmZmY4MGQ3YWY1NTAwKSBhdCAvbWVkaWEvZmJzZF9wYXJ0Mi9iaHl2ZS9iaHl2 ZS9zeXMvYW1kNjQvYW1kNjQvdHJhcC5jOjU3MwojNyAgMHhmZmZmZmZmZjgwYjVlMDMzIGluIGNh bGx0cmFwICgpIGF0IC9tZWRpYS9mYnNkX3BhcnQyL2JoeXZlL2JoeXZlL3N5cy9hbWQ2NC9hbWQ2 NC9leGNlcHRpb24uUzoyMjgKIzggIDB4ZmZmZmZmZmY4MDhhZDYxYiBpbiBrZGJfZW50ZXIgKHdo eT0weGZmZmZmZmZmODBkYzljZWEgInBhbmljIiwgbXNnPTB4ODAgPEFkZHJlc3MgMHg4MCBvdXQg b2YgYm91bmRzPikgYXQgY3B1ZnVuYy5oOjYzCiM5ICAweGZmZmZmZmZmODA4NzU3MzEgaW4gcGFu aWMgKGZtdD1WYXJpYWJsZSAiZm10IiBpcyBub3QgYXZhaWxhYmxlLgopIGF0IC9tZWRpYS9mYnNk X3BhcnQyL2JoeXZlL2JoeXZlL3N5cy9rZXJuL2tlcm5fc2h1dGRvd24uYzo2MzMKIzEwIDB4ZmZm ZmZmZmY4MGI3M2Y2NyBpbiB0cmFwIChmcmFtZT0weGZmZmZmZjgwZDdhZjVkMDApIGF0IC9tZWRp YS9mYnNkX3BhcnQyL2JoeXZlL2JoeXZlL3N5cy9hbWQ2NC9hbWQ2NC90cmFwLmM6NDYwCiMxMSAw eGZmZmZmZmZmODBiNWUwMzMgaW4gY2FsbHRyYXAgKCkgYXQgL21lZGlhL2Zic2RfcGFydDIvYmh5 dmUvYmh5dmUvc3lzL2FtZDY0L2FtZDY0L2V4Y2VwdGlvbi5TOjIyOAojMTIgMHhmZmZmZmZmZjgw YjVmM2UxIGluIGZwdXNhdmUgKGFkZHI9MHhmZmZmZmUwMDY1MDNkMDAwKSBhdCAvbWVkaWEvZmJz ZF9wYXJ0Mi9iaHl2ZS9iaHl2ZS9zeXMvYW1kNjQvYW1kNjQvZnB1LmM6MTYyCiMxMyAweGZmZmZm ZmZmODE4OTRmYWQgaW4gdm1fcnVuICh2bT0weGZmZmZmZTAwMDdkZGM4MDAsIHZtcnVuPTB4ZmZm ZmZlMDAwZDkxNTE0MCkKICAgIGF0IC9tZWRpYS9mYnNkX3BhcnQyL2JoeXZlL2JoeXZlL3N5cy9t b2R1bGVzL3ZtbS8uLi8uLi9hbWQ2NC92bW0vdm1tLmM6NTE4CiMxNCAweGZmZmZmZmZmODE4OTU3 ZTEgaW4gdm1tZGV2X2lvY3RsIChjZGV2PTB4MTAsIGNtZD0zMjI0NDAxNDA4LCBkYXRhPTB4ZmZm ZmZlMDAwZDkxNTE0MCAiIiwgZmZsYWc9VmFyaWFibGUgImZmbGFnIiBpcyBub3QgYXZhaWxhYmxl LgopCiAgICBhdCAvbWVkaWEvZmJzZF9wYXJ0Mi9iaHl2ZS9iaHl2ZS9zeXMvbW9kdWxlcy92bW0v Li4vLi4vYW1kNjQvdm1tL3ZtbV9kZXYuYzoyMTMKIzE1IDB4ZmZmZmZmZmY4MDc5MjNmYSBpbiBk ZXZmc19pb2N0bF9mIChmcD0weGZmZmZmZTAwNjc4NjY2NDAsIGNvbT0zMjI0NDAxNDA4LCBkYXRh PVZhcmlhYmxlICJkYXRhIiBpcyBub3QgYXZhaWxhYmxlLgopIGF0IC9tZWRpYS9mYnNkX3BhcnQy L2JoeXZlL2JoeXZlL3N5cy9mcy9kZXZmcy9kZXZmc192bm9wcy5jOjc1NwojMTYgMHhmZmZmZmZm ZjgwOGM3MmFkIGluIGtlcm5faW9jdGwgKHRkPVZhcmlhYmxlICJ0ZCIgaXMgbm90IGF2YWlsYWJs ZS4KKSBhdCBmaWxlLmg6Mjg3CiMxNyAweGZmZmZmZmZmODA4Yzc1NGQgaW4gc3lzX2lvY3RsICh0 ZD0weGZmZmZmZTAwMGQ1YmY0NjAsIHVhcD0weGZmZmZmZjgwZDdhZjViYjApIGF0IC9tZWRpYS9m YnNkX3BhcnQyL2JoeXZlL2JoeXZlL3N5cy9rZXJuL3N5c19nZW5lcmljLmM6NjkxCiMxOCAweGZm ZmZmZmZmODBiNzJhMTkgaW4gYW1kNjRfc3lzY2FsbCAodGQ9MHhmZmZmZmUwMDBkNWJmNDYwLCB0 cmFjZWQ9MCkgYXQgc3Vicl9zeXNjYWxsLmM6MTM1CiMxOSAweGZmZmZmZmZmODBiNWUzMTcgaW4g WGZhc3Rfc3lzY2FsbCAoKSBhdCAvbWVkaWEvZmJzZF9wYXJ0Mi9iaHl2ZS9iaHl2ZS9zeXMvYW1k NjQvYW1kNjQvZXhjZXB0aW9uLlM6Mzg3CiMyMCAweDAwMDAwMDA4MDBmNmI4Y2MgaW4gPz8gKCkK UHJldmlvdXMgZnJhbWUgaW5uZXIgdG8gdGhpcyBmcmFtZSAoY29ycnVwdCBzdGFjaz8pCgo= --e89a8f2351f5e8d74a04c546ccdc--