When I was testing Vagrant builds for Fedora I needed to run Vagrant in a virtual machine and then test vagrant libvirt integration there. So to say a needed to do virtualization on the virtual machine. Luckily for me it is possible with KVM and Rhys Oxenhams wrote about setting it up. This post is about setting it up and using it with virt-manager. First lets see whether we have nested KVM enabled:
Some time ago we finished most of the work for Vagrant Fedora 22 feature. The Vagrant package is currently in the review process, but I maintain Copr repositories for both Fedora 21 and rawhide. Here is how to install Vagrant and vagrant-libvirt on Fedora 21.
It can happen to anyone. You went with
yum distro-sync transaction that got interrupted and your system is broken. And you want to know how to fix it.
RubyGems started with a single marshaled file called Marshal.4.8.gz containing the array of every
Gem::Specification object for every gem that has been uploaded to RubyGems directory. Since then we have new indexes for RubyGems to speed things up, but good old Marshal.4.8.gz is still around carrying important information about gems from RubyGems.org. Are you interested to know what is and what is not there and finally understand why
gem specification rails -r does not give you the information on licensing even though it’s part of rails’ gemspec file?
Do you need to set up a shared folder between your host OS and guests running in virt-manager? I will show you how to do it on your Fedora system which involves a SELinux policy change.