virtualbox.org

My HP Z200 Windows 7 machine died so I am now booting up in an HP EliteDesk Mini PC with the same Windows 7 harddrive.

I cannot find any hyperthreading or virtualisation options in the BIOS for the EliteDesk - there is very little in the way of configuration.

When I try to boot up my VM in VirtualBox I get the error "The native API dll was not found (C:\Windows\system32\WinHvPlatform.dll) (VER_NEM_NOT_AVAILABLE) VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).

Is it not possible to run VirtualBox on this machine?? I didn't think VirtualBox required fancy hardware?? Any help in booting this up would be greatly appreciated.

Please find log file attached.

If you cannot enable hardware virtualization on the host, your only option is to try 6.0.24. Version 6.1 will not run vms without it.

Have you done an Internet search to find how to enable it on your particular host?

https://support.hp.com/lv-en/document/c03840403#AbT4 - Search for SVM in the BIOS Security settings and make sure it's enabled.

SparkyNZ wrote:I didn't think VirtualBox required fancy hardware??

Uh... VirtualBox is (by design) one of the most resource hungry apps you will ever encounter. Do not take it lightly.

The Elitedesk G1 mini has several processor variants. As far as I can tell all of the ones I know of (i3-4160T, i5-4570T, i5-4590T, i7-4785T) do support VT-x. It does however need to be enabled in the BIOS.

Note however that you only have 4 cores total (max - VirtualBox has no use for threads), so you obviously can't assign 4 cores to a VM. Reduce to 2, after fixing the BIOS problem.

Final note: your Elitedesk has 8GB RAM. Fitting two 64bit OS in that will be a tight squeeze, so take care with RAM.

I would suggest you google " HP EliteDesk Mini bios enable VT-x" and check out the answers. If you know the EliteDesk Mini include it in the google search.

multiOS wrote:Search for SVM in the BIOS Security settings and make sure it's enabled.

I believe SVM is an AMD term, so there won't be any mention of that with any of the processors listed.

Also beware: "Elitedesk 800" covers a broad category of confusingly named small PCs. The important distinction here is "G1 Desktop Mini" (see log), which means it's one of the very small (~200mm square ~30mm deep), first generation boxes with the CPU range I mentioned.

I'm very fond of the G1 Mini range. They take up very little space (especially headless) and will happily sit in a corner crunching numbers all day, e.g. video recoding. I don't run VMs on mine though: no point, you just buy another G1 Mini on eBay and install your little project directly onto it!

mpack,

Thanks for the correction. I noted the AMD Processor, but missed the "G1' element of the computer name My own experience of mini-PCs is largely with NUC models which seem to provide much clearer specs.

I have now checked the correct BIOS Setup document for the 800 G1 - https://support.hp.com/gb-en/document/c04272112#AbT4 - Rather confusingly for users it states "Virtualization Technology (VTx) (enable/disable) - Controls the virtualization features of the processor. Changing this setting requires turning the computer off and then back on. Default is disabled." but under a Security heading, which states "System Security (these options are hardware dependent)".

multiOS wrote:I noted the AMD Processor, but missed the "G1' element of the computer name

Not your fault! HP has an intensely annoying habit of giving almost exactly the same verbose name to radically different products. E.g. look up "HP EliteDesk 800 G1 SFF" and then "HP EliteDesk 800 G1 Mini". The problem is that many discussions will leave off that last word from the description - so you have to be very careful when reading eBay listings, since the seller doesn't always choose the right picture either. Careful reading of the specs usually confirm if it's the Mini or not.

Hopefully the OP will soon confirm the processor so we'll know for certain if it supports VT-x (but I'm quite certain it does).

FWIW, the CPU vendor will prove not to be AMD, because VirtualBox only delivers the VERR_VMX_MSR_ALL_VMX_DISABLED error after identifying an Intel (or VIA or ..., but not AMD) CPU.

There is a very small probability to get this error on an AMD CPU, if VirtualBox would be running inside another hypervisor emulating an Intel CPU on an AMD CPU, but I haven't heard of such a hypervisor yet.

fth0 wrote:because VirtualBox only delivers the VERR_VMX_MSR_ALL_VMX_DISABLED error after identifying an Intel (or VIA or ..., but not AMD) CPU.

Well that and it explicitly said: "VT-x is disabled in the BIOS for all CPU modes".

Thank you everybody. Sorry it took so long for me to get round to checking this out.

I was looking in the wrong place in the BIOS for that VT-x enable option - I honestly didn't think it would be under "security". So I enabled it and VirtualBox has started up no problem! Thank you.

FYI, the machine is an i5-4570T