tonescas.blogg.se

Additionally, the same manufacturer may implement different BIOS versions depending on the age or model of your computer.

Accessing a computer’s BIOS will differ from manufacturer to manufacturer. Since Access Commander runs in a virtual environment, your computer’s BIOS settings must be configured to allow virtualization. This means that the hardware acceleration settings required by the CPU to support virtualization are currently disabled in your BIOS. This is the first time I’m running VirtualBox on the laptop, so I wasn’t aware that a setting needed to be enabled in the UEFI/BIOS before VirtualBox can run 64-bit operating systems.Having installed the Access Commander virtual machine on your computer it is possible that the machine may not start and you may encounter an error telling you that VT-x is disabled (or referencing a problem with AMD-V if you have an AMD CPU). Figure 1 shows what operating system architectures were supported out of the box. The laptop is running Linux Mint 18.2, with VirtualBox 5.1 installed. So in this short post, you’ll learn how to apply that fix so you too can run both 32- and 64-bit guest operating systems in VirtualBox. I found that the key to getting VirtualBox to run both 32- and 64-bit operating systems is a setting in the UEFI/BIOS. To my surprise, VirtualBox showed that it could only run 32-bit operating system, even though the host operating system is a 64-bit installation.

And the first time I actually tried to do that is today, when I wanted to test drive Debian 9. That includes running guest operating systems in VirtualBox. With my main desktop busy mining Ethereum using an Nvidia GeForce GTX 1070, I’ve had to use my Lenovo G50 (a laptop) for my regular computing tasks.