Custom Query (16363 matches)
Results (2293 - 2295 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2187 | wontfix | can't use copy/duplicate of virtualdisk ( vdi ) | ||
| Description |
why we can't used copy of virtualdisk ( vdi file ) so we can use directly same os ( two same os ) on same time with different name for networking on them copy the file vdi could but can be use as new/different one because properties said identically its not like microsoft virtualpc that i used before where i could copy virtualdisk as much as i want and used it on the same time ( for networking test between them ) |
|||
| #14062 | duplicate | can't use VHDX file | ||
| Description |
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 |
|||
| #5190 | duplicate | can't use USB on Vista 64 host | ||
| Description |
running a win Xp professional guest on a vista 64 bit host using the latest 3.0.8 virtual box. plugging a usb device of any sort into the computer will cause either a freeze of the host or a blue screen crash of host. This usually destroys the guest XP as well. Once vista is rebooted and the XP host is started, it reports many corrupt files. attempts to fix are fruitless. I have a back up of the XP guest hard drive file and I have had to re-copy that. I need to install a printer on the XP guest so I can then install linksys software for a bi-directional print server (the reason for the XP guest in the first place is that linksys has no 64 bit drivers for that server). I had this working on a previous virtual box build, but after upgrading, I attempted to add some files to XP using a USB flash drive and destroyed the XP guest in the process. If USB support is broken in 3.0.8, which older version works? Are there any plans to restore USB support? Is it just this configuration (vista 64 host/XP guest) that doesn't work? |
|||

