From owner-freebsd-virtualization@FreeBSD.ORG Mon Apr 16 07:08:33 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 C0FE6106564A; Mon, 16 Apr 2012 07:08:33 +0000 (UTC) (envelope-from crodr001@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 6B6728FC08; Mon, 16 Apr 2012 07:08:33 +0000 (UTC) Received: by obqv19 with SMTP id v19so5997803obq.13 for ; Mon, 16 Apr 2012 00:08:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=OLleCgMxDtdhK7hLoo4fwKcniWLnrhtoZ0T+br7Fsi4=; b=HV7nuAA06K35yavCT/TYZxRUWI0fyD951o/H+0DzUCJIRTq1yt6P8gdCMxQ/B27ZQo aLGHlBo5j0LTk3CP0ei2NsMeebFtwvc4XpzG0LPLWAMxHG4KsGDHaEVoENNf+ya6haG9 wHZwUX3LQbb49GpLj96lVzx4JXUrLU9vuK5rhEM1JBmqJdNN7Uu64sSl1j/ZdUecnq8z kH7BMWjHEGSGDWYJlfcBuQLLI9Q+bkBt3iojLbB3jVk/Phl6SW4ij/kT07pGrLooWkZd 3KMYJetw6JHTu/S/xRRZK5nx9IZatmKVvKiWxBAYVbkIs3Kktf21+Y1NVdUlUPyXv0r0 G/ag== MIME-Version: 1.0 Received: by 10.60.170.145 with SMTP id am17mr14601200oec.73.1334560113008; Mon, 16 Apr 2012 00:08:33 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.182.142.65 with HTTP; Mon, 16 Apr 2012 00:08:32 -0700 (PDT) Date: Mon, 16 Apr 2012 00:08:32 -0700 X-Google-Sender-Auth: st3mhr5uO22b_vXgwjLaNviTpWc Message-ID: From: Craig Rodrigues To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-emulation@freebsd.org, freebsd-stable@freebsd.org Subject: VirtualBox problem booting FreeBSD-9.0-RELEASE-amd64-bootonly.iso 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 Apr 2012 07:08:33 -0000 Hi, I am trying to run FreeBSD-9.0-RELEASE-amd64-bootonly.iso inside VirtualBox and am having some problems. The error messages I am getting are similar to the ones mentioned here: http://lists.freebsd.org/pipermail/freebsd-stable/2011-December/065079.html My host environment =================== Operating System: Windows 7, home edition, 64-bit VirtualBox for Windows, version 4.1.12 r77245 CPU Information ================ I downloaded the CoreInfo.exe utility which is part of Windows Sysinternals utilities ( http://technet.microsoft.com/en-us/sysinternals/bb545027 ) According to this utility, my CPU is: ============================================================ Intel(R) Core(TM)2 Duo CPU T5450 @ 1.66GHz Intel64 Family 6 Model 15 Stepping 13, GenuineIntel HTT * Hyperthreading enabled HYPERVISOR - Hypervisor is present VMX - Supports Intel hardware-assisted virtualization SVM - Supports AMD hardware-assisted virtualization EM64T * Supports 64-bit mode ============================================================ So my CPU support 64-bit mode, but does not support hardware-assisted virtualization. Error message ============= If I try to mount and then boot it under VirtualBox, I get this error: CPU doesn't support long mode Consoles: internal video/keyboard BIOS drive C: is disk0 BIOS 639kB/523264kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 (root@farrell.cse.buffalo.edu, Tue Jan 3 06:51:49 UTC 2012) Can't work out which disk we are booting from. Guess BIOS device 0xffffffff not found by probes, defaulting to disk0: FATAL: int13_harddisk: function 42. Can't use 64bits lba Does anyone know how to fix this problem in VirtualBox? QEMU for Windows ================ Just to try something else, I downloaded QEMU 0.9.0 for Windows from: http://www.h7.dion.ne.jp/~qemu-win/ I extracted the zip file into a directory: C:\local\qemu-0.9.0-windows I then ran: cd c:\local\qemu-0.9.0-windows qemu-system-x86_64.exe -L . -m 128 -cdrom c:\temp\FreeBSD-9.0-RELEASE-amd64-bootonly.iso The ISO booted up just fine. From the dmesg output, this was the emulated CPU: CPU: QEMU Virtual CPU version 0.9.0 (1666.98-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x623 Family = 6 Model = 2 Stepping = 3 Features=0x78bfbfd Features2=0x1 AMD Features=0x20100800 Does anyone know how I can get VirtualBox to behave the same way as QEMU for FreeBSD-9.0-RELEASE-amd64-bootonly.iso? Thanks. -- Craig Rodrigues rodrigc@crodrigues.org From owner-freebsd-virtualization@FreeBSD.ORG Mon Apr 16 07:23:52 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 8F0FC1065673; Mon, 16 Apr 2012 07:23:52 +0000 (UTC) (envelope-from decke@FreeBSD.org) Received: from groupware.itac.at (groupware.itac.at [91.205.172.99]) by mx1.freebsd.org (Postfix) with ESMTP id 242158FC0A; Mon, 16 Apr 2012 07:23:52 +0000 (UTC) Received: from home.bluelife.at (93.104.210.95) by groupware.itac.at (Axigen) with (AES256-SHA encrypted) ESMTPSA id 34A461; Mon, 16 Apr 2012 09:23:54 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 16 Apr 2012 09:23:44 +0200 From: Bernhard Froehlich To: Craig Rodrigues In-Reply-To: References: Message-ID: X-Sender: decke@FreeBSD.org User-Agent: Roundcube Webmail/0.7.2 X-AxigenSpam-Level: 1 X-CTCH-RefID: str=0001.0A0B0205.4F8BC901.004A,ss=1,fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown Cc: freebsd-emulation@freebsd.org, freebsd-stable@freebsd.org, freebsd-virtualization@freebsd.org Subject: Re: VirtualBox problem booting FreeBSD-9.0-RELEASE-amd64-bootonly.iso 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 Apr 2012 07:23:52 -0000 On 16.04.2012 09:08, Craig Rodrigues wrote: > Hi, > > I am trying to run FreeBSD-9.0-RELEASE-amd64-bootonly.iso > inside VirtualBox and am having some problems. > > The error messages I am getting are similar to the ones mentioned > here: > > > http://lists.freebsd.org/pipermail/freebsd-stable/2011-December/065079.html > > [snip] > > Error message > ============= > If I try to mount and then boot it under VirtualBox, I get this > error: > > CPU doesn't support long mode > > Consoles: internal video/keyboard > BIOS drive C: is disk0 > BIOS 639kB/523264kB available memory > > FreeBSD/x86 bootstrap loader, Revision 1.1 > (root@farrell.cse.buffalo.edu, Tue Jan 3 06:51:49 UTC 2012) > Can't work out which disk we are booting from. > Guess BIOS device 0xffffffff not found by probes, defaulting to > disk0: > FATAL: int13_harddisk: function 42. Can't use 64bits lba Please create a new VM with preset Operating System "BSD" and Version "FreeBSD (64 bit)". -- Bernhard Froehlich http://www.bluelife.at/ From owner-freebsd-virtualization@FreeBSD.ORG Mon Apr 16 11:07:31 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 19D49106567F for ; Mon, 16 Apr 2012 11:07:31 +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 0324F8FC0A for ; Mon, 16 Apr 2012 11:07:31 +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 q3GB7UY4022566 for ; Mon, 16 Apr 2012 11:07:30 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3GB7UR9022564 for freebsd-virtualization@FreeBSD.org; Mon, 16 Apr 2012 11:07:30 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 16 Apr 2012 11:07:30 GMT Message-Id: <201204161107.q3GB7UR9022564@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 Apr 2012 11:07:31 -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/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/158686 virtualization[vimage] [tap] [patch] Add VIMAGE support to if_tap a 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 Tue Apr 17 03:30:02 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 94C4B106566C; Tue, 17 Apr 2012 03:30:02 +0000 (UTC) (envelope-from crodr001@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 365838FC0A; Tue, 17 Apr 2012 03:30:02 +0000 (UTC) Received: by obqv19 with SMTP id v19so7591550obq.13 for ; Mon, 16 Apr 2012 20:30:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=swbWpc1xfz/3+Y/e43+OqUQCYNUqlSDvw9768HqfseE=; b=b+gYMw8NKD20+83P/wvVsdImgRLPMgi13Bd9w6YUvFcYqFd18pmnI5WbSCvTzm0nfE 6dVB/Sa4iDLhZuCH+LARfeSHQQ225hOW1wRIZzjhfe85LWLKgtDVCektXIFxC7OHmXCR t2UG4WVEggCuyl/hKF8aBf+RcK2sgeflb+6FAFrCzVJaeR/zGmYE90tmDeChOxQb2OXW D5qixosAYmDs9ej3PIODFdBHYGJbWhD4Ryu71EJNWyK/Cm5gt+5UZ6+QYzvfATxfR3pp vm5hV/EDBDsydFKoFTOGXbLFuDnp9Zgm01xQ814cmyAeYs2QAD1A6VUYwgH9IEOeHkpX X3lQ== MIME-Version: 1.0 Received: by 10.60.20.3 with SMTP id j3mr19995063oee.43.1334633401808; Mon, 16 Apr 2012 20:30:01 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.182.142.65 with HTTP; Mon, 16 Apr 2012 20:30:01 -0700 (PDT) In-Reply-To: References: Date: Mon, 16 Apr 2012 20:30:01 -0700 X-Google-Sender-Auth: xDA0KqvDHDgu7W5d0GwyfL_370Y Message-ID: From: Craig Rodrigues To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-emulation@freebsd.org, freebsd-stable@freebsd.org Subject: Re: VirtualBox problem booting FreeBSD-9.0-RELEASE-amd64-bootonly.iso 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, 17 Apr 2012 03:30:02 -0000 On Mon, Apr 16, 2012 at 12:08 AM, Craig Rodrigues wrote: > My host environment > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > Operating System: Windows 7, home edition, 64-bit > VirtualBox for Windows, version 4.1.12 r77245 > > CPU Information > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > I downloaded the CoreInfo.exe utility which is part of Windows > Sysinternals utilities > ( http://technet.microsoft.com/en-us/sysinternals/bb545027 ) > > According to this utility, my CPU is: > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > =A0 =A0Intel(R) Core(TM)2 Duo CPU =A0 =A0 T5450 =A0@ 1.66GHz > =A0 =A0Intel64 Family 6 Model 15 Stepping 13, GenuineIntel > =A0 =A0HTT =A0 =A0 =A0 =A0 * =A0 =A0 =A0 Hyperthreading enabled > =A0 =A0HYPERVISOR =A0- =A0 =A0 =A0 Hypervisor is present > =A0 =A0VMX =A0 =A0 =A0 =A0 - =A0 =A0 =A0 Supports Intel hardware-assisted= virtualization > =A0 =A0SVM =A0 =A0 =A0 =A0 - =A0 =A0 =A0 Supports AMD hardware-assisted v= irtualization > =A0 =A0EM64T =A0 =A0 =A0 * =A0 =A0 =A0 Supports 64-bit mode > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > So my CPU support 64-bit mode, but does not support hardware-assisted > virtualization. > > > > Error message > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > If I try to mount and then boot it under VirtualBox, I get this error: > > =A0 CPU doesn't support long mode > > =A0 Consoles: internal video/keyboard > =A0 BIOS drive C: is disk0 > =A0 BIOS 639kB/523264kB available memory > > =A0 FreeBSD/x86 bootstrap loader, Revision 1.1 > =A0 (root@farrell.cse.buffalo.edu, Tue Jan =A03 06:51:49 UTC 2012) > =A0 Can't work out which disk we are booting from. > =A0 Guess BIOS device 0xffffffff not found by probes, defaulting to disk0= : > =A0 FATAL: int13_harddisk: function 42. Can't use 64bits lba > > > > Does anyone know how to fix this problem in VirtualBox? Hi, After exchanging a few e-mails with Bernard, I think I understand the probl= em. According to the VirtualBox manual: http://www.virtualbox.org/manual/ch03.html#intro-64bitguests The CPU needs to support hardware-assisted virtualization in order for VirtualBox to support 64-bit guests. Without the CPU support, VirtualBox cannot do it. I double checked this with CoreInfo.exe from Windows Sysinternals utilities, and also from the Intel data sheet for my CPU: http://ark.intel.com/products/30787 (VT-x option not supported) I will use QEMU under Windows until I can get a better machine. :) -- Craig Rodrigues rodrigc@crodrigues.org --=20 Craig Rodrigues rodrigc@crodrigues.org From owner-freebsd-virtualization@FreeBSD.ORG Tue Apr 17 04:29:12 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 BB47A106564A; Tue, 17 Apr 2012 04:29:12 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id E08D78FC0C; Tue, 17 Apr 2012 04:29:11 +0000 (UTC) Received: by wern13 with SMTP id n13so4954343wer.13 for ; Mon, 16 Apr 2012 21:29:10 -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=pWyFLDqYzfCxgBPRKnhUCEUBh58ApsnR/HXuBY718lg=; b=SeNYS1NeJtcfJL1546ViRluYicuvc83qBfCNqZ8wInSIM7tF4uBZKCXxgvjpy6vpce CUrQBj1LR8mDqSyhujBHIRQLQic0avpzhfO6F9aA5tRZE4+ahMFCrdE4bkdRgLF0rMSL FP9l7uphFG+fGU6iwxntvhIgAlv5FXWIzzpWX7fhqXZlw8F8sbxMQfYDlyhz03JUDa1J 7jptdf0CgOuU53ijDB3EFu3h9lOetZ72zGk2G2AP8KJmKQlKw7b7vVVQpiWdxAtBhAxh ZLRD1BIQCQG9IHUzDJZZ1l1nF9B4b9mC1rSL8T3M/Qnt6/1FdGvlIbFbKal3PCh8p/GT tvng== MIME-Version: 1.0 Received: by 10.180.76.240 with SMTP id n16mr24596545wiw.10.1334636950781; Mon, 16 Apr 2012 21:29:10 -0700 (PDT) Received: by 10.223.94.73 with HTTP; Mon, 16 Apr 2012 21:29:10 -0700 (PDT) In-Reply-To: References: Date: Mon, 16 Apr 2012 23:29:10 -0500 Message-ID: From: Adam Vande More To: Craig Rodrigues Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-emulation@freebsd.org, freebsd-stable@freebsd.org, freebsd-virtualization@freebsd.org Subject: Re: VirtualBox problem booting FreeBSD-9.0-RELEASE-amd64-bootonly.iso 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, 17 Apr 2012 04:29:12 -0000 On Mon, Apr 16, 2012 at 10:30 PM, Craig Rodrigues wrote: > After exchanging a few e-mails with Bernard, I think I understand the > problem. > According to the VirtualBox manual: > > http://www.virtualbox.org/manual/ch03.html#intro-64bitguests > > The CPU needs to support hardware-assisted virtualization in order for > VirtualBox to support 64-bit guests. > Without the CPU support, VirtualBox cannot do it. I double checked > this with CoreInfo.exe from Windows Sysinternals utilities, > and also from the Intel data sheet for my CPU: > > http://ark.intel.com/products/30787 > (VT-x option not supported) > > > I will use QEMU under Windows until I can get a better machine. :) > I believe a Windows 7 product key will activate either 32 or 64 install, so unless you have a specific reason to install 64 bit then you are likely better using 32 anyway. 32 bit OS's and apps use less memory than their corresponding 64 bit counterparts. -- Adam Vande More From owner-freebsd-virtualization@FreeBSD.ORG Tue Apr 17 22:19:04 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 3FEE7106564A; Tue, 17 Apr 2012 22:19:04 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id C40078FC1A; Tue, 17 Apr 2012 22:19:03 +0000 (UTC) Received: by ggnk4 with SMTP id k4so4106293ggn.13 for ; Tue, 17 Apr 2012 15:19:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=D6f0TVu/n6E7hCKVeme+5mcFvnLC9OtYhOyHZ8q77+4=; b=K1p7WVIMZXYTO8OR7OBJHsNq0gSyf0jFkm9oUEkZug7LjoMoGsIcqwG03j3TfprA26 kkypNsNsTLBHgSRh3oEvARa5djpVOUN6dpC0CPG/ZcVAM3upm1UltT3IjNCJF5snAPfl SXiQlwfKGQ0F3SFn3Bg3TZ5O09CYbTf/fSZpMMa3eHfema1BDchCxgEFnqHOMpBPe30C sN7DVsJnx8wiPA1DrNo6HvY5PELPLcyKV8Ad+Pr3REoSVAqFX5u4Z/abAshyDS9t353V fX3OJ3I0OvqTkVkDcjF5STFYvBn4calBs09LoRAo2iTTfW+KPWWpZK4PU4NWYxqF4ptE sZdg== MIME-Version: 1.0 Received: by 10.60.20.3 with SMTP id j3mr24882354oee.43.1334701143005; Tue, 17 Apr 2012 15:19:03 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.182.142.65 with HTTP; Tue, 17 Apr 2012 15:19:02 -0700 (PDT) In-Reply-To: References: Date: Tue, 17 Apr 2012 15:19:02 -0700 X-Google-Sender-Auth: ov5wl5WykaM2uqX9tKFUhJVtlQM Message-ID: From: Craig Rodrigues To: Adam Vande More Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-emulation@freebsd.org, freebsd-stable@freebsd.org, freebsd-virtualization@freebsd.org Subject: Re: VirtualBox problem booting FreeBSD-9.0-RELEASE-amd64-bootonly.iso 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, 17 Apr 2012 22:19:04 -0000 On Mon, Apr 16, 2012 at 9:29 PM, Adam Vande More wr= ote: > On Mon, Apr 16, 2012 at 10:30 PM, Craig Rodrigues > wrote: >> >> After exchanging a few e-mails with Bernard, I think I understand the >> problem. >> According to the VirtualBox manual: >> >> http://www.virtualbox.org/manual/ch03.html#intro-64bitguests >> >> The CPU needs to support hardware-assisted virtualization in order for >> VirtualBox to support 64-bit guests. >> Without the CPU support, VirtualBox cannot do it. =A0I double checked >> this with CoreInfo.exe from Windows Sysinternals utilities, >> and also from the Intel data sheet for my CPU: >> >> http://ark.intel.com/products/30787 >> (VT-x option not supported) >> >> >> I will use QEMU under Windows until I can get a better machine. :) > > > I believe a Windows 7 product key will activate either 32 or 64 install, = so > unless you have a specific reason to install 64 bit then you are likely > better using 32 anyway.=A0 32 bit OS's and apps use less memory than thei= r > corresponding 64 bit counterparts. > > > > -- > Adam Vande More Hi, Yes, you are right. Windows 7 comes on 2-DVD's, one for 32-bit and one for 64-bit. The same product key can be used for either version. I had installed 64-bit Windows with the intent of testing out 64-bit guest OS's under FreeBSD, and was unaware of the requirements for hardware assisted virtualization. :) I am interested in developing and testing 32-bit and 64-bit Windows binarie= s anyways, so I will keep my install for now. :) Thanks. --=20 Craig Rodrigues rodrigc@crodrigues.org