![]() However, the better long-term solution would be to install a 64-bit host OS. Pay attention to any warnings or errors from VirtualBox during the import process (in the textbox in the import window) and also while running the VM. ![]() (Also note that the first startup takes quite a long time). The only change required while importing is reducing the allocated RAM - I would suggest no more than 2048 MB, and even that can potentially starve your host. Ok, I actually tested Cloudera, and you can pretty much run the OVF directly. I'm assuming you're running a Virtual Appliance, which you should be able to import into the 32-bit copy of VirtualBox (see the File menu). Make sure your VM guest is configured as 64-bit. Install a 32-bit version of the VirtualBox program, so it can run its exes. Just to be sure, I suggest that you also make sure EPT (Extended Page Tables, also known as SLAT) is enabled, again in firmware (BIOS) settings. Check that the VT-x instruction is available: Since your CPU supports x86_64, this will allow hypervisors to use hardware acceleration to support 64-bit guests despite the 32-bit host OS.Ĭheck that this is correctly enabled using a tool such as CPU-Z. ![]() This is supported by your CPU model, so you should be able to toggle it on in your firmware (BIOS) settings. ![]() According to the VirtualBox Manual, you need to:Įnable VT-x (hardware acceleration) on your CPU. Theoretically, you should be able to do so, without 'hacking' anything. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |