KVM Import VM to keep activation

[Marc Allard]

Hello,

I would like to know if it is possible to import existing virtual machines (debian) into a KVM guest.
I see no option to import a VM, so I decided to export the config after creating a VM, but I see no guid in the two vm tables from the db.
Is there a way to modify the guid to keep the activation of windows (there must me something or the activation would be lost with an update of scale (or a restoration from config)?

Thank you

 

[otpi]

Maybe not what you're looking for, but I installed Proxmox in a VM on Scale. Added the Proxmox-VM to my cluster and migrated my Win10VM over to my TNScale box. (Inception)

 

[Marc Allard]

Hello,

Thank you for the idea. If I understand correctly, I can import my VM to the proxmox and after that it will run from proxmox inside Scale?
At the moment my scale is in a VM so I am not sure I can make a test (triple layer of virtualisation seems a lot) but it is interesting

 

[otpi]

This YT series (ep 14-15-16) shows the process, but you can see the "live" migration here: https://youtu.be/QWyLilz1RqU?t=753

Edit: Running Proxmox inside Scale might be really dumb... I take no responsibility

 

[Marc Allard]

Thank you.
I hope there is a way to change the UUID in truenas to avoid things like this (Scale ==> ProxMox==>Win10 ==> Hyper-v or sandbox) seems not efficient :) .

EDIT :
I have seen the file in
/etc/libvirt/qemu
But the UUID changes after every reboot. Does it mean that I will have to reactivate Windows at every boot?
Thank you

 

[otpi]

But the UUID changes after every reboot. Does it mean that I will have to reactivate Windows at every boot?

This is above my level of expertise. But that is certainly strange...

Meanwhile. I have been live migrating a win10 VM between my two proxmox nodes just fine (one bare bone amd system, and one proxmoxVM on Intel). Reboots performed on both nodes. No problems with windows activation yet. I had some internet connectivity problems at first, but it turned out to be port security on the switch (did not like that the MAC jumped between ports).