Date: Wed, 10 Apr 2024 09:24:46 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 278289] nvme_opc_delete_io_sq NOT PERMITTED queue id 0 Message-ID: <bug-278289-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D278289 Bug ID: 278289 Summary: nvme_opc_delete_io_sq NOT PERMITTED queue id 0 Product: Base System Version: 14.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bhyve Assignee: virtualization@FreeBSD.org Reporter: freebsd-bugs@virtualtec.ch We're running a Windows 2019 VM within bhyve, using the nvme drive emulation like so: bhyve -c 4 -m 16G -H -w \ -s 0,hostbridge \ -s 4,nvme,/dev/zvol/data/volumes/zvol2 \ -s 5,virtio-net,tap11 \ -s 7,virtio-net,tap21 \ -s 6,nvme,/dev/zvol/data/volumes/zvol-bk01.r \ -s 29,fbuf,tcp=3D0.0.0.0:5901 \ -s 30,xhci,tablet \ -s 31,lpc \ -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd \ winserv2 & the VM is used to implement a veeam backup repository with ReFS on the 2nd disk. We just had an incident, that this VM took the ReFS volume offline due to these events: stornvme: Reset to device, \Device\RaidPort1, was issued Disk: An error was detected on device\Device\Harddisk1\DR1 during a paging operation stornvme: the driver detected a controller error on \Device\RaidPort1 Disk: An error was detected on device\Device\Harddisk1\DR1 during a paging operation ReFS: The file system was unable to write metadata to the media backing vol= ume R:. A write failed with status "The specified request is not a valid operat= ion for the target device." ReFS will take the volume offline. It may be mounted again automatically. On the freebsd side, I have error messages like these: daemon[70039]: nvme_opc_delete_io_sq NOT PERMITTED queue id 0 / num_squeues= 4 syslogd: last message repeated 5 times Checking the source, a queue_id of 0 is invalid, so why would Windows attem= pt this? Could this be a consequence of issuing a "Reset device" to the nvme controller, and if= so, is there anything the bhyve drive could do to recover from this without failing the request l= ike it does at the moment? Note that this system is rather under powered for the task, so timeouts are= to be expected. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-278289-27103>