Mathieu Tarral

+1, big issue for me too.

@camilasan can we ping Nextcloud devs to have some idea how to debug this ? How can we provide you more information and help you find the bug ?

Surprisingly, it's not libkvmi which failed, it's the self tests: https://app.travis-ci.com/github/KVM-VMI/kvm-vmi/builds/239353934#L1105 ~~~ TASK [run kvm self-tests] ****************************************************** fatal: [kvmi]: FAILED! => changed=true cmd: - ./tools/testing/selftests/kvm/x86_64/kvmi_test delta: '0:00:00.003372' end: '2021-10-07 18:22:17.241996'...

Libvmi compilation failed https://app.travis-ci.com/github/KVM-VMI/kvm-vmi/builds/239413034#L1181 ~~~ /vagrant/libvmi/libvmi/driver/kvm/kvm_private.h:64:30: error: KVMI_NUM_EVENTS undeclared here (not in a function); did you mean KVMI_VM_EVENT? status_t (*process_event[KVMI_NUM_EVENTS])(vmi_instance_t vmi, struct kvmi_dom_event *event); ^~~~~~~~~~~~~~~ KVMI_VM_EVENT ~~~

The build timed out: https://app.travis-ci.com/github/KVM-VMI/kvm-vmi/builds/239455542#L1089 Looks like building the kernel takes more time than it used to be. Before: kernel + modules compilation: `~7313 seconds` https://app.travis-ci.com/github/KVM-VMI/kvm-vmi/builds/237909810#L1011 now: kernel + modules...

`*** No rule to make target 'kvmconfig'. Stop.`

Somehow it wasn't able to start the second playbook: ~~~ ==> kvmi: Machine already provisioned. Run `vagrant provision` or use the `--provision` ==> kvmi: flag to force provisioning. Provisioners marked...

I tried to rebuild this branch locally with vagrant, and the `kvmi-test` hangs: ~~~ TASK [run kvm self-tests] ****************************************************** ~~~ I'm running on AMD Ryzen Pro here. When I executed...

So, packer depend on docker, which refuses to start I just tested with `vagrant up --no-provision` and `sudo apt-get packer`, it works. So Docker can't start on the KVMi kernel...

Just pushed a fix where we install Packer from the zip archive distributed by packer.io instead of the Debian package