Hello!
Before build 1803 my VM was working fine! Now I cannot create any 64 bit machine, my VM is not working complaining the Hyper-V etc... I have a second drive with boot, installed VirtualBox there and the 64bit is available, so the issue remains with that new build.
My Windows is Home Edition, I don't have Hyper-V option to install/uninstall.
The thing simply stopped to work
Actually the error is not showing option for allow creating 64bit OS.
Now with my previous Linux VM I have that message:
"Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT)."
And the other shows:
"VT-x is not available (VERR_VMX_NO_VMX)."
EDIT: Also, I cannot increase the number of CPU, its grayed on I can't change.
My other boot, same computer, can handle with that, but of course I need to start these VM on this boot session.
If you're on Home, I'm not sure if this will be of help, but I had the same problem and fixed it by setting a local policy to disable the Virtualization Base Security in Win 10:
virtualbox.org View topic - [Solved] Windows 10 1803 - VT-x is not available
Hi.Hello!
Before build 1803 my VM was working fine! Now I cannot create any 64 bit machine, my VM is not working complaining the Hyper-V etc... I have a second drive with boot, installed VirtualBox there and the 64bit is available, so the issue remains with that new build.
My Windows is Home Edition, I don't have Hyper-V option to install/uninstall.
The thing simply stopped to work
For Windows 10 Home and newest versions, need to disable in registry.
Code:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity Enabled = 0
This worked, thank you! One thing to add is that in 1803 in the optional Windows features there is no longer a "Hyper-V" option but rather it is called "Windows Hypervisor Platform" and the description makes it sound like you need to enable it to use Virtualization it is not - make sure this isn't enabled as that will cause the problems that are being reported.
Hi there
the FREE version of VMPLAYER from VMware will work seamlessly without needing any modifications to registry.
For 32 bit guests you don't need any settings in BIOS to make it work. For 64 bit guests you do need to enable the Intel VT virtualisation in the Bios though.
Otherwise define an empty VM (just the HDD space, and virtual config such as networking etc).
Then get an iso (software) image of the guest OS, and in the VM just boot from the iso and install the guest OS just as if installing on a real machine.
Cheers
jimbo
vmware player
- does not support snapshots
- does not support nonpersistent disks directly
- is not open source
- is free only for non-profit use
etc
jimbo45: If you say A please say B too. People have their own reasons for using particular software.
(Yes, at home I use vmware player more frequently than other non-baremetal hypervisors.)
Last edited by muchomurka; 30 May 2018 at 08:25.
Hi there
I don't think you mentioned snapshotting / non persistent disks etc in the OP --- if you had stated these were required features then of course I would not have suggested vmplayer.
IMO anyway most basic (installed by non superuser) software should work without needing registry changes -- BIOS changes fine -- VT-X I think is still needed whether VBOX or VMWARE for running 64 bit guests.
One can only make suggestions on the information provided. Of course people will always have preferences over what software they like to use and specific reasons for using it.
I don't think it's necessarily wrong to point out possible alternatives
cheers
jimbo
Magno never said he wants to use any software other than Virtualbox, he tries to sort his problem. Consequently, there was no need to enumerate required features. And especially snapshotting is very basic feature; afaik only VMPlayer - the most crippled hypervisor - lacks it.
Neither Virtualbox nor VMPlayer can be correctly installed by non-superuser account.
Did you notice it is one of "after Win10 1803 upgrade" problems? Next version of Virtualbox will likely address it.
Maybe - if issue becomes unresolvable; still many problems converting existing VMs. in any case, it would be better not to conceal serious shortcomings of recommended software.
Quote