You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unikraft's KVM platform library crashes early during boot on x86_64 with TCG (no KVM virtualization) with Paging API enabled. This only happens with QEMU pc models starting from 7.1: pc-i440fx-7.1, pc-i440fx-7.2, ...
I could not reproduce the crash with KVM acceleration (Tested on GCP Debian11 Linux: 5.10.0-23-cloud-amd64).
A workaround for avoiding the crash (failing assertion) can be achieved by using an QEMU pc machine model < 7.1: like pc-i440fx-7.0.
Steps to reproduce
It can be reproduced just with Unikraft (x86_64) and the following settings. The important one that causes the crash is CONFIG_PAGING-y:
CONFIG_PLAT_KVM=y
# CONFIG_KVM_KERNEL_VGA_CONSOLE is not set
# CONFIG_KVM_DEBUG_VGA_CONSOLE is not set
# CONFIG_KVM_PCI is not set
CONFIG_PAGING=y
CONFIG_LIBUKDEBUG_PRINTK_INFO=y
CONFIG_LIBUKDEBUG_PRINTD=y
QEMU (must be version >= 7.1) can be launched with:
Limits QEMU PC machine model up to version 7.0 (pc-i440fx-7.0) for
x86. This is primarily done to keep Unikraft compatibility with TCG.
GitHub-Issue: unikraft#1040
Signed-off-by: Simon Kuenzer <simon@unikraft.io>
Limits QEMU PC machine model up to version 7.0 (pc-i440fx-7.0) for
x86. This is primarily done to keep Unikraft compatibility with TCG.
GitHub-Issue: unikraft#1040
Signed-off-by: Simon Kuenzer <simon@unikraft.io>
Limits QEMU PC machine model up to version 7.0 (pc-i440fx-7.0) for
x86. This is primarily done to keep Unikraft compatibility with TCG.
GitHub-Issue: #1040
Signed-off-by: Simon Kuenzer <simon@unikraft.io>
Reviewed-by: Stefan Jumarea <stefanjumarea02@gmail.com>
Approved-by: Razvan Deaconescu <razvand@unikraft.io>
Tested-by: Unikraft CI <monkey@unikraft.io>
GitHub-Closes: #1041
Describe the bug
Unikraft's KVM platform library crashes early during boot on x86_64 with TCG (no KVM virtualization) with Paging API enabled. This only happens with QEMU pc models starting from 7.1:
pc-i440fx-7.1
,pc-i440fx-7.2
, ...I could not reproduce the crash with KVM acceleration (Tested on GCP Debian11 Linux:
5.10.0-23-cloud-amd64
).A workaround for avoiding the crash (failing assertion) can be achieved by using an QEMU
pc
machine model < 7.1: likepc-i440fx-7.0
.Steps to reproduce
It can be reproduced just with Unikraft (x86_64) and the following settings. The important one that causes the crash is
CONFIG_PAGING-y
:QEMU (must be version >= 7.1) can be launched with:
Expected behavior
The crash should not appear and the system should continue booting further, up to the application.
Which architectures were you using or does this bug affect?
x86_64
Which platforms were you using or does this bug affect?
kvm
Relevant log output
The text was updated successfully, but these errors were encountered: