Tamas K Lengyel
Tamas K Lengyel
AFAICT the trick is just going to be compiling all libraries statically into the final IncludeOS binary. For the most part this should be straight forward, although I haven't yet...
Something is weird, QEMU tells me `VMI: missing kernel built with CONFIG_KVM_INTROSPECTION` even after booting the v12 kernel with `kvm.introspection=1`.
Ah yes, that was it :)
@adlazar Any chance you could rebase your libvmi branch on the latest master of libvmi? I tried to do that but I'm getting: ``` -o libvmi/driver/kvm/.libs/libvmi_la-kvm_events.o libvmi/driver/kvm/kvm_events.c: In function ‘process_cpuid’:...
Also, is `KVMI_GET_MAX_GFN` no longer available? That's going to be an issue since LibVMI needs that to initialize.
@adlazar LibVMI right now needs to know the max address or have a complete memory map to determine if a requested access is sane or not. I'm not actually sure...
To get LibVMI working it still needs this: https://github.com/libvmi/libvmi/commit/8d0fabf01305faffaf3acbbc82e334a03bd59cfa
Ah, didn't catch those commits. Is the QEMU patch going to work even if the guest is booted with ovmf and there is no e820 map?
@adlazar is remote mapping no longer available in the 5.15 kernel?
I don't know what's the right move here then, I don't see a reason to move to v12 if it has less features. If v12 gets merged to upstream that's...