Opened 8 years ago
Closed 6 years ago
#16078 closed defect (fixed)
NVMe controller not working
| Reported by: | Sven | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.1.6 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | other |
Description
Create a Windows 10 virtual machine in default configuration (no EFI, 1CPU). Then, after everything is installed and Windows is updated to version 1607, add an NVMe controller and a harddisk.
Result: In device manager, the NVMe controller shows up and the proper drivers are used. But it is marked with a yellow exclamation triangle. The NVMe drive is not available and cannot be partitioned.
On Linux, the NVMe controller doesn't work after "rmmod nvme; modprobe nvme". Tested with the LiveCD ubuntu-16.10-desktop-amd64.iso.
Attachments (1)
Change History (6)
comment:1 by , 8 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 by , 7 years ago
5.2.0 RC1 still has this (or similar) problem.
NVM Express controller appears in Device manager with yellow exclamation:
This device cannot start. (Code 10) An invalid parameter was passed to a service or function.
(Host: Linuxmint 18.2, guest: Win10 16299.15 guest [okay, this is an insider version today, but this build will be released next week to everybody as official Fall Update])
by , 7 years ago
comment:3 by , 7 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
comment:5 by , 6 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
See #17228, closing this again as the issue for this ticket was something else (the current issue was introduced with the Windows 10 Fall Creators update)
There are several NVMe-related fixed in 5.1.8. Please reopen if still relevant with VBox 5.1.8.