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" > > >