Unable to restore vm: Attempt to restore VM with qid that already exist in the collection

[fer...@openmailbox.org]

Hi,
I was moving VM from second pc. I got some errors, So I got a fresh installed version of qubes 3.2 here.

I am trying to restore and got this error: Attempt to restore VM with qid that already exist in the collection

It is possible to clean the "collection"? I'm not afraid of losing my existing VM since I have backed up.

Thanks you for your help

[Yuraeitha]

Run
'qvm-ls --format full'
in your dom9 terminal, and read the output, here you got all your existing QID's listed.

I'm no expert, but I belive QID stands for Qubes Identification, and XID stands for Xen Identification.

Now the question is probably how to attain the QID numbwr of the AppVM you're trying to restore, is there any chance you can still access it on your other Qubes machine to read the QID from the above command?

Then compare the QID, and see if you can find a match.

Though, I'm really not sure if these QID's or XID's are fixed or flexible, but it appears like they serve somewhat the same purpose such as UUID does for drives and partitions, just for virtualization instead, possibly, it's a guess.

If lucky, this can help, if not, someone more knowledgeable will have to step in to provide better answers.

[Yuraeitha]

On Sunday, November 12, 2017 at 4:46:39 PM UTC, fer...@openmailbox.org wrote:

It could also be a bug, since these QID's are small numbers, they do not appear to be something akin to fingerprints like UUID's are, yet still seem like serving a similar purpose. The number is too small to be something permanently fixed when restored from i.e. backup. It's odd that the Qubes backup restore does not give it a new QID number.