Vagrant up error

[aghamir]

I've got this error when I run vagrant up --provider=libvirt:

TASK [include] *****************************************************************
fatal: [default]: FAILED! => {"failed": true, "reason": "ERROR! no action detected in task\n\nThe error appears to have been in '/home/mohammad/Desktop/kvm-vmi-wenzel/kvm-vmi/vagrant/provision/remote.yml': line 14, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: restart SSH server\n  ^ here\n"}

PLAY RECAP *********************************************************************
default                    : ok=1    changed=0    unreachable=0    failed=1   

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

[Wenzel]

Hi !

I already had this error before. You have to use an up to date ansible.

The action that is no detected is related to the systemd module, which is only present in ansible 2.2

Either install a recent Ansible or install it from pip, in a virtualenv.

[aghamir]

Hi Wenzel! Thank you very much. I solved this by upgrading my ansible. I've got other error during vagrant up. fatal: [default]: FAILED! => {"changed": false, "failed": true, "module_stderr": "Shared connection to 192.168.121.175 closed.\r\n", "module_stdout": "Traceback (most recent call last):\r\n File \"/tmp/ansible_Lpnhkv/ansible_module_command.py\", line 220, in <module>\r\n main()\r\n File \"/tmp/ansible_Lpnhkv/ansible_module_command.py\", line 163, in main\r\n os.chdir(chdir)\r\nOSError: [Errno 2] No such file or directory: '/data/src/linux-source-4.9'\r\n", "msg": "MODULE FAILURE", "rc": 0} I've got also a warning that said:

[WARNING]: While constructing a mapping from /home/mohammad/Desktop/kvm-vmi-
wenzel/kvm-vmi/vagrant/provision/kvm.yml, line 66, column 5, found a duplicate
dict key (chdir). Using last defined value only.

Maybe I've got this error cause we have duplicate key in kvm.yml:

- name: compile kernel
  command: make -j4 bzImage
  args:
    chdir: "{{ root_dir }}/kvm"
    chdir: /data/src/linux-source-4.9
  become: false

How can I fix this?

[Wenzel]

hi @aghamir

my bad, it's my fault here, i wanted to make a quick fix and i should have retested the entire playbook. I just fixed it now. you can pull master and retry. :)

Thanks for trying it on vagrant !

[aghamir]

OK. I saw your branch(refactor-vagrant) that fixes this. Thanks you can close this issue if you want.

[aghamir]

Hi Mathieu! Can you help me with this error?

TASK [compile modules] *********************************************************
fatal: [default]: FAILED! => {"changed": true, "cmd": ["make", "-j4", "modules"], "delta": "0:02:18.544489", "end": "2017-05-30 16:08:35.679310", "failed": true, "rc": 2, "start": "2017-05-30 16:06:17.134821", "stderr": "In file included from arch/x86/kvm/../../../virt/kvm/coalesced_mmio.c:13:0:\n./include/linux/kvm_host.h:271:1: error: expected specifier-qualifier-list before '<<' token\n <<<<<<< HEAD\n ^\n./include/linux/kvm_host.h:440:1: error: expected specifier-qualifier-list before '<<' token\n <<<<<<< HEAD\n ^\nIn file included from arch/x86/kvm/../../../virt/kvm/kvm_main.c:21:0:\n./include/linux/kvm_host.h:271:1: error: expected specifier-qualifier-list before '<<' token\n <<<<<<< HEAD\n ^\n./include/linux/kvm_host.h:440:1: error: expected specifier-qualifier-list before '<<' token\n <<<<<<< HEAD\n ^\nmake[2]: *** [arch/x86/kvm/../../../virt/kvm/coalesced_mmio.o] Error 1\nmake[2]: *** Waiting for unfinished jobs....\narch/x86/kvm/../../../virt/kvm/kvm_main.c: In function 'kvm_destroy_vm_debugfs':\narch/x86/kvm/../../../virt/kvm/kvm_main.c:559:10: error: 'struct kvm' has no member named 'debugfs_dentry'\n  if (!kvm->debugfs_dentry)\n          ^\narch/x86/kvm/../../../virt/kvm/kvm_main.c:562:30: error: 'struct kvm' has no member named 'debugfs_dentry'\n  debugfs_remove_recursive(kvm->debugfs_dentry);\n                              ^\narch/x86/kvm/../../../virt/kvm/kvm_main.c:564:9: error: 'struct kvm' has no member named 'debugfs_stat_data'\n  if (kvm->debugfs_stat_data) {\n         ^\narch/x86/kvm/../../../virt/kvm/kvm_main.c:566:13: error: 'struct kvm' has no member named 'debugfs_stat_data'\n    kfree(kvm->debugfs_stat_data[i]);\n             ^\narch/x86/kvm/../../../virt/kvm/kvm_main.c:567:12: error: 'struct kvm' has no member named 'debugfs_stat_data'\n   kfree(kvm->debugfs_stat_data);\n            ^\narch/x86/kvm/../../../virt/kvm/kvm_main.c: In function 'kvm_create_vm_debugfs':\narch/x86/kvm/../../../virt/kvm/kvm_main.c:581:5: error: 'struct kvm' has no member named 'debugfs_dentry'\n  kvm->debugfs_dentry = debugfs_create_dir(dir_name,\n     ^\narch/x86/kvm/../../../virt/kvm/kvm_main.c:583:10: error: 'struct kvm' has no member named 'debugfs_dentry'\n  if (!kvm->debugfs_dentry)\n          ^\narch/x86/kvm/../../../virt/kvm/kvm_main.c:586:5: error: 'struct kvm' has no member named 'debugfs_stat_data'\n  kvm->debugfs_stat_data = kcalloc(kvm_debugfs_num_entries,\n     ^\narch/x86/kvm/../../../virt/kvm/kvm_main.c:587:18: error: 'struct kvm' has no member named 'debugfs_stat_data'\n       sizeof(*kvm->debugfs_stat_data),\n                  ^\narch/x86/kvm/../../../virt/kvm/kvm_main.c:589:10: error: 'struct kvm' has no member named 'debugfs_stat_data'\n  if (!kvm->debugfs_stat_data)\n          ^\narch/x86/kvm/../../../virt/kvm/kvm_main.c:599:6: error: 'struct kvm' has no member named 'debugfs_stat_data'\n   kvm->debugfs_stat_data[p - debugfs_entries] = stat_data;\n      ^\narch/x86/kvm/../../../virt/kvm/kvm_main.c:601:10: error: 'struct kvm' has no member named 'debugfs_dentry'\n       kvm->debugfs_dentry,\n          ^\narch/x86/kvm/../../../virt/kvm/kvm_main.c: In function 'kvm_create_vcpu_debugfs':\narch/x86/kvm/../../../virt/kvm/kvm_main.c:2420:6: error: 'struct kvm_vcpu' has no member named 'debugfs_dentry'\n  vcpu->debugfs_dentry = debugfs_create_dir(dir_name,\n      ^\narch/x86/kvm/../../../virt/kvm/kvm_main.c:2421:18: error: 'struct kvm' has no member named 'debugfs_dentry'\n         vcpu->kvm->debugfs_dentry);\n                  ^\narch/x86/kvm/../../../virt/kvm/kvm_main.c:2422:11: error: 'struct kvm_vcpu' has no member named 'debugfs_dentry'\n  if (!vcpu->debugfs_dentry)\n           ^\narch/x86/kvm/../../../virt/kvm/kvm_main.c:2427:32: error: 'struct kvm_vcpu' has no member named 'debugfs_dentry'\n   debugfs_remove_recursive(vcpu->debugfs_dentry);\n                                ^\narch/x86/kvm/../../../virt/kvm/kvm_main.c: In function 'kvm_vcpu_ioctl':\narch/x86/kvm/../../../virt/kvm/kvm_main.c:2554:1: error: expected expression before '<<' token\n <<<<<<< HEAD\n ^\narch/x86/kvm/../../../virt/kvm/kvm_main.c:2556:1: error: expected expression before '==' token\n =======\n ^\narch/x86/kvm/../../../virt/kvm/kvm_main.c: In function 'kvm_dev_ioctl_create_vm':\narch/x86/kvm/../../../virt/kvm/kvm_main.c:3285:1: error: expected expression before '<<' token\n <<<<<<< HEAD\n ^\narch/x86/kvm/../../../virt/kvm/kvm_main.c:3292:1: error: expected expression before '==' token\n =======\n ^\narch/x86/kvm/../../../virt/kvm/kvm_main.c:3295:1: error: expected expression before '>>' token\n >>>>>>> linux-vmi\n ^\narch/x86/kvm/../../../virt/kvm/kvm_main.c: In function 'kvm_init':\narch/x86/kvm/../../../virt/kvm/kvm_main.c:4066:1: warning: label 'out_undebugfs' defined but not used [-Wunused-label]\n out_undebugfs:\n ^\narch/x86/kvm/../../../virt/kvm/kvm_main.c: At top level:\narch/x86/kvm/../../../virt/kvm/kvm_main.c:555:13: warning: 'kvm_destroy_vm_debugfs' defined but not used [-Wunused-function]\n static void kvm_destroy_vm_debugfs(struct kvm *kvm)\n             ^\narch/x86/kvm/../../../virt/kvm/kvm_main.c:571:12: warning: 'kvm_create_vm_debugfs' defined but not used [-Wunused-function]\n static int kvm_create_vm_debugfs(struct kvm *kvm, int fd)\n            ^\narch/x86/kvm/../../../virt/kvm/kvm_main.c:2408:12: warning: 'kvm_create_vcpu_debugfs' defined but not used [-Wunused-function]\n static int kvm_create_vcpu_debugfs(struct kvm_vcpu *vcpu)\n            ^\narch/x86/kvm/../../../virt/kvm/kvm_main.c:3907:12: warning: 'kvm_init_debug' defined but not used [-Wunused-function]\n static int kvm_init_debug(void)\n            ^\nmake[2]: *** [arch/x86/kvm/../../../virt/kvm/kvm_main.o] Error 1\nmake[1]: *** [arch/x86/kvm] Error 2\nmake: *** [arch/x86] Error 2\nmake: *** Waiting for unfinished jobs....\nmake: *** wait: No child processes.  Stop.", "stderr_lines": ["In file included from arch/x86/kvm/../../../virt/kvm/coalesced_mmio.c:13:0:", "./include/linux/kvm_host.h:271:1: error: expected specifier-qualifier-list before '<<' token", " <<<<<<< HEAD", " ^", "./include/linux/kvm_host.h:440:1: error: expected specifier-qualifier-list before '<<' token", " <<<<<<< HEAD", " ^", "In file included from arch/x86/kvm/../../../virt/kvm/kvm_main.c:21:0:", "./include/linux/kvm_host.h:271:1: error: expected specifier-qualifier-list before '<<' token", " <<<<<<< HEAD", " ^", "./include/linux/kvm_host.h:440:1: error: expected specifier-qualifier-list before '<<' token", " <<<<<<< HEAD", " ^", "make[2]: *** [arch/x86/kvm/../../../virt/kvm/coalesced_mmio.o] Error 1", "make[2]: *** Waiting for unfinished jobs....", "arch/x86/kvm/../../../virt/kvm/kvm_main.c: In function 'kvm_destroy_vm_debugfs':", "arch/x86/kvm/../../../virt/kvm/kvm_main.c:559:10: error: 'struct kvm' has no member named 'debugfs_dentry'", "  if (!kvm->debugfs_dentry)", "          ^", "arch/x86/kvm/../../../virt/kvm/kvm_main.c:562:30: error: 'struct kvm' has no member named 'debugfs_dentry'", "  debugfs_remove_recursive(kvm->debugfs_dentry);", "                              ^", "arch/x86/kvm/../../../virt/kvm/kvm_main.c:564:9: error: 'struct kvm' has no member named 'debugfs_stat_data'", "  if (kvm->debugfs_stat_data) {", "         ^", "arch/x86/kvm/../../../virt/kvm/kvm_main.c:566:13: error: 'struct kvm' has no member named 'debugfs_stat_data'", "    kfree(kvm->debugfs_stat_data[i]);", "             ^", "arch/x86/kvm/../../../virt/kvm/kvm_main.c:567:12: error: 'struct kvm' has no member named 'debugfs_stat_data'", "   kfree(kvm->debugfs_stat_data);", "            ^", "arch/x86/kvm/../../../virt/kvm/kvm_main.c: In function 'kvm_create_vm_debugfs':", "arch/x86/kvm/../../../virt/kvm/kvm_main.c:581:5: error: 'struct kvm' has no member named 'debugfs_dentry'", "  kvm->debugfs_dentry = debugfs_create_dir(dir_name,", "     ^", "arch/x86/kvm/../../../virt/kvm/kvm_main.c:583:10: error: 'struct kvm' has no member named 'debugfs_dentry'", "  if (!kvm->debugfs_dentry)", "          ^", "arch/x86/kvm/../../../virt/kvm/kvm_main.c:586:5: error: 'struct kvm' has no member named 'debugfs_stat_data'", "  kvm->debugfs_stat_data = kcalloc(kvm_debugfs_num_entries,", "     ^", "arch/x86/kvm/../../../virt/kvm/kvm_main.c:587:18: error: 'struct kvm' has no member named 'debugfs_stat_data'", "       sizeof(*kvm->debugfs_stat_data),", "                  ^", "arch/x86/kvm/../../../virt/kvm/kvm_main.c:589:10: error: 'struct kvm' has no member named 'debugfs_stat_data'", "  if (!kvm->debugfs_stat_data)", "          ^", "arch/x86/kvm/../../../virt/kvm/kvm_main.c:599:6: error: 'struct kvm' has no member named 'debugfs_stat_data'", "   kvm->debugfs_stat_data[p - debugfs_entries] = stat_data;", "      ^", "arch/x86/kvm/../../../virt/kvm/kvm_main.c:601:10: error: 'struct kvm' has no member named 'debugfs_dentry'", "       kvm->debugfs_dentry,", "          ^", "arch/x86/kvm/../../../virt/kvm/kvm_main.c: In function 'kvm_create_vcpu_debugfs':", "arch/x86/kvm/../../../virt/kvm/kvm_main.c:2420:6: error: 'struct kvm_vcpu' has no member named 'debugfs_dentry'", "  vcpu->debugfs_dentry = debugfs_create_dir(dir_name,", "      ^", "arch/x86/kvm/../../../virt/kvm/kvm_main.c:2421:18: error: 'struct kvm' has no member named 'debugfs_dentry'", "         vcpu->kvm->debugfs_dentry);", "                  ^", "arch/x86/kvm/../../../virt/kvm/kvm_main.c:2422:11: error: 'struct kvm_vcpu' has no member named 'debugfs_dentry'", "  if (!vcpu->debugfs_dentry)", "           ^", "arch/x86/kvm/../../../virt/kvm/kvm_main.c:2427:32: error: 'struct kvm_vcpu' has no member named 'debugfs_dentry'", "   debugfs_remove_recursive(vcpu->debugfs_dentry);", "                                ^", "arch/x86/kvm/../../../virt/kvm/kvm_main.c: In function 'kvm_vcpu_ioctl':", "arch/x86/kvm/../../../virt/kvm/kvm_main.c:2554:1: error: expected expression before '<<' token", " <<<<<<< HEAD", " ^", "arch/x86/kvm/../../../virt/kvm/kvm_main.c:2556:1: error: expected expression before '==' token", " =======", " ^", "arch/x86/kvm/../../../virt/kvm/kvm_main.c: In function 'kvm_dev_ioctl_create_vm':", "arch/x86/kvm/../../../virt/kvm/kvm_main.c:3285:1: error: expected expression before '<<' token", " <<<<<<< HEAD", " ^", "arch/x86/kvm/../../../virt/kvm/kvm_main.c:3292:1: error: expected expression before '==' token", " =======", " ^", "arch/x86/kvm/../../../virt/kvm/kvm_main.c:3295:1: error: expected expression before '>>' token", " >>>>>>> linux-vmi", " ^", "arch/x86/kvm/../../../virt/kvm/kvm_main.c: In function 'kvm_init':", "arch/x86/kvm/../../../virt/kvm/kvm_main.c:4066:1: warning: label 'out_undebugfs' defined but not used [-Wunused-label]", " out_undebugfs:", " ^", "arch/x86/kvm/../../../virt/kvm/kvm_main.c: At top level:", "arch/x86/kvm/../../../virt/kvm/kvm_main.c:555:13: warning: 'kvm_destroy_vm_debugfs' defined but not used [-Wunused-function]", " static void kvm_destroy_vm_debugfs(struct kvm *kvm)", "             ^", "arch/x86/kvm/../../../virt/kvm/kvm_main.c:571:12: warning: 'kvm_create_vm_debugfs' defined but not used [-Wunused-function]", " static int kvm_create_vm_debugfs(struct kvm *kvm, int fd)", "            ^", "arch/x86/kvm/../../../virt/kvm/kvm_main.c:2408:12: warning: 'kvm_create_vcpu_debugfs' defined but not used [-Wunused-function]", " static int kvm_create_vcpu_debugfs(struct kvm_vcpu *vcpu)", "            ^", "arch/x86/kvm/../../../virt/kvm/kvm_main.c:3907:12: warning: 'kvm_init_debug' defined but not used [-Wunused-function]", " static int kvm_init_debug(void)", "            ^", "make[2]: *** [arch/x86/kvm/../../../virt/kvm/kvm_main.o] Error 1", "make[1]: *** [arch/x86/kvm] Error 2", "make: *** [arch/x86] Error 2", "make: *** Waiting for unfinished jobs....", "make: *** wait: No child processes.  Stop."], "stdout": "  CHK     include/config/kernel.release\n  CHK     include/generated/uapi/linux/version.h\n  CHK     include/generated/utsrelease.h\n  CHK     include/generated/timeconst.h\n  CHK     include/generated/bounds.h\n  CHK     include/generated/asm-offsets.h\n  CALL    scripts/checksyscalls.sh\n  CC [M]  arch/x86/kvm/../../../virt/kvm/kvm_main.o\n  CC [M]  arch/x86/kvm/../../../virt/kvm/coalesced_mmio.o\nscripts/Makefile.build:293: recipe for target 'arch/x86/kvm/../../../virt/kvm/coalesced_mmio.o' failed\nscripts/Makefile.build:293: recipe for target 'arch/x86/kvm/../../../virt/kvm/kvm_main.o' failed\nscripts/Makefile.build:544: recipe for target 'arch/x86/kvm' failed\nMakefile:988: recipe for target 'arch/x86' failed", "stdout_lines": ["  CHK     include/config/kernel.release", "  CHK     include/generated/uapi/linux/version.h", "  CHK     include/generated/utsrelease.h", "  CHK     include/generated/timeconst.h", "  CHK     include/generated/bounds.h", "  CHK     include/generated/asm-offsets.h", "  CALL    scripts/checksyscalls.sh", "  CC [M]  arch/x86/kvm/../../../virt/kvm/kvm_main.o", "  CC [M]  arch/x86/kvm/../../../virt/kvm/coalesced_mmio.o", "scripts/Makefile.build:293: recipe for target 'arch/x86/kvm/../../../virt/kvm/coalesced_mmio.o' failed", "scripts/Makefile.build:293: recipe for target 'arch/x86/kvm/../../../virt/kvm/kvm_main.o' failed", "scripts/Makefile.build:544: recipe for target 'arch/x86/kvm' failed", "Makefile:988: recipe for target 'arch/x86' failed"]}

[Wenzel]

On which branch are you ? master ?

because i don't see any git conflict pushed on the vmi branch in kvm/

This is how you source tree branches should look like:

• master for kvm-vmi:
• vmi for QEMU
• vmi for KVM
• nitro for libvmi
• master for nitro

[Wenzel]

Are you using NFS ?

[aghamir]

I was on master for kvm. Yes. I'm using NFS. I try to use vmi branch for kvm Tnx.

[Wenzel]

@aghamir if that could help you, i just merged a new branch providing ready to use debian packages for KVM, QEMU and libvmi. The vagrant build is much faster.

Maybe you can check it out ? it's on master, option is packaged = true in the Vagrantfile.

[bigbigbanana]

Hi,Wenzel! I use the original Nitro project and I get the following result!I don't know the meaning of Syscall trapped key and Sysret trapped key,could you tell me?And why the values of rax are same,is this wrong?Furthermore,I want to know how to use your project and could you send me a technical paper of your project,i will be very grateful to you for doing this,my email address is ning2616@mail.ustc.edu.cn. One more question,can your project be used in trapping syscalls of linux virtual machine?

[noxdafox]

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: https://github.com/KVM-VMI/nitro/pull/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)

[Wenzel]

Hi @aghamir ,

Do you still any issues with Vagrant ? Can i close this issue ?

Thanks.

[aghamir]

Hi @Wenzel , Vagrant works perfectly with packaged provisioning(Maybe its packages need some updates). I didn't use the other method for provisioning.

[ajaymas]

Hi,Wenzel! I use the original Nitro project and I get the following result!I don't know the meaning of Syscall trapped key and Sysret trapped key,could you tell me?And why the values of rax are same,is this wrong?Furthermore,I want to know how to use your project and could you send me a technical paper of your project,i will be very grateful to you for doing this,my email address is ning2616@mail.ustc.edu.cn. One more question,can your project be used in trapping syscalls of linux virtual machine?

I am Ajay, I have the same above question asked by ning2616@mail.ustc.edu.cn. 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. NtSetLdtEntries
NtSetLowEventPair
NtSetLowWaitHighEventPair
NtSetQuotaInformationFile
NtSetSecurityObject
NtSetSystemEnvironmentValue
NtSetSystemEnvironmentValueEx
NtSetSystemInformation
NtSetSystemPowerState
NtSetSystemTime
NtSetThreadExecutionState

How the older version Nitro captured system call are different from the above system call trace captured by Xen hypervisor through LibVMI.

1. @Wenzal could you please explain how system call sequence capture appears through KVM-VMI..? https://twitter.com/mtarral/status/1135304073576681473
2. Can you share a few snapshots with a detailed explanation related to system call trace capture in KVM-VMI?

[Wenzel]

@ajaymas the comment you provided here is not related to the vagrant up issue. Please open a new issue.

KVM-VMI has 2 versions, as explicitely said in the README:

• old: nitro, captures syscalls
• new: kvmi, set breakpoints anywhere in physical memory.

2. stop focusing on system call capture or tracing, what you want is breakpoints. What i can share is what KVM-VMI provides: a vagrant environment to build KVM with VMI modifications and have a VM to test it.

[ajaymas]

I am installing KVM-VM in the KVM Hypervisor with target introspection as Windows 10. I am following the Vagrant procedure to install KVM-VMI with its submodules such as modified KVM, Modified QEMU, libvmi and Nitro.

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 Bringing machine 'default' up with 'libvirt' provider... ==> default: Checking if box 'debian/stretch64' version '9.9.0' is up to date... ==> default: Machine already provisioned. Run vagrant provision or use the --provision ==> default: flag to force provisioning. Provisioners marked to run always will still run.

ajay@ubuntu-kvm3:~/kvm-vmi-master/vagrant$ vagrant provision ==> default: Running provisioner: ansible... Vagrant has automatically selected the compatibility mode '2.0' according to the Ansible version installed (2.6.0). Alternatively, the compatibility mode can be specified in your Vagrantfile: https://www.vagrantup.com/docs/provisioning/ansible_common.html#compatibility_mode

default: Running ansible-playbook...

PLAY [default] *****

TASK [Gathering Facts] ***** ok: [default]

TASK [add backports] *** ok: [default]

TASK [add backports sources] *** ok: [default]

TASK [update cache] **** fatal: [default]: FAILED! => {"changed": false, "msg": "Failed to update apt cache: E:The repository 'http://ftp.debian.org/debian jessie-backports Release' does not have a Release file."} to retry, use: --limit @/home/dodtech/kvm-vmi-master/vagrant/generate_deb/playbook.retry

PLAY RECAP ***** default : ok=3 changed=0 unreachable=0 failed=1

Ansible failed to complete successfully. Any error output should be visible above. Please fix these errors and try again.

[ajaymas]

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.

[ajaymas]

TASK [build test vm] *** fatal: [default]: FAILED! => {"changed": true, "cmd": ["./packer", "build", "--var-file=windows_7_x64.json", "windows.json"], "delta": "0:00:01.667651", "end": "2019-07-17 16:20:14.994345", "msg": "non-zero return code", "rc": 1, "start": "2019-07-17 16:20:13.326694", "stderr": "", "stderr_lines": [], "stdout": "\u001b[1;32mqemu output will be in this color.\u001b[0m\n\n\u001b[1;32m==> qemu: Downloading or copying ISO\u001b[0m\n\u001b[0;32m qemu: Downloading or copying: http://care.dlservice.microsoft.com/dl/download/evalx/win7/x64/EN/7600.16385.090713-1255_x64fre_enterprise_en-us_EVAL_Eval_Enterprise-GRMCENXEVAL_EN_DVD.iso\u001b[0m\n\u001b[0;32m qemu: Error downloading: checksums didn't match expected: 15ddabafa72071a06d5213b486a02d5b55cb7070\u001b[0m\n\u001b[1;31m==> qemu: ISO download failed.\u001b[0m\n\u001b[1;31mBuild 'qemu' errored: ISO download failed.\u001b[0m\n\n==> Some builds didn't complete successfully and had errors:\n--> qemu: ISO download failed.\n\n==> Builds finished but no artifacts were created.", "stdout_lines": ["\u001b[1;32mqemu output will be in this color.\u001b[0m", "", "\u001b[1;32m==> qemu: Downloading or copying ISO\u001b[0m", "\u001b[0;32m qemu: Downloading or copying: http://care.dlservice.microsoft.com/dl/download/evalx/win7/x64/EN/7600.16385.090713-1255_x64fre_enterprise_en-us_EVAL_Eval_Enterprise-GRMCENXEVAL_EN_DVD.iso\u001b[0m", "\u001b[0;32m qemu: Error downloading: checksums didn't match expected: 15ddabafa72071a06d5213b486a02d5b55cb7070\u001b[0m", "\u001b[1;31m==> qemu: ISO download failed.\u001b[0m", "\u001b[1;31mBuild 'qemu' errored: ISO download failed.\u001b[0m", "", "==> Some builds didn't complete successfully and had errors:", "--> qemu: ISO download failed.", "", "==> Builds finished but no artifacts were created."]} to retry, use: --limit @/home/dodtech/kvm-vmi-1/vagrant/provision_full/playbook.retry

PLAY RECAP ***** default : ok=50 changed=43 unreachable=0 failed=1

Ansible failed to complete successfully. Any error output should be visible above. Please fix these errors and try again.