VM does not start automatically after migration

[madeus]

Hi

Virtualizer: XCP-NG
OS: Centos 8.5

After using the script and trying to start a virtual machine with the default OS: EuroLinux, the system does not start. I have to manually point to Centos Linux for the system to boot.

Besides, I don't know why the difference between version names: once is Kyiv and hostname says something else:
cat /etc/el-release
EuroLinux release 8.7 (Brussels)

[AlexBaranowski]

HI,

We release kernel built with wrong el-release on the build host. The name of the kernel on the command line does not impact the functionality itself. I'm sorry for the inconvenience and confusion.

Does your XCP-NG have the secure boot enabled? https://xcp-ng.org/blog/2021/01/28/guest-uefi-secure-boot/? If so could you disable Secure Boot for this machine?

Best,
Alex

[madeus]

Hi,

Thanks for the clarification. Nevertheless, I had to recreate the VM from a snapshot. But I will come back to this script later. ;-)

P.s. And for information only, Active Backup for Business (Synology) does not work with EuroLinux.

[AlexBaranowski]

@aronowski could you look into it?

[aronowski]

@madeus Please provide more information on what it means that the system does not start. Are there any messages that will be indispensable for solving this issue?

[madeus]

Hi,
I installed a new virtual machine (Centos 8.5.2111). I ran the script. The machine boots up fine but there is still a discrepancy between what GRUB shows and what cat /etc/el-release shows.

This is of course not a problem, the important thing is that the machine starts correctly.

The question is, isn't the problem the number of kernel versions installed? See previous screenshots. I will check the script again on the machine where it failed previously and let you know.

[madeus]

Welcome back.

The problem has returned. On the next machine, I deleted all previous kernel versions except EuroLinux and one Centos. Unfortunately, the VM does not boot on the EuroLinux kernel. I need to point Centos manually.

There is nothing interesting in the XCP-ng logs except maybe this:

Mar 9 18:11:08 xcp-ng-2 xapi: [ info||79638 |sm_exec D:cb4ed560db4d|xapi_session] Session.destroy trackid=db078a41d1d5b92caccdb574e075f54f
Mar 9 18:11:08 xcp-ng-2 xapi: [debug||79638 ||dummytaskhelper] task VDI.detach D:6f342396f713 created by task O:dp_destroy
Mar 9 18:11:08 xcp-ng-2 xapi: [debug||79599 ||storage_impl] dbg:dp_destroy dp:vbd/27/xvda sr:fecbaff8-e697-a56f-595e-7e936349f231 vdi:f999ca36-8fbd-47f4-95bb-2c9e9956bab5 superstate:detached
Mar 9 18:11:08 xcp-ng-2 xapi: [debug||79599 ||storage_impl] [destroy_sr] Filtered VDI count:0
Mar 9 18:11:08 xcp-ng-2 xapi: message repeated 6 times: [ [debug||79599 ||storage_impl] [destroy_sr] Filtered VDI count:0]
Mar 9 18:11:08 xcp-ng-2 xenopsd-xc: [debug||32 |Parallel:task=234137.atoms=2.(VBD.unplug vm=e583e880-2ff7-c80f-8c40-4bdfb1f4e5d5)|xenops_server] VBD_DB.signal e583e880-2ff7-c80f-8c40-4bdfb1f4e5d5.xvda
Mar 9 18:11:08 xcp-ng-2 xenopsd-xc: [debug||32 |Parallel:task=234137.atoms=2.(VBD.unplug vm=e583e880-2ff7-c80f-8c40-4bdfb1f4e5d5)|task_server] Task 234138 completed; duration = 1
Mar 9 18:11:08 xcp-ng-2 xenopsd-xc: [debug||32 ||xenops_server] TASK.signal 234138 = ["Completed",{"duration":1.4098930358886719}]
Mar 9 18:11:08 xcp-ng-2 xenopsd-xc: [debug||40 ||xenops_server] end_Parallel:task=234137.atoms=2.(VBD.unplug vm=e583e880-2ff7-c80f-8c40-4bdfb1f4e5d5)
Mar 9 18:11:08 xcp-ng-2 xenopsd-xc: [debug||40 ||xenops_server] TASK.signal 234137 (object deleted)
Mar 9 18:11:08 xcp-ng-2 xenopsd-xc: [debug||40 ||xenops_server] Performing: ["VIF_unplug",[["e583e880-2ff7-c80f-8c40-4bdfb1f4e5d5","0"],true]]
Mar 9 18:11:08 xcp-ng-2 xenopsd-xc: [debug||40 ||xenops_server] VIF.unplug e583e880-2ff7-c80f-8c40-4bdfb1f4e5d5.0
Mar 9 18:11:08 xcp-ng-2 xapi: [debug||162 |org.xen.xapi.xenops.classic events D:94f5d5261f3e|xenops] Processing event: ["Vbd",["e583e880-2ff7-c80f-8c40-4bdfb1f4e5d5","xvda"]]
Mar 9 18:11:08 xcp-ng-2 xapi: [debug||162 |org.xen.xapi.xenops.classic events D:94f5d5261f3e|xenops] xenops event on VBD e583e880-2ff7-c80f-8c40-4bdfb1f4e5d5.xvda
Mar 9 18:11:08 xcp-ng-2 xenopsd-xc: [debug||40 ||xenops] Device.Generic.hard_shutdown_request frontend (domid=27 | kind=vif | devid=0); backend (domid=0 | kind=vif | devid=0)
Mar 9 18:11:08 xcp-ng-2 xenopsd-xc: [debug||40 ||xenops] xenstore-write /local/domain/0/backend/vif/27/0/online = 0
Mar 9 18:11:08 xcp-ng-2 xenopsd-xc: [debug||40 ||xenops] Device.Generic.hard_shutdown about to blow away frontend
Mar 9 18:11:08 xcp-ng-2 xenopsd-xc: [debug||40 ||xenops] xenstore-rm /local/domain/27/device/vif/0
Mar 9 18:11:08 xcp-ng-2 xenopsd-xc: [debug||40 ||xenops] xenstore-rm /xenops/domain/27/device/vif/0
Mar 9 18:11:08 xcp-ng-2 xenopsd-xc: [debug||436068 |org.xen.xapi.xenops.classic events D:94f5d5261f3e|xenops_server] VBD.stat e583e880-2ff7-c80f-8c40-4bdfb1f4e5d5.xvda
Mar 9 18:11:08 xcp-ng-2 xenopsd-xc: [debug||436068 |org.xen.xapi.xenops.classic events D:94f5d5261f3e|xenops] VM = e583e880-2ff7-c80f-8c40-4bdfb1f4e5d5; domid = 27; Device is not active: kind = vbd3; id = xvda; active devices = [ ]
Mar 9 18:11:08 xcp-ng-2 xapi: [debug||162 |org.xen.xapi.xenops.classic events D:94f5d5261f3e|xenops] VM e583e880-2ff7-c80f-8c40-4bdfb1f4e5d5 VBD userdevices = [ 3; 0 ]
Mar 9 18:11:08 xcp-ng-2 xapi: [debug||162 |org.xen.xapi.xenops.classic events D:94f5d5261f3e|xenops] VBD e583e880-2ff7-c80f-8c40-4bdfb1f4e5d5.xvda matched device 0
Mar 9 18:11:08 xcp-ng-2 xapi: [debug||162 |org.xen.xapi.xenops.classic events D:94f5d5261f3e|xenops] xenopsd event: Updating VBD e583e880-2ff7-c80f-8c40-4bdfb1f4e5d5.xvda device <- xvda; currently_attached <- true

Where: e583e880-2ff7-c80f-8c40-4bdfb1f4e5d5 is the UUID of the virtual machine.