My VDI file won't attach with VERR_NOT_SUPPORTED
Posted: 8. Dec 2020, 00:23
Hi.
I was trying to start up my virtual machine, and I saw in its info that its only hard disk, in VDI format, looks inaccessible. I looked at the path to the disk, and the file exists. When I tried re-attaching the disk to the VM, I got this error:
I had a power outage recently, so my PC obviously shut down, and this VM was running at the time; I think this may be relevant. I've tried using CloneVDI, and it gets an OS error 0 when reading from the file. None of my other VDIs have this.
Here's some info about my host and guest configuration.
Host: HP All-in-One 24-f1xx // Windows 10 build 19042.662 64-bit // 8 GB RAM, 6 GB usable // VirtualBox 6.1.16r140961
Guest: Windows XP SP3 32-bit // 192 MB RAM // Guest Additions
I can't really provide a log, since the issue is with the VDI file and not the VM itself. The VM starts just fine without that disk though.
I was trying to start up my virtual machine, and I saw in its info that its only hard disk, in VDI format, looks inaccessible. I looked at the path to the disk, and the file exists. When I tried re-attaching the disk to the VM, I got this error:
Code: Select all
Could not get the storage format of the medium 'C:\Users\fjmud\Virtualbox VMs\Windows XP\Windows XP.vdi' (VERR_NOT_SUPPORTED).
Result Code: VBOX_E_IPRT_ERROR (0x80BB0005)
Component: MediumWrap
Interface: IMedium {ad47ad09-787b-44ab-b343-a082a3f2dfb1}
Callee: IVirtualBox {d0a0163f-e254-4e5b-a1f2-011cf991c38d}
Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
Here's some info about my host and guest configuration.
Host: HP All-in-One 24-f1xx // Windows 10 build 19042.662 64-bit // 8 GB RAM, 6 GB usable // VirtualBox 6.1.16r140961
Guest: Windows XP SP3 32-bit // 192 MB RAM // Guest Additions
I can't really provide a log, since the issue is with the VDI file and not the VM itself. The VM starts just fine without that disk though.