Fix libvirt Vagrant provider config #1491
Conversation
I made a mistake where I had used square brackets instead of pipes, potentially breaking the Vagrantfile. I'm sorry....
|
I did an actual test this time (after making some changes) to see whether it is working. Here are some screenshots of libvirt working: Changes made in RAM: Machine running afterwards: |
|
There seems to be a slight ttfb of 1-2 seconds, which I'm trying to fix but not really sure where it is coming from in the VM... I'm thinking it might be some sort of I/O issue? Maybe bindfs? As you can see it is waiting for 2.3s here on first html ttfb load: |
In order for a more accelerated virtual machine, KVM needs to be installed and set as the driver, so that the VM will be a lot faster.
|
Thanks for the quick fix (+ @talss89) Also my fault for not noticing that. The TTFB issue could be a lot of things but I'll merge this for now and if there's any Vagrant setting that improves that a follow-up fix is good. |
|
I just added the latest commit to change the accelerator for the VM to KVM (Right before you merged the fix), this should make the virtual machine a lot faster, I'm hoping that fixes the TTFB issue. I'm testing that right now. This does mean that whoever uses libvirt needs kvm and qemu both installed on their machine. I'm currently recreating the virtual machine, and it already feels a lot faster. EDIT: there we go, test results are in: TTFB issue solved 👍 To be sure I also did a |
I made a mistake where I had used square brackets instead of pipes, potentially breaking the Vagrantfile. I'm sorry....