From owner-freebsd-emulation@FreeBSD.ORG Wed Jun 17 16:01:43 2009 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D6BF1065670 for ; Wed, 17 Jun 2009 16:01:43 +0000 (UTC) (envelope-from lwindschuh@googlemail.com) Received: from mail-pz0-f171.google.com (mail-pz0-f171.google.com [209.85.222.171]) by mx1.freebsd.org (Postfix) with ESMTP id 12F008FC18 for ; Wed, 17 Jun 2009 16:01:43 +0000 (UTC) (envelope-from lwindschuh@googlemail.com) Received: by pzk1 with SMTP id 1so445756pzk.3 for ; Wed, 17 Jun 2009 09:01:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=aYjQhHrNzt47R+1pzPIylqE1jyudpUAC5PJKmTrYj3s=; b=KKM3C4Mo5j7gNDFbZLLPfyMswlXui3M77Bm34eHeDNbXEpO3tuWfGwL1QGwZKTCiYT PZHi7GLCSDZBGQppsUvtAJb7tuwb46n0CWQTeYBPzFKAmCLGxQ+8DL1JO4gD+U73V4Jp eqtiwtIJATVi4Yu2Cueted3uqrnfFY75krsBQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=vOV1CChm/e1AdUOU3fRjhZTKMIBeYFNojW9h2ZbPrVejn2bdGak16rVba9kx0YnZUb 75WBFf/Y462DpTb5bjmWD4G/4Lw3qa3ySb7pk6gEj3V117GUjo+eSfPxuK0stBbh60e2 shBooYb2sSIDpbI4UBUNJJkrIz2yMH8Lt4tAE= MIME-Version: 1.0 Received: by 10.142.223.20 with SMTP id v20mr301472wfg.109.1245252776415; Wed, 17 Jun 2009 08:32:56 -0700 (PDT) In-Reply-To: <4A390797.3000102@voicenet.com> References: <4A383783.3010800@voicenet.com> <20090617093329.488f8f2f@ernst.jennejohn.org> <4A390797.3000102@voicenet.com> Date: Wed, 17 Jun 2009 17:32:56 +0200 Message-ID: <90a5caac0906170832v168542d1w3663bc0d238f2071@mail.gmail.com> From: Lucius Windschuh To: freebsd-emulation@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: kernel panic with VirtualBox on -CURRENT X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jun 2009 16:01:43 -0000 2009/6/17 Adam K Kirchhoff > Unfortunately, I do not see an option in this computers' BIOS to enable v= irtualization. =A0I'm actually trying on a machine at work now, rather than= the one I tried at home yesterday, but the results are the same. =A0This c= omputer actually has as an Intel Core 2 Quad CPU (unlike yesterdays dualcor= e Xeon). =A0Is there someway to check if the processors on these machines s= upport the virtualization extensions? > > I also am not able to disable the AMD-V option in VirtualBox. =A0The chec= k box is selected but greyed out. "Me too". Same panic on an Atom board (i386 mode). Same greyed out checkbox= es. Are you also using i386? If I remember correctly, VT-x / AMD-V only work on amd64, so VirtualBox shouldn't use them anyway in my case. And disabling VT-x in a machine's XML file leads to the same panic. Interestingly, it worked before with virtualbox_3.tgz. Lucius