From owner-freebsd-virtualization@FreeBSD.ORG Sun Jul 22 20:22:36 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 A083D106564A; Sun, 22 Jul 2012 20:22:36 +0000 (UTC) (envelope-from trociny@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8C5628FC0A; Sun, 22 Jul 2012 20:22: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 q6MKMaYn043776; Sun, 22 Jul 2012 20:22:36 GMT (envelope-from trociny@freefall.freebsd.org) Received: (from trociny@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q6MKMa09043772; Sun, 22 Jul 2012 20:22:36 GMT (envelope-from trociny) Date: Sun, 22 Jul 2012 20:22:36 GMT Message-Id: <201207222022.q6MKMa09043772@freefall.freebsd.org> To: exzzec@gmail.com, trociny@FreeBSD.org, freebsd-virtualization@FreeBSD.org, trociny@FreeBSD.org From: trociny@FreeBSD.org Cc: Subject: Re: kern/167551: [vimage] Fatal trap 12 jails, vimage, ifconfig destroy epair*a 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: Sun, 22 Jul 2012 20:22:36 -0000 Synopsis: [vimage] Fatal trap 12 jails, vimage, ifconfig destroy epair*a State-Changed-From-To: open->patched State-Changed-By: trociny State-Changed-When: Sun Jul 22 20:13:43 UTC 2012 State-Changed-Why: I believe r238309 fixes this. I am going to MFC after stable/9 unfreeze. This is not a critical because of the existing workaround, which is a good practice too: move both ends to the home vnet before destroying the epair. Responsible-Changed-From-To: freebsd-virtualization->trociny Responsible-Changed-By: trociny Responsible-Changed-When: Sun Jul 22 20:13:43 UTC 2012 Responsible-Changed-Why: I am going to MFC r238309 after stable/9 unfreeze. http://www.freebsd.org/cgi/query-pr.cgi?pr=167551 From owner-freebsd-virtualization@FreeBSD.ORG Sun Jul 22 20:41:42 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 A48051065670; Sun, 22 Jul 2012 20:41:42 +0000 (UTC) (envelope-from trociny@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 778AB8FC0C; Sun, 22 Jul 2012 20:41: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 q6MKfgc0057271; Sun, 22 Jul 2012 20:41:42 GMT (envelope-from trociny@freefall.freebsd.org) Received: (from trociny@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q6MKfg6U057267; Sun, 22 Jul 2012 20:41:42 GMT (envelope-from trociny) Date: Sun, 22 Jul 2012 20:41:42 GMT Message-Id: <201207222041.q6MKfg6U057267@freefall.freebsd.org> To: trociny@FreeBSD.org, freebsd-net@FreeBSD.org, freebsd-virtualization@FreeBSD.org From: trociny@FreeBSD.org Cc: Subject: Re: kern/169991: [if_run] [vimage] panic after device plugged in 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: Sun, 22 Jul 2012 20:41:42 -0000 Synopsis: [if_run] [vimage] panic after device plugged in Responsible-Changed-From-To: freebsd-net->freebsd-virtualization Responsible-Changed-By: trociny Responsible-Changed-When: Sun Jul 22 20:39:48 UTC 2012 Responsible-Changed-Why: VIMAGE related. http://www.freebsd.org/cgi/query-pr.cgi?pr=169991 From owner-freebsd-virtualization@FreeBSD.ORG Mon Jul 23 11:07:28 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 CFB731065689 for ; Mon, 23 Jul 2012 11:07:28 +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 B94BD8FC18 for ; Mon, 23 Jul 2012 11:07:28 +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 q6NB7SXp090197 for ; Mon, 23 Jul 2012 11:07:28 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q6NB7SKK090195 for freebsd-virtualization@FreeBSD.org; Mon, 23 Jul 2012 11:07:28 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 23 Jul 2012 11:07:28 GMT Message-Id: <201207231107.q6NB7SKK090195@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, 23 Jul 2012 11:07:28 -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/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 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 Mon Jul 23 22:00:20 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 A01701065676; Mon, 23 Jul 2012 22:00:20 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4F6378FC25; Mon, 23 Jul 2012 22:00:18 +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 q6NM0IiA078384; Mon, 23 Jul 2012 22:00:18 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q6NM0IqP078380; Mon, 23 Jul 2012 22:00:18 GMT (envelope-from linimon) Date: Mon, 23 Jul 2012 22:00:18 GMT Message-Id: <201207232200.q6NM0IqP078380@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-virtualization@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/170096: [vimage] Dynamically-attached network interface will crash with VIMAGE enabled kernel 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, 23 Jul 2012 22:00:20 -0000 Old Synopsis: Dyanamically-attached network interface will crash with VIMAGE enabled kernel New Synopsis: [vimage] Dynamically-attached network interface will crash with VIMAGE enabled kernel Responsible-Changed-From-To: freebsd-bugs->freebsd-virtualization Responsible-Changed-By: linimon Responsible-Changed-When: Mon Jul 23 22:00:00 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=170096 From owner-freebsd-virtualization@FreeBSD.ORG Tue Jul 24 04:55: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 CF743106566B; Tue, 24 Jul 2012 04:55:36 +0000 (UTC) (envelope-from takawata@init-main.com) Received: from sana.init-main.com (unknown [IPv6:2001:240:28::1]) by mx1.freebsd.org (Postfix) with ESMTP id 7BC8A8FC0C; Tue, 24 Jul 2012 04:55:36 +0000 (UTC) Received: from ns.init-main.com (localhost [127.0.0.1]) by sana.init-main.com (8.14.3/8.14.3) with ESMTP id q6O4sAdO084119; Tue, 24 Jul 2012 13:54:11 +0900 (JST) (envelope-from takawata@ns.init-main.com) Message-Id: <201207240454.q6O4sAdO084119@sana.init-main.com> To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-virtualization@FreeBSD.org In-reply-to: Your message of "Mon, 23 Jul 2012 21:40:09 GMT." <201207232140.q6NLe9Z8077186@freefall.freebsd.org> Date: Tue, 24 Jul 2012 13:54:10 +0900 From: Takanori Watanabe Cc: Subject: Re: kern/170096: Dyanamically-attached network interface will crash with VIMAGE enabled kernel 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: Tue, 24 Jul 2012 04:55:36 -0000 It is fixed with following patch, though some consideration needed with kernel module: Index: usb_process.c =================================================================== --- usb_process.c (revision 238557) +++ usb_process.c (working copy) @@ -55,6 +55,7 @@ #include #include #include +#include #if (__FreeBSD_version < 700000) #define thread_lock(td) mtx_lock_spin(&sched_lock) @@ -111,6 +112,9 @@ td = curthread; thread_lock(td); sched_prio(td, up->up_prio); +#ifdef VIMAGE + td->td_vnet = vnet0; +#endif thread_unlock(td); mtx_lock(up->up_mtx); === From owner-freebsd-virtualization@FreeBSD.ORG Tue Jul 24 05:00:23 2012 Return-Path: Delivered-To: freebsd-virtualization@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 68286106566B for ; Tue, 24 Jul 2012 05:00:22 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 413F18FC08 for ; Tue, 24 Jul 2012 05:00:22 +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 q6O50LmZ036250 for ; Tue, 24 Jul 2012 05:00:21 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q6O50L8m036249; Tue, 24 Jul 2012 05:00:21 GMT (envelope-from gnats) Date: Tue, 24 Jul 2012 05:00:21 GMT Message-Id: <201207240500.q6O50L8m036249@freefall.freebsd.org> To: freebsd-virtualization@FreeBSD.org From: Takanori Watanabe Cc: Subject: Re: kern/170096: Dyanamically-attached network interface will crash with VIMAGE enabled kernel X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Takanori Watanabe List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jul 2012 05:00:23 -0000 The following reply was made to PR kern/170096; it has been noted by GNATS. From: Takanori Watanabe To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-virtualization@FreeBSD.org Cc: Subject: Re: kern/170096: Dyanamically-attached network interface will crash with VIMAGE enabled kernel Date: Tue, 24 Jul 2012 13:54:10 +0900 It is fixed with following patch, though some consideration needed with kernel module: Index: usb_process.c =================================================================== --- usb_process.c (revision 238557) +++ usb_process.c (working copy) @@ -55,6 +55,7 @@ #include #include #include +#include #if (__FreeBSD_version < 700000) #define thread_lock(td) mtx_lock_spin(&sched_lock) @@ -111,6 +112,9 @@ td = curthread; thread_lock(td); sched_prio(td, up->up_prio); +#ifdef VIMAGE + td->td_vnet = vnet0; +#endif thread_unlock(td); mtx_lock(up->up_mtx); === From owner-freebsd-virtualization@FreeBSD.ORG Tue Jul 24 12:06:43 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 968B4106566C for ; Tue, 24 Jul 2012 12:06:43 +0000 (UTC) (envelope-from noreply@sca.com.au) Received: from smtphw01.hostworks.net.au (smtphw01.hostworks.net.au [202.58.32.4]) by mx1.freebsd.org (Postfix) with ESMTP id 4FFC48FC1D for ; Tue, 24 Jul 2012 12:06:43 +0000 (UTC) Received: from scaprweb11.unix.local (unknown [10.20.23.31]) by smtphw01.hostworks.net.au (Postfix1d) with ESMTP id 2418069004A for ; Tue, 24 Jul 2012 21:47:13 +1000 (EST) Received: from scaprweb11.unix.local (localhost.localdomain [127.0.0.1]) by scaprweb11.unix.local (8.13.8/8.13.8) with ESMTP id q6OBlC04017823 for ; Tue, 24 Jul 2012 21:47:12 +1000 Received: (from apache@localhost) by scaprweb11.unix.local (8.13.8/8.13.8/Submit) id q6OBlCQA017807; Tue, 24 Jul 2012 21:47:12 +1000 Date: Tue, 24 Jul 2012 21:47:12 +1000 Message-Id: <201207241147.q6OBlCQA017807@scaprweb11.unix.local> To: freebsd-virtualization@freebsd.org X-PHP-Originating-Script: 502:.lindex.php From: Ms@scaprweb11.unix.local, Julie.Booker@scaprweb11.unix.local, Publishing Manager MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit Subject: Invitation to the Grand Suite Hotel Employment Opportunity Canada X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: grandsuiteshotels_canada@yahoo.ca List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jul 2012 12:06:43 -0000 JOB VACANCY IN CANADA GRAND SUITES HOTELS. Sir / Madam, Due to the expansion in our services and the opening of new outlets the hotel needs 1 to 15 men and females workers to fill in different categories of job openings. Grand suites Hotels Management is using this Media to announce to public that we have some jobs offers in the hotel. If you' re a good Sous-chefs / Lobby agents / Accounting clerks / Waiters / House-Keepers / Event Coordinators / Sales Managers / Bartenders / Maintenance Staff / Banquet Servers / Stewards / Software & Hardware Support Services and others jobs you can apply for any suitable post that you can be perfect in handling. At Grand suites Hotels, a huge variety of professions exists under one roof, creating the utmost chance for mobility and growth in your career. We value our employees as our most essential resource. If you wish to make an application to join our professional team at Grand suites Hotels, we invite you to contact us back with your information's. IE: (CV) in micro word. When submitting your application Letter, be as specific as possible about which positions are of interest to you. The hotel shall be responsible for Air Ticket and accommodation only. If you are interested contact us with your C.V via our e mail address. We can only reply you through our e mail address. E mail: grandsuiteshotels_canada@yahoo.ca Regards, Julie Booker. Publishing Manager From owner-freebsd-virtualization@FreeBSD.ORG Wed Jul 25 00:25:38 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 4FBEB1065670 for ; Wed, 25 Jul 2012 00:25:38 +0000 (UTC) (envelope-from neelnatu@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 122448FC12 for ; Wed, 25 Jul 2012 00:25:38 +0000 (UTC) Received: by obbun3 with SMTP id un3so300166obb.13 for ; Tue, 24 Jul 2012 17:25:37 -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=FYJyxChNTinJtHvfZOz5x3J7yanXRQoaRKJB0lBUKN8=; b=im8nuUHccf08hM3Hnegey/5ADvwmMaliXR4zbQJN2uGvKs+UpTt526D5ICyZXCa0Pk HFFgL2dXWUObjGun/AcZIAkcEf0mFvDiibpo1o8n1FaycWTg2bWx581jQ3AYUplmjtx3 GLsVvPJ0tx5HRFh8T4Q38fO2tJoevb2tRexbzWWa4dEGdVWkxRkILwzxWBgxZHRtULvO LKip9S+WSmARbUPalLkxvfhVQl7VsYHkKecMFv16/gKjAJqx/eg9CgwIRWdP3Z24Zkc0 k/QxuQsEoByi6dKF+A+W78CyjFFYjnf2ftjhgeG+Fdg3a+MhqvQ9Ye1JsMcYbnK/LdvE u9xQ== MIME-Version: 1.0 Received: by 10.182.167.101 with SMTP id zn5mr31414735obb.60.1343175937579; Tue, 24 Jul 2012 17:25:37 -0700 (PDT) Received: by 10.64.104.234 with HTTP; Tue, 24 Jul 2012 17:25:37 -0700 (PDT) In-Reply-To: References: Date: Tue, 24 Jul 2012 17:25:37 -0700 Message-ID: From: Neel Natu To: "sree.openwrk" 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, 25 Jul 2012 00:25:38 -0000 Hi, 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. > Also fixed in the projects/bhyve now: http://svnweb.freebsd.org/base?view=revision&revision=238758 best Neel > 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" >> > > >