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