From 3e4c5a6261770bced301b5e74233e7866166ea5b Mon Sep 17 00:00:00 2001 From: Christian Krinitsin Date: Sun, 1 Jun 2025 21:35:14 +0200 Subject: clean up repository --- .../target_missing/host_missing/accel_missing/1516 | 39 ---------------------- 1 file changed, 39 deletions(-) delete mode 100644 gitlab/issues_text/target_missing/host_missing/accel_missing/1516 (limited to 'gitlab/issues_text/target_missing/host_missing/accel_missing/1516') diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1516 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1516 deleted file mode 100644 index 4e5213df8..000000000 --- a/gitlab/issues_text/target_missing/host_missing/accel_missing/1516 +++ /dev/null @@ -1,39 +0,0 @@ -QEMU does not reload kernel image on guest reboot (direct kernel boot) -Description of problem: -I am using virtiofs as root filesystem with QEMU direct kernel boot. The kernel is loaded from the guests directory structure that is exported from the host. - -The problem is that QEMU does not reload the kernel image file from disk during a guest reboot. This means it is not possible to update the kernel from inside the guest and do a simple reboot to load it. A full power cycle of the guest is required to load the updated kernel image. -Steps to reproduce: -1. Migrate a Linux guest to virtiofs as root fs. -2. Enable QEMU direct kernel boot and point to guest's kernel in the exported root filesystem. -3. Boot. -4. Update the kernel inside the guest. Overwrite the existing kernel image -5. Issue `reboot` inside the guest. -6. When the guest reboots, the old kernel is still booted, even though the image file was overwritten. -7. Issue `poweroff` inside the guest. -8. Issue `virsh start ` -9. Now the new kernel image is booted. -Additional information: -XML: -``` -hvm - /media/vm/libvirt/images/alpine-q/root/boot/vmlinuz-virt - /media/vm/libvirt/images/alpine-q/root/boot/initramfs-virt - rootfstype=virtiofs root=root rw - - - - -... - - - - - - - - - -
- -``` -- cgit 1.4.1