Skip to main content

Resolving a VirtualBox BIOS error on an MSi motherboard-based PC

What follows is how I solved the following error message from VirtualBox.

Not in a hypervisor partition (HVP=0) (VERR_NEM_NOT_AVAILABLE).
AMD-V is disabled in the BIOS (or by the host OS) (VERR_SVM_DISABLED).
Result Code:E_FAIL (0X80004005)
Component:ConsoleWrap
Interface:IConsole {6ac83d89-6ee7-4e33-8ae6-b257b2e81be8}

VERR_SVM_DISABLED error message from VirtualBox

What am I messing around with hypervisors and virtual machines for? And for that matter, what's a virtual machine anyway? Answers to these questions are here; but back to the matter at hand.

Fortunately the error message is actually quite helpful and gives us the answer to solving the problem. SVM is disabled in the BIOS.

SVM is the TLA for Secure Virtual Machine (see this article for more information) and the BIOS on motherboards is normally shipped with this option disabled, because the majority of users never need to use it and having it enabled is a minor but not insignificant security issue.

I am running an MSi A320M-A PRO motherboard so accessing the BIOS is simply a matter of holding down the DEL key at start up and, instead of booting to Windows, the user interface for the MSi Click BIOS will appear (I am running the 7C51 2020 version not the flashy Click 5 version though).

The required setting change in this case is,

Overclocking > CPU Features > SVM Mode > Enable.

Once it is set to Enabled simply Save Changes and Reboot and VirtualBox will now start to play ball.

Now we can get a virtualised server set up what's next? Well that would be getting Home Assistant and Grocy on-line.

For anyone who wants a step-by-step tutorial, see below. Apologies for the picture quality, but it should be good enough. There are a series of other tutorials out there but the BIOS options seem to be quite variable (here are three different options from MSi [1/2/3] all from the same Google search).

Step-by-step tutorial

After holding down the DEL key at start up here is the first screen I was greeted with. Your mouse should still be working so mouse over and click on the Overclocking icon circled in red.

BIOS Start Menu

Once you are on the Overclocking Menu tab, scroll down to the bottom of the page,

BIOS Overclocking Menu

where you will find a menu item, CPU Features (red box).

Locate CPU Features option

Selecting that leads to the Overclocking\CPU Features menu and you are looking for the SVM Mode option (red box), which is marked as [Disabled].

BIOS Overclocking CPU Features Menu

Clicking the Disabled text will bring up an option box titled SVM Mode from which you can select Enabled.

BIOS SVM Mode option

Once that reads SVM Mode - Enabled go to the Save & Exit tab (red circle in screenshot below) and select Save Changes and Reboot (red square).

BIOS Save & Exit option

This will generate a pop up asking "Save configuration and reset?" Clicking Yes will restart your PC,

BIOS alterations complete

when your PC has restarted you should be able to launch VirtualBox and start up a VM from it with no errors. Well, at least not the one you started with.

Comments

Popular posts from this blog

Evri-thing, Evri-where, All Over the Place

You have to wonder why Hermes went through the hassle of rebranding themselves to Evri, then you get a parcel delivered by them. Only a year ago in a desperate, and cynical, attempt to shed their woeful reputation as the worst parcel delivery company in the UK Hermes rebranded themselves as Evri. On the 14 th March 2022 they rolled out their corporate PR machine and made promises . "The new brand will also see a significant investment in its customer service as part of its commitment to ensuring that its customer service remains responsive, knowledgeable and helpful. This will include Evri opening a fully UK-based customer service team and adding 200 experts who will be based in local depots, closer to where potential issues are. It will also be upgrading its chatbot and releasing more phone lines for those who prefer to speak directly to someone." So was it a surprise when I got an e-mail about a parcel I was expecting? Well, most other couriers don't do this an...

How-to: Setting up a Blogger account with a non-Google e-mail address

As I've set up an e-mail address for the blog it makes sense to be able to post from it too. To do that I will need to set up an account with Blogger for the new e-mail address. At the same time I'll create a gmail account to both manage the blog and give access to the Google apps suite without the monthly fee. Skullcinema@gmail.com is already taken (as there is nothing new under the sun), but I can take a related e-mail address. I won't publish it here as the first address will generate enough spam as it is. Setting up a gmail account really doesn't require a guide, but it is covered here if you need one. So, off to set up an account  through Blogger . First of all though, log out of Google and/or Chrome or it will pull you straight through to Blogger on the account you are logged in on. Choose SIGN IN in the top right-hand corner of the Blogger home page, and then select  Use another account underneath the list of your current Google accounts. Now ...

Alexander Aircraft Company

And here we are at the Alexander Aircraft Company , a start-class rated article about a defunct aeronautical engineering company from the USA in the 1920's. As this is a subject with more interest to me I spent a little longer than usual on this article, giving it a top-to-tail polish. Starting with the lead paragraph , which consisted of a grand total of twelve words on arrival, I expanded it, if only by a bit, so at least there are now two sentences. The associated book citation was limited so this was expanded as well. Founding and Disaster subsections received a heavy dose of wiki-linking and the single reference provided across both subsections was dead, requiring a trip to The Wayback Machine to search for the given URL. The Wayback Machine is part of The Internet Archive , which is a not-for-profit set up back in the early days of the web to archive the nascent internet, as it was recognised that the content was not anywhere near as permanent as the previous forms of...