Can I fix it somehow?Не удалось открыть файл виртуального жёсткого диска /Users/user/Documents/LA-MB.VHDX.
Could not open the medium '/Users/user/Documents/LA-MB.VHDX'.
VD: error VERR_NOT_SUPPORTED opening image file '/Users/user/Documents/LA-MB.VHDX' (VERR_NOT_SUPPORTED).
Код ошибки: NS_ERROR_FAILURE (0x80004005)
Компонент: Medium
Интерфейс: IMedium {05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac}
Вызванный интерфейс: IVirtualBox {fafa4e17-1ee2-4905-a10e-fe7c18bf5554}
Код ошибки метода: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
Virtualbox can not open vhdx file
-
- Posts: 7
- Joined: 20. Jan 2014, 20:55
Virtualbox can not open vhdx file
I've created image of my old Windows 7 notebook in VHDX format, but when I try to open it with Virtualbox running on OSX 10.9, I get the following error:
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Virtualbox can not open vhdx file
a) See the red text.bugmenot44 wrote:VD: error VERR_NOT_SUPPORTED opening image file '/Users/user/Documents/LA-MB.VHDX' (VERR_NOT_SUPPORTED).
Can I fix it somehow?
b) Try something different than VHDX.
c) Help the developers by contributing code to support VHDX.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Posts: 7
- Joined: 20. Jan 2014, 20:55
Re: Virtualbox can not open vhdx file
Surely, I've seen that. Since I can choose VHDX files (it is also available at Files of type dropdown), I expected that Virtualbox supports it.
I can open VHD files, but there is no sense to try something else since I need this particular VHDX image.
Probably, some conversion could help? (but I don't have Windows Server/Windows 8 where it is possible)
I can open VHD files, but there is no sense to try something else since I need this particular VHDX image.
Probably, some conversion could help? (but I don't have Windows Server/Windows 8 where it is possible)
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Virtualbox can not open vhdx file
According to the changelog, VirtualBox has had read-only support for VHDX since 4.2.x, but I've never tried it. In fact this is only the second time I've noticed the format being mentioned. You can try a conversion - readonly should be fine for that. Better IMHO to stick to a more proven format for now.
Re: Virtualbox can not open vhdx file
"A more proven format" ?
This is THE default format now for Hyper-V on Windows Server 2012 or 2012 R2 or Windows 8 or 8.1.
It has additional benefits, notably for supporting much larger volumes, and faster performance including for iSCSI, native hardware acceleration, EFI, dynamic migration and live synchronisation in an heterogeneous architecture combining local and network storage, or better support of volume shadows (possibly on other remote storages).
It's definitely an improvement over VHD (and in Hyper-V we can see much faster I/O with that formatn reduced latency, lower CPU usage, smoother scheduling of processors/threads, better support of NUMA, and possibility to host many more VMs on the same host, with dynamic memory management, including above the physical RAM).
Also VMs can start and stop much faster and more smoothly, they can be set to autostart at boot time without increasing much the boot time and avaialbility of the server. When VMs are running you can't notice that there are other VMs running, all of them can easily get the CPU, memory, and I/O support on-demand.
Of course this has an impact: you need about 100MB of additional storage space per virtual disk (I suppose this is for storing the synchronization/logging data for reliability, recovery and live remounting or migrations)
The VHDX format is proven on very large scales for Hyper-V (which is now free for all and is a direct competitor to VirtualBox, except for legacy hosts on Windows XP and 7 where VHD is still the only option in VirtualPC) and it has excellent compatibility with lots of 32-bit or 64-bit guest OSes too.
And VMware will certainly support that format to allow live migrations of VMs from Windows hosts to Unix/Linux hosts in online clouds.
Even Oracle will need it to sell its own cloud hosting solution (i.e. allowing clients to migrate their local VMs created in Hyper-V with VHDX format onto the cloud and support all features also proposed by Microsoft Azure)
Supporting VHDX is not just a desire, it's a short-time necessity. Of course we can still copy a read-only VHDX to VHD in VirtualBox tools and then copy a VHD to VHDX with Hyper-V tools. But live migration and redeployment is not so easy.
This is THE default format now for Hyper-V on Windows Server 2012 or 2012 R2 or Windows 8 or 8.1.
It has additional benefits, notably for supporting much larger volumes, and faster performance including for iSCSI, native hardware acceleration, EFI, dynamic migration and live synchronisation in an heterogeneous architecture combining local and network storage, or better support of volume shadows (possibly on other remote storages).
It's definitely an improvement over VHD (and in Hyper-V we can see much faster I/O with that formatn reduced latency, lower CPU usage, smoother scheduling of processors/threads, better support of NUMA, and possibility to host many more VMs on the same host, with dynamic memory management, including above the physical RAM).
Also VMs can start and stop much faster and more smoothly, they can be set to autostart at boot time without increasing much the boot time and avaialbility of the server. When VMs are running you can't notice that there are other VMs running, all of them can easily get the CPU, memory, and I/O support on-demand.
Of course this has an impact: you need about 100MB of additional storage space per virtual disk (I suppose this is for storing the synchronization/logging data for reliability, recovery and live remounting or migrations)
The VHDX format is proven on very large scales for Hyper-V (which is now free for all and is a direct competitor to VirtualBox, except for legacy hosts on Windows XP and 7 where VHD is still the only option in VirtualPC) and it has excellent compatibility with lots of 32-bit or 64-bit guest OSes too.
And VMware will certainly support that format to allow live migrations of VMs from Windows hosts to Unix/Linux hosts in online clouds.
Even Oracle will need it to sell its own cloud hosting solution (i.e. allowing clients to migrate their local VMs created in Hyper-V with VHDX format onto the cloud and support all features also proposed by Microsoft Azure)
Supporting VHDX is not just a desire, it's a short-time necessity. Of course we can still copy a read-only VHDX to VHD in VirtualBox tools and then copy a VHD to VHDX with Hyper-V tools. But live migration and redeployment is not so easy.
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Virtualbox can not open vhdx file
I should have thought it was obvious, given that these are the VBox forums, and given the plain meaning of words in the English language (i.e. I was talking about selecting from formats supported by VirtualBox), that by "proven" I meant in the VirtualBox context. Why should any of us care how well VHDX works in Hyper-v? We are not using Hyper-v - in case you hadn't noticed.
Re: Virtualbox can not open vhdx file
this message board wont let my post a link (it wasnt completely correct anyhow) but here's the basic command:
VBoxManage.exe clonehd --format VDI SOURCE.vhdx DEST.vdi
VBoxManage.exe clonehd --format VDI SOURCE.vhdx DEST.vdi