VirtualBox can't read VDI anymore
Andrea Venturoli
ml at netfence.it
Sun Jan 10 11:28:16 UTC 2021
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.
More information about the freebsd-emulation
mailing list