Mathieu Tarral
Mathieu Tarral
I've just realized that we have the same error in our Travis CI recently: https://travis-ci.com/github/KVM-VMI/kvm-vmi/jobs/494684290#L1103
Actually the failure is very early in the playbook, when running `apt-get dist-upgrade`. I will try a PR bumping the vagrant box version, see if it solves the issue
> I assume that vagrant box = host system? No actually the vagrant box is the VM in which KVM-VMI will be installed. So it doesn't matter what happens on...
> I couldn't get past the initial ramdisk part of boot. could you elaborate ? the kernel you compiled wasn't bootable ? In the meantime, I just merged the PR...
just pull the latest changes on master, the vagrantfile will be updated and vagrant up will download the new box
Yes, please, with as details as you can get to investigate
Then i can't help you more than that. Just stick with the vagrant based setup in this case
If you need more direct assistance while setting up kvm-vmi and playing with libkvmi, i advise you to join our Slack community: https://kvm-vmi.herokuapp.com/
Regarding libvmi, there is an integration for [kvmi-v6](https://github.com/KVM-VMI/libvmi/tree/kvmi) and [kvmi-v7](https://github.com/mtarral/libvmi/tree/kvmi_v7) Also there is an opened pull request to integrate the new KVM driver in upstream libvmi: https://github.com/libvmi/libvmi/pull/844 I hope this...
@allewwaly Nitro is a deprecated project. if you want to revive it you will likely need to use libvmi exclusively and put breakpoints on the syscall handlers.