Hi.
I had a VM running on a laptop where the CPU-fan died on me so I can't shut the machine down or export it until the replacement arrives (maybe a month or so...)
I tried copying the files to a new machine but when I just double click the .vbox, I get the dreaded
Konnte die virtuelle Maschine in C:/Users/wieke/VirtualBox VMs/CT3Wieke_EBM/CT3Wieke_EBM.vbox nicht öffnen.
Medium 'C:\Users\wieke\VirtualBox VMs\CT3Wieke_EBM\CT3Wieke.vdi' cannot be closed because it is still attached to 1 virtual machines.
Fehlercode:VBOX_E_OBJECT_IN_USE (0x80BB000C)
Komponente:Medium
Interface:IMedium {05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac}
Callee:IVirtualBox {fafa4e17-1ee2-4905-a10e-fe7c18bf5554}
Callee RC:VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
Message.
Is there any workaround for that?
Maybe I could export all the relevant information from the .vbox into a new vm, change the uuid of the vdi and start it in a new vm.
It's probably OK to lose the running snapshot of the vm, but I need the file system like it was in my previous machine...
Copied running VM to new Computer => "cannot be closed b..."
-
OracleNickName
- Posts: 2
- Joined: 14. Jan 2014, 12:46
Copied running VM to new Computer => "cannot be closed b..."
- Attachments
-
CT3Wieke_EBM.vbox.txt- (22.01 KiB) Downloaded 4 times
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Copied running VM to new Computer => "cannot be closed b
What files did you copy?
If there's a saved state associated with this VM then you might try discarding it. They aren't intended to be portable.
If there's a saved state associated with this VM then you might try discarding it. They aren't intended to be portable.
-
OracleNickName
- Posts: 2
- Joined: 14. Jan 2014, 12:46
Re: Copied running VM to new Computer => "cannot be closed b
I copied the entire subdirectory of "VirtualBox VMs" with the name of my vm from the old computer's hd to my new computer's "VirtualBox VMs" directory.
Luckily, I found an older backup of the vm and that one wasn't currently running.
I copied that one and replaced the harddisk file with the one from the running vm and now it's working.
Luckily, I found an older backup of the vm and that one wasn't currently running.
I copied that one and replaced the harddisk file with the one from the running vm and now it's working.