Virtualization on Asus Sabertooth 990FX

Hello All, I have been trying to set up on my system Virtual Box 64 Bit software but have been unsuccessful.

Let me start at the beginning:
I have a AMD FX8350 processor with a Asus Sabertooth motherboard 990FX R 2.0, I am running Windows 7 Professional 64 bit operating system.
I want to use Virtual Box to run a 64 bit Linus Mint version for testing. When I have tried this Virtual box will not run the 64 bit version of Mint but will run it appears run the 32 bit version.
I used a program called Speccy to see what my processor is set to through my UEFI and it shows the following:
Visualization is supported but Disabled
Hyper Threading is not supported

I have gone into my UEFI and my Visualization is set to on so I do not know why it is shown as Disabled.

Has any others have this problem and if so what do I need to do!

Regards

Al

well i personaly have an Asus M5A97 EVO r2.0, which basicly has the same bios.
And i personaly dont have issues running 64bit mint.

Did you also install the virtualbox extension pack?
I think its probably an issue related to VB.

I have the extension pack installed but when configuring the set up of mint or for that matter any other operating system it only allows for 32 bit Ops to load. I believe the problem is with virtualization and Hyper Threading not being enabled.

Do you have AMD V turned on?

Did you also tried to install in legacy mode instead of Efi?

When you say it appears to run the 32 bit version have you actually tried to install the 32 bit version? does it run? if it does then the virtualization setting in your BIOS shouldn't be the problem, on your board in the advanced settings make sure SVM is enabled, along with IOMMU, if both of these settings are correct and stick when saving then your problem is elsewhere, AMD CPUs do not support hyper threading that is a Intel cpu function and does not work on AMD.

https://news.ycombinator.com/item?id=1068492

Thank you every one for your input and assistance.

I have virtual box running some time ago in the 32 bit version only but could not get the 64 bit version running. I moved on from that point as I was heading off on an extended holiday. Many months later I brought down Virtual box again and have/am trying to get it working again.
Things that have changed today: I am now able to load virtual box and select a 64 bit operating system something that I could not do previously.
I tried to install both the 32 bit and 64 bit versions of Linux 17.2 Cinnamon versions and both will not install.
I went into my UEFI then into Advanced mode then to the Advanced folder and selected SVM and that is enabled.
I then went into the Northbridge folder and selected IOMMU and turned that on which selects 64Mb.
I then rebooted my system and checked the application Speccy and it showed like before Virtualization is supported but Disabled. This is the key I believe, I have to turn Virtualization to on to make this work?

Thoughts please!

So something changed in that many months with your computer either hardware or software that is preventing it from working....did you change anything? maybe trying to solve another unrelated issue...think back....

I have tried to recreate everything going back several months ago. I have tried to revert my UEFI to its base configuration but all has failed. What gets me is that I have set the bios (UEFI) and reset the bios to support Virtualization, which it had when I first got the system but the system stubbornly maintains Virtualization as "Disabled".
I was hoping that Wendel might jump in here as he has the same MB and CPU that I have.

I have ran out of things to do so I will now contact Asus and see where that goes.

Thanks everyone for all of your input.

1 Like

Hello All;
Maybe this will help someone as I have finally got Virtual Box running.
I found that there where two issues at work that gave me fits. The first was a piece of software called Speccy,
When I would go into my UEFI and turn on SVM (for virtualization) Speccy would show that visualization was disabled.
This is an error in the Speccy utility!
The second and most important fix was moving to VirtualBox-5.0.4-102546-Win, the version I down line loaded about a month ago would not work. This version worked like a dream

Best to All