Page 1 of 1
error opening restored image
Posted: 21. Nov 2015, 23:50
by [icarus]
hi all
I have problems opening an imported (pre exported by me) virtualized service
Fallo al abrir una sesión para la máquina virtual linux-lite-2.
A new node couldn't be inserted because one with the same name exists. (VERR_CFGM_NODE_EXISTS).
Código Resultado: E_FAIL (0x80004005)
Componente: ConsoleWrap
Interfaz: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Windows 10
VirtualBox 5.0.8 r103449
Re: error opening restored image
Posted: 22. Nov 2015, 12:05
by mpack
Well, if the error message is to be believed, you already have that VM (or less likely: another with exactly the same name).
Hopefully you aren't using export/import for backup/restore to the same host, since that has several issues.
Re: error opening restored image
Posted: 22. Nov 2015, 14:13
by [icarus]
mpack wrote:Well, if the error message is to be believed, you already have that VM (or less likely: another with exactly the same name).
Hopefully you aren't using export/import for backup/restore to the same host, since that has several issues.
is there a way to see/check/show you that I have no other configuration with the same name?
the first name was linux-lite, I did an export to keep everything configured as base
then the system crashed, I remove the machine and import the saved one
when I first have that error, I read about it in this forum so I renamed
all files name where changed to "-2", even the disk name had changed to linux-lite-2.6-x64-mcrose-disk1.vmdk
so I don't know where to look at
Re: error opening restored image
Posted: 22. Nov 2015, 15:32
by mpack
Renaming the files using the host is not the correct thing to do. The media files remain registered with their original names, and its the register conflict that VirtualBox is reporting.
The only way to unregister a VM is to remove it. You may have to restore the original naming before you can do that.
Re: error opening restored image
Posted: 22. Nov 2015, 23:16
by [icarus]
mpack wrote:Renaming the files using the host is not the correct thing to do. The media files remain registered with their original names, and its the register conflict that VirtualBox is reporting.
The only way to unregister a VM is to remove it. You may have to restore the original naming before you can do that.
I just did it again, remove, import, same error
I guess I have to forget about this file
thanks any way