virtualbox does not recognize AMD-V enabled

[Evensteven]

I have an AMD E1-1200 APU chipset running Windows 8.1, which is AMD-V enabled, and according to the Piriform Speccy application is "supported and enabled."

According to my Windows Features box, Hyper V is not installed (it is not listed with a check box). Therefore, I don't know what other application could be stealing AMD-V and not sharing it with virtualbox. All I know, is that I have AMD-V enabled, and virtualbox for whatever reason, is not detecting it.

I was (with much coaxing) able to install Ubuntu 32 bit, but watching it run is like watching paint dry..

In the Ubuntu 64 bit installation, I was able to choose Ubuntu 64 bit from the drop down menu, but the boot always craps out with the following error: AMD-V is disabled in the BIOS. (VERR_SVM_DISABLED).

Log file attached.

Your comments would be much appreciated.

[mpack]

00:00:08.515354 VMSetError: AMD-V is disabled in the BIOS.

Believe what the message tells you. It isn't wrong.

You also seem to be operating under the misapprehension that 64bit guests can be expected to run faster than 32bit on the same hardware? In fact the opposite is true. 64bit addressing allows an OS to handle larger memory, but moving twice as much RAM for the same function has a cost attached.

If your 32bit Ubuntu ran slowly, it's because of the VM recipe you chose.

[Evensteven]

In all humility, what do you mean by

VM recipe

"?

[loukingjr]

VM recipe = the settings you used for the guest.

[AnrDaemon]

In all humility, what do you mean by

VM recipe

"?

The template you've picked when adding new VM to the list.

[mpack]

The template you've picked when adding new VM to the list.

... as modified by the user.

[loukingjr]

I have a question regarding this post. The OP said he can choose the 64bit template…

in the Ubuntu 64 bit installation, I was able to choose Ubuntu 64 bit from the drop down menu

My understanding was, without VT-x/AMD-V enabled, there won 't be any 64bit templates available to chose from.
Yet…

00:00:08.515354 VMSetError: AMD-V is disabled in the BIOS.

How can both be true? Or did he disable VT-X/AMD-V in the guest?

[mpack]

Yeah, I had similar thoughts but let it slide given the state reached. I assume that there has been intermediate steps left out, like moving the VM from another PC.

[loukingjr]

Strange, Maybe more info from the OP will be forthcoming.

[Evensteven]

Both the Ubuntu 32 bit and Ubuntu 64 bit VMs are initial installations in VirtualBox.

My computer is a Toshiba Satellite 855D. It seems there is a great deal of confusion as to whether AMD-V is enabled or not in Toshiba BIOS versions. I if you care to see some of the conversation, here is a link to one Toshiba AMD-V discussion: http://www.techsupportforum.com/forums/ ... 52997.html

My own BIOS version is Toshiba 6.20, which is the latest one offered for this laptop. As mentioned in the discussion link above with regard to other Toshiba BIOS versions, there is no option in Toshiba BIOS 6.20 to select or deselect AMD-V.

Oddly, in the Ubuntu 64 bit installation, the <settings> <system> <processor> tab has the checkbox for VT-x/AMD-V and it is checked.

I don't know what to tell you other than it is a confusing situation, which is basically out of my control.

I'm fully willing to believe that there is no hardware virtualization assistance from the AMD chips installed in my Toshiba, because of the dialup-modem speeds with which the Ubuntu 32 bit VM limps along. But, it is enough for me to complete the Network Defense lab course I am taking, and that is good enough for me.

BTW: The instructor recommended 512k memory and 20 GB of hard drive space for the installation "recipe." If you guys have speed enhancement ideas, please let me know, and thanks for your help on this.

[mpack]

512MB is a good number for a 32bit VM. I would go for a 40GB dynamic drive. Don't be talking into using a fixed size drive.

Other than that, the main performance tip is to install the Guest Additions. Details in user manual.