When submitting a patch to add Vagrant Halt capabilities to Vagrant-libvirt,the maintainer asked me to test the patch against a PXE VM.
Recently got the opportunity to learn Red Hat Virtualization. So I decided to take a stab at installing a simple RHV environment using vagrant-libvirt,
Simulating an Openstack environment that consists of 12 Openstack nodes and 4 switches. When I first started, performance was horrible. Here are some the things I did to improve performance. Still learning, so if anyone has any tips, please share.
Have a need for tiny VMs for my Vagrant environment to simulate devices I do not care about. For example: printers.
Update: Cumulus Networks have upstreamed a patch that sets a speed on a virtio_net enabled VM NIC.
In Part 1 of Troubleshooting Mirantis Fuel, it was discovered that
OpenStack installation failed because the nodes could not reach
the internet. To remedy this, an APT mirror was setup using the
The virtual design setup for installing Mirantis OpenStack in a vagrant-libvirt environment does not work with the default settings of Mirantis Fuel. Bad design? Maybe. This series of posts may be changed in the near future as Mirantis Openstack adventures continue.
These are the notes on how the Mirantis Fuel Vagrant Box was built. For details on the install, go to the previous post.
Updated: 25th Feb 2016
Packer comes with a QEMU Builder. Its not well documented, but thanks to J.Toppins, I have a git repo that shows you how to build a Ubuntu and Jessie Libvirt compatible Vagrant Box
Updated June 2016
About 2 years ago, I began exploring stitching virtual machine(VM) interfaces together directly using QEMU. The reason for doing this is because connecting VMs together using linux bridges has the following disadvantages:
Interesting error message when running
bundle install on the libvirt-vagrant