virtualbox.org

Hi. I'm running VirtualBox 5.0.12 on an x64 Windows 7 SP1 host, and for some reason, even though HW virtualization is enabled on my AMD A6 CPU, the program doesn't register it. When I repair the program in the setup, it prompts me to, of course, restart the host system, but when I do, it "undoes" the repair. There's an error message just before it shuts down, but it flashes too fast for me to read, something saying, "Installation failed, blah blah blah..." What the hell's going on? It doesn't support hyperthreading, if that helps.

If I recall correctly, and I may not be, you have to turn off the computer completely after toggling the VT-X/AMD-V in the Bios. Complete power down.

Re the error message, usually the installer allows for not shutting the host down immediately after closing the installer. Try to not let the installer do the reboot, maybe the error message will show so you can read it. Also, if the installer is erroring, then Microsoft needs to be consulted about the error: Virtualbox uses the Microsoft MSI installer system, which is provided by MS. There's ways on Google to troubleshoot installer errors.

scottgus1 wrote:If I recall correctly, and I may not be, you have to turn off the computer completely after toggling the VT-X/AMD-V in the Bios. Complete power down.

Re the error message, usually the installer allows for not shutting the host down immediately after closing the installer. Try to not let the installer do the reboot, maybe the error message will show so you can read it. Also, if the installer is erroring, then Microsoft needs to be consulted about the error: Virtualbox uses the Microsoft MSI installer system, which is provided by MS. There's ways on Google to troubleshoot installer errors.

It's an AMD CPU, so AMD-v is enabled by default. Also, even after powering down completely, then restarting, it's still erasing the repair. The only time I get the error message is when I let VirtualBox do the reboot.

jman12351 wrote:Hi. I'm running VirtualBox 5.0.12 on an x64 Windows 7 SP1 host, and for some reason, even though HW virtualization is enabled on my AMD A6 CPU, the program doesn't register it.

What makes you think it doesn't "register it"? Can you not create 64bit guests? Other programs could be using hardware virtualization.

loukingjr wrote: What makes you think it doesn't "register it"? Can you not create 64bit guests? Other programs could be using hardware virtualization.

I had VMWare Workstation, but that was uninstalled, so it can't be that.

Is that the problem though? you can't create 64bit guests? If so, repairing VirtualBox won't fix it.

loukingjr wrote:Is that the problem though? you can't create 64bit guests? If so, repairing VirtualBox won't fix it.

What would fix it, then?

finding which program is using hardware acceleration. Some anti-virus programs use it. Bitdefender uses it. There are several.

It's an AMD CPU, so AMD-v is enabled by default. Also, even after powering down completely, then restarting, it's still erasing the repair. The only time I get the error message is when I let VirtualBox do the reboot.

I would not put a great deal of faith in that statement. I would have more faith if you told me expressly that AMD-v was enabled in the hardware BIOS settings. If it is not, you are wasting your time.

If it is enabled in the BIOS but VirtualBox cannot see it, you need to find out what is using it and preventing VirtualBox from doing so. I doubt that VMWare would, but Hyper-V certainly does. Some phone emulator software programs do too.

BillG is correct of course. Your CPU may very well support AMD-V. That doesn't mean it's enabled in your PC's BIOS.

jman12351 wrote:It's an AMD CPU, so AMD-v is enabled by default.

I think not. The CPU doesn't decide what the motherboard BIOS code allows or doesn't by default. I suspect that this statement confuses "implemented" with "enabled".

mpack wrote:

jman12351 wrote:It's an AMD CPU, so AMD-v is enabled by default.

I think not. The CPU doesn't decide what the motherboard BIOS code allows or doesn't by default. I suspect that this statement confuses "implemented" with "enabled".

No, I've run Piriform Speccy, and it says it's enabled.

jman12351 wrote:No, I've run Piriform Speccy, and it says it's enabled.

You should really enter the BIOS of your PC and make sure.