VirtualBox

Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#14062 closed defect (duplicate)

can't use VHDX file

Reported by: costinel Owned by:
Component: virtual disk Version: VirtualBox 4.3.26
Keywords: Microsoft Hyper-V VHDX Cc:
Guest type: all Host type: all

Description (last modified by aeichner)

using latest released version 4.3.26 on windows 8.1 64bit, trying to attach existing VHDX file to a vm.

steps to reproduce: 1.download server 2012 r2 eval version from http://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2012-r2 2.create a vm and try to add existing vhdx file - it won't attach the vhdx.

Log:

VirtualBox COM Server 4.3.26 r98988 win.amd64 (Mar 16 2015 17:35:35) release log
00:00:00.006000 main Log opened 2015-04-20T18:55:25.290762400Z
00:00:00.006000 main Build Type: release
00:00:00.006000 main OS Product: Windows 8.1
00:00:00.006000 main OS Release: 6.3.9600
00:00:00.006000 main OS Service Pack:
00:00:00.029007 main DMI Product Name: X38-DQ6
00:00:00.038007 main DMI Product Version:
00:00:00.038007 main Host RAM: 4094MB total, 1059MB available
00:00:00.038007 main Executable: D:\Programs\virtualbox\VBoxSVC.exe
00:00:00.038007 main Process ID: 7780
00:00:00.038007 main Package type: WINDOWS_64BITS_GENERIC
00:00:01.153411 HostDnsMonitorProxy::notify
00:00:01.153411 HostDnsMonitorProxy: Host's DNS information updated:
00:00:01.153411 server 1: 192.168.1.1
00:00:01.153411 no search string entries
00:00:01.153411 domain: example.com
00:00:01.218414 VDInit finished
00:00:03.171525 USBPROXY usbLibDevStrDrEntryGet: DeviceIoControl 1 fail winEr (31)
00:01:03.022308 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac} aComponent={Medium} aText={Could not open the medium 'D:\IMAGES\10041.vhdx'. 00:01:03.023308 VD: error VERR_NOT_SUPPORTED opening image file 'D:\IMAGES\10041.vhdx' (VERR_NOT_SUPPORTED)}, preserve=false 
00:01:41.770504 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={480cf695-2d8d-4256-9c7c-cce4184fa048} aComponent={Machine} aText={This machine does not have any snapshots}, preserve=false
00:02:32.216361 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac} aComponent={Medium} aText={Could not open the medium 'D:\IMAGES\10041.vhdx'. 00:02:32.216361 VD: error VERR_NOT_SUPPORTED opening image file 'D:\IMAGES\10041.vhdx' (VERR_NOT_SUPPORTED)}, preserve=false 
00:02:42.405939 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac} aComponent={Medium} aText={Could not open the medium 'D:\IMAGES\2012r2_eval.vhdx'. 00:02:42.405939 VD: error VERR_NOT_SUPPORTED opening image file 'D:\IMAGES\2012r2_eval.vhdx' (VERR_NOT_SUPPORTED)}, preserve=false 
00:08:18.733993 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac} aComponent={Medium} aText={Could not open the medium 'D:\IMAGES\10041.vhdx'. 00:08:18.733993 VD: error VERR_NOT_SUPPORTED opening image file 'D:\IMAGES\10041.vhdx' (VERR_NOT_SUPPORTED)}, preserve=false 

I also get the same error using 4.3.x revision 99378

I thought this was an open format[1]? Is it a bug in vbox or should the file dialog filter out VHDX files? This redhat bug suggests some qemu-img code for reading VHDX is already working: https://bugzilla.redhat.com/show_bug.cgi?id=1007176

[1] http://www.microsoft.com/en-us/download/details.aspx?id=34750

Change History (3)

comment:1 by aeichner, 9 years ago

Description: modified (diff)

VHDX is supported readonly only so far. You need to convert it to a format which VirtualBox supports writing to like VDI, VHD or VMDK in order to attach it to a VM. This can be done using VBoxManage:

VBoxManage clonemedium disk <input VHDX> <output image>

comment:2 by aeichner, 9 years ago

Resolution: duplicate
Status: newclosed

Btw. duplicate of #12399. Please don't open new tickets but use the existing one.

comment:3 by costinel, 9 years ago

I created new because:

1) #12399 was 17 months old with NO FEEDBACK from developers 2) #12399 had a different message VBOX_E_OBJECT_NOT_FOUND while I only had VERR_NOT_SUPPORTED so I assumed it could be a different cause.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use