Open 0xDivyanshu-new opened 3 weeks ago
Hi !
I've never seen this error before. Also you altready toggled the debug output (which is great), but doesn't give us much information. _"Failed to start QEMU binary /usr/local/bin/qemu-system-x8664 for probing"
Can you try posting it on the https://github.com/vagrant-libvirt/vagrant-libvirt project ?
Side note: what was the last time you successfuly built the Windows template ? I tried it on Monday, and it breaks when reaching the VSIX extension setup.
I didn't manage to fix it yet, so I can't test vagrant provisioning again for the moment.
Hi @Wenzel ,
Thanks for the response. So i tried 2 things basically.
sdk_setup.exe /q /installpath "C:\\Program Files\\Windows Kits\\10" /norestart /log po.txt
After removing the VSIX extension line, i was facing the main error that i just shared here in the issue.
windows.pkr.hcl
rather than the one that i built by make deploy
with kafl support. So i removed the hashicorp dependency and installed the qemu with kafl support system wide by make install
from x86_64-softmmu
directory. After doing that, I started facing issues with the OS installation part itself which is way before the execution of playbook commands inside VM.
I think the 2nd approach is the right once since we are supposed to use the qemu that was build with kafl support rather than using the hashicorp's default qemu plugin.
Would love to know your inputs on this!
Thanks
Hi team,
I am currently trying to get the snapshot by importing the vm into libvrt as defined in the docs mentioned here.
I am not really quite sure on what is the exact issue here. Before that i was getting permission denied issues but those got fixed by fixing the apparmor.
I was able to create the box and it was added to vagrant
I also ran the vagrant up command with debug flag but there is literally no message that says what exactly went wrong that failed
virDomainDefineXML
. This is the error snippet when running with debug flag