Date: Fri, 8 Jan 2021 19:58:36 +0100 From: Andrea Venturoli <ventu@netfence.it> To: vbox@FreeBSD.org, freebsd-virtualization@freebsd.org Subject: VirtualBox can't read VDI anymore Message-ID: <4f894683-d6dc-c878-6e92-fb0832b85a49@netfence.it>
next in thread | raw e-mail | index | archive | help
Hello.
I'm tracking the quarterly port branches and building my packages with
poudriere.
Today I switched from 2020Q4 to 2021Q1 and upgraded VirtualBox from
5.2.44_3 to 5.2.44_4.
After that I can no longer start any guest.
What 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_HEADER).
> 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}
Any hint?
Does this have anything to do with the following:
> emulators/virtualbox-ose: Turn off aio usage and make VirtualBox use generic
> Unix implementation.
I'm not enabling aio myself or messing with its config in any way, AFAIK.
I tried the sysctl suggested in pkg-messages, but they did not help.
bye & Thanks
av.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4f894683-d6dc-c878-6e92-fb0832b85a49>