VirtualBox

Opened 7 years ago

Closed 7 years ago

#16080 closed defect (fixed)

NVMe drive stops working after rmmod/modprobe nvme => fixed in SVN/5.1.x

Reported by: Sven Owned by:
Component: other Version: VirtualBox 5.1.8
Keywords: Cc:
Guest type: Linux Host type: other

Description

How to reproduce

  • boot ubuntu 16.10 live CD
  • dd if=/dev/nvme0n1 of=/dev/null works as expected
  • rmmod nvme
  • modprobe nvme
  • dd if=/dev/nvme0n1 of=/dev/null fails with an error

dmesg shows the following errors: nvme nvme0: Device not ready; aborting initialisation nvme nvme0: Removing after probe failure status: -19

Change History (5)

comment:1 by aeichner, 7 years ago

Summary: NVMe drive stops working after rmmod/modprobe nvmeNVMe drive stops working after rmmod/modprobe nvme => fixedin SVN/5.1.x

Thanks for the report, this will be fixed in the next maintenance release.

comment:2 by aeichner, 7 years ago

Summary: NVMe drive stops working after rmmod/modprobe nvme => fixedin SVN/5.1.xNVMe drive stops working after rmmod/modprobe nvme => fixed in SVN/5.1.x

comment:3 by Frank Mehnert, 7 years ago

The fix is part of the most recent 5.1 Extension Pack (>= 112114) which you can download here.

comment:4 by Sven, 7 years ago

I just checked with 5.1.12 and rmmod nvme followed by modprobe nvme now works. I can read the disk after even after rmmod/modprobe.

However, rmmod nvme takes a long time to complete. More precisely, it takes about 60 seconds. It seems as if the driver is waiting for some response - as if the module could only be removed when some internal driver timeout occurs.

comment:5 by Frank Mehnert, 7 years ago

Resolution: fixed
Status: newclosed

Still reproducible with VBox 5.1.18? I couldn't. Using an Ubuntu 16.10 guest with 1 disk attached to the NVMe controller. The nvme module is automatically loaded (together with nvme_core). The disk is accessible by /dev/nvme0n1. I could also rmmod nvme + nvme nvme_core + modprobe nvme. No problem either. Please reopen if this is still a problem for you. In that case, please attach a VBox.log file of such a VM session (mainly to see if your VM configuration is somehow special) and provide exact steps to reproduce.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use