-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vagrant up error #6
Comments
Hi ! I already had this error before. The action that is no detected is related to the Either install a recent Ansible or install it from pip, in a virtualenv. |
Hi Wenzel!
Maybe I've got this error cause we have duplicate key in kvm.yml:
How can I fix this? |
hi @aghamir my bad, it's my fault here, i wanted to make a quick fix and i should have retested the entire playbook. Thanks for trying it on vagrant ! |
OK. I saw your branch(refactor-vagrant) that fixes this. Thanks you can close this issue if you want. |
Hi Mathieu!
|
On which branch are you ? because i don't see any git conflict pushed on the This is how you source tree branches should look like:
|
Are you using |
I was on master for kvm. |
@aghamir if that could help you, i just merged a new branch providing ready to use debian packages for KVM, QEMU and libvmi. Maybe you can check it out ? it's on |
Hi,Wenzel! |
Hi @bigbigbanana, the original Nitro project is not maintained anymore. The results you see are the raw registry values for each syscall and their translation is a big effort we are trying to carry on in the KVM-VMI project. There is no technical paper written yet as this project is under heavy development. I would recommend you to read @pfohjo original dissertation about Nitro: https://www.sec.in.tum.de/assets/Uploads/pfoh2013b.pdf Moreover, technical understanding of low level OS mechanism and x86 architecture is highly recommended. Nitro supports Linux OS as well. As usual, the real issue is the symbols translations. There is an ongoing effort within the project to fill this gap as well: KVM-VMI/nitro#13 One more thing: I would like to kindly ask you not to hijack other issues with non-related question. If you have some question please open a dedicated ticket in the correct repository (in this case: https://github.com/KVM-VMI/nitro) |
Hi @aghamir , Do you still any issues with Thanks. |
Hi @Wenzel , |
I am Ajay, I have the same above question asked by [email protected]. I am expecting an answer related to KVM-VMI system call trace. I worked on the Nitro 2 year before unfortunately, I couldn't continue to work furthermore on this project for 2 more years. I have used the older version of this Nitro in my experimental testbed to obtained the system call trace (named by @pfohjo) on both Windows-7 and Ubuntu 14.o4 system.(Snapshot attached). Currently, I am working on the improved fork of Nitro such as KVM-VMI (https://github.com/KVM-VMI/kvm-vmi) to extract a system call on the Windows 10 and Ubuntu 14.04 System. I understand the response provided @noxdafox to the above question. But generally, system call trace appears as below in Xen Hypervisor based system call extraction for Windows. How the older version Nitro captured system call are different from the above system call trace captured by Xen hypervisor through LibVMI.
|
@ajaymas the comment you provided here is not related to the vagrant up issue. KVM-VMI has 2 versions, as explicitely said in the README:
|
I am installing KVM-VM in the KVM Hypervisor with target introspection as Windows 10. I have installed Ansible version 2.6.0. (latest) I got this error. I am trying to use Windows 10 as my introspection system to fetch system call trace. Is anybody used Windows 10 in KVM-VMI..? ajay@ubuntu-kvm3:~/kvm-vmi-master/vagrant$ vagrant up --provider=libvirt ajay@ubuntu-kvm3:~/kvm-vmi-master/vagrant$ vagrant provision
PLAY [default] ***************************************************************** TASK [Gathering Facts] ********************************************************* TASK [add backports] *********************************************************** TASK [add backports sources] *************************************************** TASK [update cache] ************************************************************ PLAY RECAP ********************************************************************* Ansible failed to complete successfully. Any error output should be |
I am training to build KVM-VMI through the master branch, all the dependencies are installed well, However, at last, I am getting this error Could you please advise me. |
TASK [build test vm] *********************************************************** PLAY RECAP ********************************************************************* Ansible failed to complete successfully. Any error output should be |
I've got this error when I run vagrant up --provider=libvirt:
The text was updated successfully, but these errors were encountered: