Date: Sat, 1 Oct 2011 13:58:32 -0400 From: Hub- FreeBSD <freebsd@hub.org> To: Sean C. Farley <scf@FreeBSD.org> Cc: freebsd-emulation@FreeBSD.org Subject: =?windows-1252?q?Re=3A_VirtualBox=3A_64bit_FreeBSD_guest_on_64bi?= =?windows-1252?q?t_FreeBSD_host_=85_=22Long_Mode=22=3F?= Message-ID: <7F4C681F-098D-4C2F-81F7-6A20BDA9B282@hub.org> In-Reply-To: <alpine.BSF.2.02.1109302049070.5298@thor.farley.org> References: <FF4A7997-77DA-4B74-926B-18A8462C768C@hub.org> <87FBE966-B70F-48F2-9771-796DA8D3032D@hub.org> <CA%2BtpaK3BzYAQZxJCi3vAc1NidQ7AkANyHHeo-rt5bxsBQo5%2Btw@mail.gmail.com> <156697DC-0D33-46A8-A719-096EED0EE699@hub.org> <alpine.BSF.2.00.1109301749070.32221@wonkity.com> <BF8A9711-EC9C-4C41-B500-9FACD59041D7@hub.org> <alpine.BSF.2.02.1109302049070.5298@thor.farley.org>
index | next in thread | previous in thread | raw e-mail
On 2011-09-30, at 8:54 PM, Sean C. Farley wrote: > On Fri, 30 Sep 2011, Hub- FreeBSD wrote: > >> 'k, I'm doing everything from the command line, and when I did the createvm, and according to the docs (https://www.virtualbox.org/manual/ch08.html#idp12400368), there eis no option to set 64 vs 32bit … even the modifyvm section only seems to have the --ostype option, and in this case, I had set it to FreeBSD_64, based on what is displayed when you do a 'list ostypes', as what should be for a 64bit environment … >> >> So, either something is broken, or I'm missing an argument / setting here :( > > The only difference between a 32-bit and 64-bit VM according to the XML files generated is whether I/O APIC is enabled. You could create a VM then use modifyvm to enable the I/O APIC: > VBoxManage modifyvm <uuid|name> --ioapic on 'k, that didn't help any … still get told no long mode, use a 32bit distro … showvminfo shows: Name: vbox.hub.org Guest OS: Linux 2.6 (64 bit) UUID: cd5424cc-4fd3-40b3-8745-c2c4f5583639 Config file: /vm/1/vbox.hub.org/vbox.hub.org.vbox Snapshot folder: /vm/1/vbox.hub.org/Snapshots Log folder: /vm/1/vbox.hub.org/Logs Hardware UUID: cd5424cc-4fd3-40b3-8745-c2c4f5583639 Memory size: 512MB Page Fusion: off VRAM size: 8MB HPET: off Chipset: piix3 Firmware: BIOS Number of CPUs: 1 Synthetic Cpu: off CPUID overrides: None Boot menu mode: message and menu Boot Device (1): Floppy Boot Device (2): DVD Boot Device (3): HardDisk Boot Device (4): Not Assigned ACPI: on IOAPIC: on PAE: on Time offset: 0 ms RTC: local time Hardw. virt.ext: on Hardw. virt.ext exclusive: on Nested Paging: on Large Pages: on VT-x VPID: on State: powered off (since 2011-10-01T17:44:25.000000000) Tried also --chipset ich9 --hwvirtex of Reading through the section on Hardware vs Software Virtualization, apparently VT-X has to be enabled for 64bit guests … now, on the server I'm using, looking at dmesg for ny CPU Features: CPU: Intel(R) Xeon(R) CPU E5420 @ 2.50GHz (2500.10-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x1067a Family = 6 Model = 17 Stepping = 10 Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> Features2=0x40ce3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,XSAVE> AMD Features=0x20100800<SYSCALL,NX,LM> AMD Features2=0x1<LAHF> TSC: P-state invariant Cores per package: 4 I don't see VTX in there … *should* I? Is this a case of, unbeknownst to me, it isn't enabled in the BIOS? This is a remote server, so a quick reboot / check isn't the easiest to do, so would alike to confirm before I go down that route … can someone that does have 64bit guests working check their CPU Features and let me know if I am missing that Feature here? :( Thx …help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7F4C681F-098D-4C2F-81F7-6A20BDA9B282>