Mathieu Tarral
Mathieu Tarral
Hi Samuel, You need to take also the pull request by @adlazar on `kvm` :) https://github.com/KVM-VMI/kvm/pull/15/files#diff-5e1c02c0a26fb24d0a3500863a692fe5R6
It's my mistake, i should have told you !
Hi @halfadmin, That's a good question. At the moment kvm-vmi only supports QEMU/KVM. KVMi (the new KVM subsystem for introspection) opens new ioctls and expands the KVM interface. The QEMU...
Thanks @mdontu. Also cc @andreeaflorescu and @aghecenco from Firecracker's team, for your insights, if you are interested.
hi @wangbaba523 , If I'm not mistaken, `KVM_INTROSPECTION_HOOK` refers to the bitdefender KVMI subsystem, the new API that is currently maintained by this project `KVM_NITRO_ATTACH_VM` is refering to the Nitro...
@wangbaba523 from what I understand you are trying to use both Nitro and KVMi and these are 2 incompatibles APIs. What you need to do is to rebuild the Nitro...
Hi, the libvmi documentation about KVM should not be used, as it reference the legacy kvm driver. you don't need that `-s` command line for GDB access. your `vmi-process-list` binary...
I don't know either. You need to enable libvmi debug output
> Also, I would like to see the error content with debugging enabled, but it does not display properly because of the bad way. I don't understand what you mean....
You don't need to run cmake as sudo. Did you rebuild and reinstall libvmi ?