From nobody Wed Apr 10 09:24:46 2024 X-Original-To: virtualization@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VDy8Z3Jcfz5Gkxl for ; Wed, 10 Apr 2024 09:24:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VDy8Z1PsMz43w9 for ; Wed, 10 Apr 2024 09:24:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1712741086; a=rsa-sha256; cv=none; b=uWe0eTLus+jiS/Q5PLzfRdPnUetwEEa6jde2g8pxEFhDjockTvSM2r2WHv+/q5SlZtiz2x 3uKic/HzkbIz21U5C5/Om/WebouAMJrMeWFQmHcFDkO+8kbP6zV338u0XKOK5WDv7bSCy4 rRUmvobGu8JwZSA8ORF3yBct0Ue5tUZwhuwHUPWYC6BrVjKKtwOib/vsG7gNWMnG1NRJDy Pbb2GBTLCYcbkxB/cmL7aRLEnhL5nqO6eWCbSN0TihoCbz9jpd8fVxiBPJtr49Z2/ttKCx rOyXcGxjXBZXaGz/1AXyFqs/rs0btf45C7tge3QyzXt0CFDHuxhnTtWhlXdbJA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1712741086; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=ELdvicw/AqPU95xf8gR5myQ2xzv3S8TOtAzZBkEEYlY=; b=cfinIWAo4h/5/w62IyE/XEXqy+MElLFORVqj52HobrKZKlyeloUL+iMHPINFijSUpxR75M bA7ad/yLINLONkN1DX0kB/Cl37WEU9fCmJst/7R+Lh1vmd5tFAWWfRda2zTQw9kWh30IHq mYoQFHs573gEZpUcfaTQxViFAE9zd3LvejDQ3m8nEY9bl7xzJT4Pp8Nq/eUUyit5zW5+3V kowVr6hIkM1h4YiDc9wBoN/TH7uHCc9WSwnIysWf7LBbgL1G/aG5n0OgTHqGkUVM4E1aA/ 0fzksNXt/sDa38Bthrlhoj5XN0PruatkDMpVvMovbKDyZw+xP4qcwnRw6CXz2g== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4VDy8Z11WmzXcb for ; Wed, 10 Apr 2024 09:24:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 43A9OkZp056022 for ; Wed, 10 Apr 2024 09:24:46 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 43A9OkA6056021 for virtualization@FreeBSD.org; Wed, 10 Apr 2024 09:24:46 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 278289] nvme_opc_delete_io_sq NOT PERMITTED queue id 0 Date: Wed, 10 Apr 2024 09:24:46 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bhyve X-Bugzilla-Version: 14.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: freebsd-bugs@virtualtec.ch X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-virtualization List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org MIME-Version: 1.0 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.=