【Problem description】
VM is started and then automatically stops after the VM OS Kernel upgrade.
【Problem analysis】
1. Log in to the FusionCompute web client. You can find that the VM automatically stops immediately after the VM startup task is complete. The task center on the web client shows that the VM is scheduled by the system.
2. Check the libvirt log. The result shows that the VM triggers the shutdown _poweroff task.
【Solution description】
1. Bind the VM to a fixed host and start the VM on the FusionCompute web client. After the VM is started, log in to the background of the host immediately and run the virsh suspend ID command to suspend the VM. Note: The ID is the same as that displayed in the output of the xl list command.
2. Log in to the FusionCompute web client, open the VNC window of the VM, log in to the background of the host where the VM is located, run the virsh resume ID command to restore the suspended VM, and go back to the VNC window immediately. Press and hold the e key until the kernel loading option page is displayed. The system shows that the VM has two kernels.
3. Select the non-default kernel, log in to the VM, and change the default value in the /boot/grub/menu.lst file of the VM to enable it to boot from the other kernel.
[Conclusion]
The OS kernel has been upgraded by the customer, causing compatibility issues. As a result, the OS automatically stops when the OS loads the kernel.
