Closed francescom closed 8 years ago
A side note: my .ievms folder is a symbolic link to a visible folder on another HD although I don't think this really changes anything..
Checking for existing IE6 - WinXP VM
Creating IE6 - WinXP VM (disk: /Users/USERNAME/.ievms/IE6 - WinXP-disk1.vmdk)
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /Users/USERNAME/.ievms/IE6 - WinXP.ova...
OK.
Disks: vmdisk1 136260878336 -1 http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized IE6 - WinXP-disk1.vmdk -1 -1
Virtual system 0:
0: Suggested OS type: "WindowsXP"
(change with "--vsys 0 --ostype <type>"; use "list ostypes" to list all possible values)
1: VM name specified with --vmname: "IE6 - WinXP"
2: Number of CPUs: 2
(change with "--vsys 0 --cpus <n>")
3: Guest memory: 512 MB
(change with "--vsys 0 --memory <MB>")
4: Sound card (appliance expects "", can change on import)
(disable with "--vsys 0 --unit 4 --ignore")
5: USB controller
(disable with "--vsys 0 --unit 5 --ignore")
6: Network adapter: orig NAT, config 2, extra slot=0;type=NAT
7: CD-ROM
(disable with "--vsys 0 --unit 7 --ignore")
8: IDE controller, type PIIX4
(disable with "--vsys 0 --unit 8 --ignore")
9: IDE controller, type PIIX4
(disable with "--vsys 0 --unit 9 --ignore")
10: Hard disk image: source image=IE6 - WinXP-disk1.vmdk, target path=/Users/USERNAME/.ievms/IE6 - WinXP-disk1.vmdk, controller=8;channel=0
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Appliance import failed
VBoxManage: error: Machine settings file '/Users/USERNAME/VirtualBox VMs/IE6 - WinXP/IE6 - WinXP.vbox' already exists
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component Machine, interface IMachine
VBoxManage: error: Context: "int handleImportAppliance(HandlerArg*)" at line 779 of file VBoxManageAppliance.cpp
getting the same or similar issue stopping at IE6
Getting the same issues here from a fresh install.
anybody have a fix for this?
Actually the Explorer 11 VM is in reality an explorer 9 VM plus the link to update to ie11 from MS. So if you install the ie 11 VM and sort of duplicate it before updating to ie 11 you got it.
I installed version 4.2.2 of virtual box and I no longer have this issue
I had the same issue when creating an IE8 system.
VBoxManage: error: Machine settings file '/Users/USERNAME/VirtualBox VMs/IE8 - WinXP/IE8 - WinXP.vbox' already exists VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component Machine, interface IMachine VBoxManage: error: Context: "int handleImportAppliance(HandlerArg*)" at line 779 of file VBoxManageAppliance.cpp
For me this happened when a box existed under ~/User/me/VirtualBox VMs/ however that didn't appear inside Virtualbox (for whatever reason). Deleting that folder then running the script again worked fine. Also you might want to look inside ~/.ievms for any incomplete/corrupt downloads.
I am running VirtualBox 4.3.20 and this solved my issue:
VBoxManage list hdds
State:
field for inaccessible
for disks you've deleted.Location:
column and confirm that is the disk you expect to be deletedUUID:
field and copy the uuid.VBoxManage closemedium disk $(uuid)
VBoxManage list hdds
# UUID: 01d5ccb5-2319-4e9c-bd76-daaaceffce53
# Parent UUID: base
# State: inaccessible
# Type: normal (base)
# Location: /Users/nperry/.ievms/IE6 - WinXP-disk1.vmdk
# Storage format: VMDK
# Capacity: 129948 MBytes
VBoxManage closemedium disk 01d5ccb5-2319-4e9c-bd76-daaaceffce53
Thanks @servel333, it solved the problem I've had.
The solution provided by @servel333 was exactly what I needed (as well as to delete the download itself under ~/.ievms/ ). I'd hit the issue because I had removed the VM from VirtualBox without deleting all files, so it remained in that inaccessible state despite not being listed in the UI.
You can also remove the inaccessible media from VirtualBox with File -> Virtual Media Manager.
Hi, thanks for this incredible script. I have been using VMs installed years ago for a long time. Today I tried reinstalling them with mixed results.
First there must be some naming problem, often the source image file is different from the path filename (on all or most VMs):
Then it has problems detecting the shutdown:
But I heard a chime so it might have already shut down.
One more problem is that I can't seem to be able to installe IE9 - Win7:
(removing IE9 - Win7-disk1.vmdk is of no help)