diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 19:39:53 +0200 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 19:39:53 +0200 |
| commit | dee4dcba78baf712cab403d47d9db319ab7f95d6 (patch) | |
| tree | 418478faf06786701a56268672f73d6b0b4eb239 /results/classifier/108/boot/1516 | |
| parent | 4d9e26c0333abd39bdbd039dcdb30ed429c475ba (diff) | |
| download | emulator-bug-study-dee4dcba78baf712cab403d47d9db319ab7f95d6.tar.gz emulator-bug-study-dee4dcba78baf712cab403d47d9db319ab7f95d6.zip | |
restructure results
Diffstat (limited to 'results/classifier/108/boot/1516')
| -rw-r--r-- | results/classifier/108/boot/1516 | 54 |
1 files changed, 0 insertions, 54 deletions
diff --git a/results/classifier/108/boot/1516 b/results/classifier/108/boot/1516 deleted file mode 100644 index 99c1ac67..00000000 --- a/results/classifier/108/boot/1516 +++ /dev/null @@ -1,54 +0,0 @@ -boot: 0.931 -files: 0.881 -device: 0.819 -graphic: 0.754 -performance: 0.744 -semantic: 0.729 -PID: 0.646 -vnc: 0.610 -permissions: 0.604 -network: 0.424 -debug: 0.422 -socket: 0.388 -KVM: 0.366 -other: 0.225 - -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 <guest-vm>` -9. Now the new kernel image is booted. -Additional information: -XML: -``` -<type arch='x86_64' machine='pc-q35-7.0'>hvm</type> - <kernel>/media/vm/libvirt/images/alpine-q/root/boot/vmlinuz-virt</kernel> - <initrd>/media/vm/libvirt/images/alpine-q/root/boot/initramfs-virt</initrd> - <cmdline>rootfstype=virtiofs root=root rw</cmdline> - <boot dev='hd'/> - <bootmenu enable='no'/> - </os> - -... - - <filesystem type='mount' accessmode='passthrough'> - <driver type='virtiofs'/> - <binary path='/usr/libexec/virtiofsd' xattr='on'> - <cache mode='always'/> - <lock posix='on' flock='on'/> - </binary> - <source dir='/media/vm/libvirt/images/alpine-q/root'/> - <target dir='root'/> - <address type='pci' domain='0x0000' bus='0x09' slot='0x00' function='0x0'/> - </filesystem> -``` |