handling nvram config when using virsh instead of webGUI to define existing VMs

Hi,

when you create a (Win10) VM with the webGUI it also creates a file in the /etc/libvirt/qemu/nvram folder.

That file's name is based on the UUID of the VM (and then '_VARS-pure-efi.fd'). It is then referenced in within the xml config of the VM.

When I keep a fully installed and configured VM on my storage server and copy it to my VM server I use virsh define to make the VM available based on the xml file (I created earlier using virsh dumpxml).

That works fine but that file in the nvram folder does not get created and so the VM won't start.

My current solution:

Together with the disk image files and the config xml I also keep a copy of that _VARS-pure-efi.fd file which was created via the webGUI initially.

So when I copy a VM back to the VM server, before I run virsh define I manually copy that _VARS-pure-efi.fd file to the folder

/etc/libvirt/qemu/nvram.

This works well so far.

But I would like to know if there is a better solution.

Thanks & regards,

Marcel