From owner-freebsd-emulation@FreeBSD.ORG Sun Oct 9 01:49:33 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 4300C1065674 for ; Sun, 9 Oct 2011 01:49:33 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.freebsd.org (Postfix) with ESMTP id CAF8C8FC14 for ; Sun, 9 Oct 2011 01:49:32 +0000 (UTC) Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by hub.org (Postfix) with ESMTP id A6CD21D3300B; Sat, 8 Oct 2011 22:49:29 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 34264-05; Sun, 9 Oct 2011 01:49:30 +0000 (UTC) Received: from [192.168.1.4] (24-246-4-43.cable.teksavvy.com [24.246.4.43]) by hub.org (Postfix) with ESMTPA id B02651D33001; Sat, 8 Oct 2011 22:49:28 -0300 (ADT) Mime-Version: 1.0 (Apple Message framework v1244.3) Content-Type: text/plain; charset=windows-1252 From: Hub- FreeBSD In-Reply-To: <1318056236.19697.5.camel@Nokia-N900-42-11> Date: Sat, 8 Oct 2011 21:49:28 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <000f01cc827e$16763ec0$4362bc40$@daevid.com> <6ab8dc440718c52524fef38f12a355da@bluelife.at> <2CC33D27-ACA3-4305-A4FE-3CEC6514DEDB@hub.org> <1318056236.19697.5.camel@Nokia-N900-42-11> To: =?iso-8859-1?Q?Bernhard_Fr=F6hlich?= X-Mailer: Apple Mail (2.1244.3) 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: Sun, 09 Oct 2011 01:49:33 -0000 On 2011-10-08, at 2:43 AM, Bernhard Fr=F6hlich wrote: > On Sa., 8. Okt. 2011 01:51:27 CEST, Hub- FreeBSD = wrote: >=20 >>=20 >> On 2011-10-04, at 7:28 AM, Bernhard Froehlich wrote: >>=20 >>> On Tue, 4 Oct 2011 03:12:12 -0700, Daevid Vincent wrote: >>>>=20 >>>> I've tried various combinations of the guest settings for: >>>>=20 >>>> . Enable IO APIC >>>>=20 >>>> . Enable PAE/NX >>>>=20 >>>> . Enable VT-x/AMD-V >>>>=20 >>>> . Enable Nested Paging >>>>=20 >>>>=20 >>>>=20 >>>> My VBox.log says: >>>>=20 >>>> 00:00:00.683 [/HWVirtExt/] (level 1) >>>>=20 >>>> 00:00:00.683 64bitEnabled =3D = 0x0000000000000000 (0) >>>=20 >>>=20 >>> You need to create a 64bit capable VM which you haven't. >>>=20 >>> http://www.virtualbox.org/manual/ch03.html#intro-64bitguests >>=20 >> Being one of those that is going through this headache right now = (have >> something to check in BIOS, but its a remote server, so haven't been >> able to yet), the above pointer / url is very much useless, >> unfortunately =85 I've read it, repeatedly, and it happily refers you = to >> the GUI =85 >>=20 >> The only thing that I found on that URL refers to "you should enable = the >> I/O APIC for virtual machines that you intend to use in 64-bit mode" = =85 >> which David stated above that he has tried =85 >>=20 >> So =85 is there something specific at that URL (beyond the I/O APIC = that >> David did try) that he and I (and potentially others) have both = missed >> for this? >=20 > It's also important to use the FreeBSD 64bit preset when creating a = new vm. Don't know which is the correct switch for that on vboxmanage. >=20 > You can also create such a vm on another box with the GUI and copy it = to your headless server or use www/phpvirtualbox. Okay, based on everything I've been able to find out, from here and othe = resources, this should work: VBoxManage createvm --basefolder /vm/1 --register --ostype Linux26_64 = --name vbox.hub.org VBoxManage modifyvm vbox.hub.org --memory 512 --nic1 bridged = --bridgeadapter1 igb0 --ioapic on VBoxManage createhd --filename /vm/1/vbox.hub.org/hdd0.vdi --size 20000 VBoxManage storagectl vbox.hub.org --name "IDE Controller" --add ide VBoxManage storageattach vbox.hub.org --storagectl "IDE Controller" = --port 0 --device 0 --type hdd --medium /vm/1/vbox.hub.org/hdd0.vdi VBoxManage storageattach vbox.hub.org --storagectl "IDE Controller" = --port 0 --device 1 --type dvddrive --medium = /vm/ISO/CentOS-5.4-x86_64-cPanel.iso VBoxHeadless --startvm vbox.hub.org --vnc --vncport 5901 --vncpass pass I still get the 'Your CPU does not support long mode' =85 and I've = triple checked, and the "Intel=AE Virtualization Technology" Setting is = enabled in the BIOS (PhoenixBIOS, Supermicro Motherboard) =85 I've just = found / enabled something called 'Intel VT for Directed I/O' as well =85 = just in case ... System is running FreeBSD 7-STABLE (a bit old, Apr 26th kernel) =85 checking vBox.log, I do see: grep -i VT VBox.log 00:00:01.075 HWACCM: No VT-x or AMD-V CPU extension found. Reason = VERR_VMX_MSR_LOCKED_OR_DISABLED Now, I did find: = http://news.metaparadigma.de/win-oracle-virtualbox-workaround-for-initiali= zation-issue-3395/ Which pretty much points everything to the BIOS =85 so I'm looking at = potential BIOS upgrades for the server to see if that will correct it =85 But, is there anything wrong with what I've done above for setting up = the VBox VM? some switch that I should be setting that isn't =85 ?