From owner-freebsd-emulation@FreeBSD.ORG Thu Oct 13 01:35:12 2011 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 871B9106564A for ; Thu, 13 Oct 2011 01:35:12 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 1347F8FC08 for ; Thu, 13 Oct 2011 01:35:11 +0000 (UTC) Received: by bkbzs8 with SMTP id zs8so947782bkb.13 for ; Wed, 12 Oct 2011 18:35:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=olsqZskjskrCdAJe0lQ4qUhOLBJcRGmtCR42EjcEbhk=; b=c1cGra2wiu+VdKCAAzlwV2T2YEopMEgBUO02Q8UvkEg4/suzdu2WuZ7kzPwSq957DO 3Ibg+eSRyAJEcSFdeUW/F/VcShoUgZ38huQWC5h/PVCU4fgARmsLksQIxGpothFEIzbX vA0S2UeM/4zmym1mYu18EEV3JYmCldUkriRTo= MIME-Version: 1.0 Received: by 10.223.15.147 with SMTP id k19mr2474104faa.26.1318469710674; Wed, 12 Oct 2011 18:35:10 -0700 (PDT) Received: by 10.223.124.197 with HTTP; Wed, 12 Oct 2011 18:35:10 -0700 (PDT) In-Reply-To: <00b501cc8940$a3e09b20$eba1d160$@daevid.com> References: <000f01cc827e$16763ec0$4362bc40$@daevid.com> <6ab8dc440718c52524fef38f12a355da@bluelife.at> <2CC33D27-ACA3-4305-A4FE-3CEC6514DEDB@hub.org> <1318056236.19697.5.camel@Nokia-N900-42-11> <0b1b01cc8790$913ff530$b3bfdf90$@daevid.com> <001701cc892c$5671b2c0$03551840$@daevid.com> <00b501cc8940$a3e09b20$eba1d160$@daevid.com> Date: Wed, 12 Oct 2011 20:35:10 -0500 Message-ID: From: Adam Vande More To: Daevid Vincent Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-emulation@freebsd.org Subject: Re: "CPU doesn't support long mode" error message 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: Thu, 13 Oct 2011 01:35:12 -0000 On Wed, Oct 12, 2011 at 7:39 PM, Daevid Vincent wrote: > Sorry, of course I agree. I hit =93reply=94 thinking that the list was se= tup > like every other normal list I=92m on, and would reply back to the list, = but > apparently it=92s not, and you have to hit =93reply all=94 instead. **sig= h****** > > ** ** > > What I=92ve done just now is re-create a =93FreeBSD_64=94 VM and pointed = it at my > existing .vdi and it does load (although networking is not working at the > moment, but it=92s at least encouraging!)**** > > ** ** > > Couldn=92t I have just change the .vbox file to say=85**** > > OSType=3D"FreeBSD_64" ?? Or is there more to it than that?**** > > Yes, you've gotten the cause. I don't know if Vbox keeps some mapping othe= r than the .vbox file, but the general way of doing it is "VBoxManage modifyvm --ostype " You can list os types with: "VBoxManage list ostypes" And find almost everything you'll need to know about it here: http://www.virtualbox.org/manual/ch08.html --=20 Adam Vande More