Date: Sun, 10 Jan 2021 12:28:11 +0100 From: Andrea Venturoli <ml@netfence.it> To: vbox@FreeBSD.org, freebsd-virtualization@freebsd.org Subject: Re: VirtualBox can't read VDI anymore Message-ID: <8937b6db-0e68-90cd-da86-084c98c241fc@netfence.it> In-Reply-To: <4f894683-d6dc-c878-6e92-fb0832b85a49@netfence.it> References: <4f894683-d6dc-c878-6e92-fb0832b85a49@netfence.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/8/21 7:58 PM, Andrea Venturoli wrote:
> 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 can confirm reverting this change makes VirtualBox work again for me.
(Noted also on #168298).
bye
av.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8937b6db-0e68-90cd-da86-084c98c241fc>