Open allewwaly opened 4 years ago
Hi,
First, Nitro is not maintained anymore, and I haven't had a working configuration of it since 2 years.
That being said, nitro_kmod shouldn't be used.
everything you need is being tracked by the main KVM-VMI repo.
checkout the nitro
branch, and git submodule update
, and go to kvm to recompile the kernel.
But, as I said, I can't confirm if this will work as I'm not maintaining it. Also, you don't need to run it on Ubuntu 14.04 (!)
I don't need kvm-vmi, just the kernel used to run nitro, is there any backups?
Kvm-vmi is cersioning the kernel as submodule
To repeat nitro, I've installed an old version of libvmi, nitro-kmod_build, and nitro. Everything works, except that no events are captured as described. This is what I get while running
If using the nitro version of libvmi, following problems encounterd:
I can't even use native libvmi examples using the above version of libvmi, as it shows:
I've tested it on ubuntu14.04 to meet the requirements of nitro-kmod, gcc, python, and so on. It's really unclear what's the exactly environment to repeat the results described in Readme.
So my question is:
I need to repeat the result of nitro to compare it with a new VMI tool, so it will be greatly appreciated if anyone who successfully configured nitro can guide me through it.