The extra grub menu written by the DMS system uses
insmod loopback
To use the grub loopback feature. However if the system was configured to boot in secure boot mode via shim it was not possible to load that module. In this case customers can activate the migration only via run_migration and that requires kexec to work in the respective environment.
As of now we don't know why the loading of the module failed in secure boot mode. This issue was a consequence of the investigations in #175
The extra grub menu written by the DMS system uses
To use the grub loopback feature. However if the system was configured to boot in secure boot mode via shim it was not possible to load that module. In this case customers can activate the migration only via run_migration and that requires kexec to work in the respective environment.
As of now we don't know why the loading of the module failed in secure boot mode. This issue was a consequence of the investigations in #175