@@ -171,20 +171,24 @@ tux > sudo zypper in SLES15-Migration
171171----
172172+
173173The `run_migration` uses `kexec` to boot into the kernel delivered with the
174- upgrade image delivered by the SLES15-Migration package. Once this system
175- is live after the `kexec` the distribution migration process is automatically
176- started. However, `kexec` is not supported and does not function in certain
177- conditions. For example, the `run_migration` utility does not work in Xen
178- based environments or when kernel keys change.
174+ upgrade image delivered by the SLES{$VERSION}-Migration package.
179175+
180- If kexec causes a kernel panic this can cause the system to hang and the
181- distribution migration to fail. In that case refer to this TID:
182- https://www.suse.com/support/kb/doc/?id=000019733
183- And set the "soft_reboot" customization option:
176+ On the s390x architecture this is the only package available and the
177+ the `run_migration` method is the only option to start the migration process.
178+ The migration process starts automatically once the `run_migration` command
179+ is issued.
180+ +
181+ On all other architectures the `kexec`, i.e. use of `run_migration` is not
182+ supported. This path does not work in certain conditions, for example
183+ on Xen based environments or when kernel keys change.
184+ +
185+ By default this method is disabled. Enabling soft reboot behavior via kexec
186+ requires an explicit configuration change on all architectures except s390x
187+ by setting the "soft_reboot" customization option:
184188+
185189[listing]
186190----
187- echo "soft_reboot: false " >> /etc/sle-migration-service.yml
191+ echo "soft_reboot: true " >> /etc/sle-migration-service.yml
188192----
189193
190194Option 2 - Trigger via reboot::
@@ -303,9 +307,10 @@ debug: true|false
303307----
304308
305309Configure Reboot Method::
306- By default, the migration system uses `kexec` to boot back into the host
307- system once migration is complete. If this is in any way problematic,
308- a regular `reboot` can be requested by setting `soft_reboot: false`.
310+ By default, the migration system uses a full reboot to boot back into the
311+ host system once migration is complete. It is possible to configure the
312+ migration system to use `kexec`, i.e. use a soft reboot by setting
313+ `soft_reboot: true` in the configuration. A soft reboot may trigger issues.
309314+
310315[listing]
311316----
0 commit comments