Discussion:
VirtualBox can't read VDI anymore
(too old to reply)
Andrea Venturoli
2021-01-08 18:58:36 UTC
Permalink
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.
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).
NS_ERROR_FAILURE (0x80004005)
ConsoleWrap
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Any hint?
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.
_______________________________________________
freebsd-***@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-***@freebsd.org"

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Andrea Venturoli
2021-01-10 11:28:11 UTC
Permalink
Post by Andrea Venturoli
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.
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?
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.
_______________________________________________
freebsd-***@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-***@freebsd.org"

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Loading...