On 2011-10-08, at 2:43 AM, Bernhard Fröhlich wrote: > On Sa., 8. Okt. 2011 01:51:27 CEST, Hub- FreeBSD <free...@hub.org> wrote: > >> >> On 2011-10-04, at 7:28 AM, Bernhard Froehlich wrote: >> >>> On Tue, 4 Oct 2011 03:12:12 -0700, Daevid Vincent wrote: >>>> >>>> I've tried various combinations of the guest settings for: >>>> >>>> . Enable IO APIC >>>> >>>> . Enable PAE/NX >>>> >>>> . Enable VT-x/AMD-V >>>> >>>> . Enable Nested Paging >>>> >>>> >>>> >>>> My VBox.log says: >>>> >>>> 00:00:00.683 [/HWVirtExt/] (level 1) >>>> >>>> 00:00:00.683 64bitEnabled <integer> = 0x0000000000000000 >>>> (0) >>> >>> >>> You need to create a 64bit capable VM which you haven't. >>> >>> http://www.virtualbox.org/manual/ch03.html#intro-64bitguests >> >> 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 … I've read it, repeatedly, and it happily refers you to >> the GUI … >> >> 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" … >> which David stated above that he has tried … >> >> So … 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? > > 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. > > 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' … and I've triple checked, and the "Intel® Virtualization Technology" Setting is enabled in the BIOS (PhoenixBIOS, Supermicro Motherboard) … I've just found / enabled something called 'Intel VT for Directed I/O' as well … just in case ... System is running FreeBSD 7-STABLE (a bit old, Apr 26th kernel) … 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-initialization-issue-3395/ Which pretty much points everything to the BIOS … so I'm looking at potential BIOS upgrades for the server to see if that will correct it … 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 … ? _______________________________________________ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
