Installing Windows 10 as EFI guest on VirtualBox with NVME fails to detect the attached storage device.Fedora 29 did not survive the change, waiting in an endless dracut loop.Ubuntu going back to Trusty had no problems. Some were previously even configured with IDE. I tested most of my VMs switching them from SATA to NVME.
It's as if you are unplugging the hard drive, which results in the same error message. There are no NVME drivers for BIOS systems, at least not in VirtualBox for now and probably will never be. The virtual machine has to boot as an EFI guest.To get expertise advice on why your non-Ubuntu OS does not boot after changing the storage configuration of your VM you should be looking in a place where the respective OS is on topic.Ĭonfiguring storage for VMs or VirtualBox VMs in particular beyond the suggested templates provided by the wizard leaves the tedious task of reading documentation and testing to you.There are a few issues with how you assess the your problem. There are a few problems with your question which make it not a good fit here. A drive gets detected when setting both extradata option on a 2 core VM, but booting from the controller or installing a new copy of Windows failed in my tests.
0 kommentar(er)
