Date: Sun, 10 Jan 2021 11:28:16 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 168298] VirtualBox using AIO on a zvol crashes Message-ID: <bug-168298-27103-qpFet5MhjD@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-168298-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-168298-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D168298 ml@netfence.it changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ml@netfence.it --- Comment #38 from ml@netfence.it --- (In reply to commit-hook from comment #28) This patch broke VirtualBox for me (12.2amd/64, with VDI files accessed via NFSv4). Starting any machine, I get: VDI: error reading pre-header in '....vdi' (VERR_DEV_IO_ERROR). VD: error VERR_VD_VDI_INVALID_HEADER opening image file '....vdi' (VERR_VD_VDI_INVALID_HEADER). Failed to open image '....vdi' in read-write mode (VERR_VD_VDI_INVALID_HEAD= ER). AHCI: Failed to attach drive to Port0 (VERR_VD_VDI_INVALID_HEADER). Result Code: NS_ERROR_FAILURE (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}=20 I can confirm reverting this brings VBox in a working state again. --=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-168298-27103-qpFet5MhjD>