From 3904c53a79ca31771ed1c3321543cafae0b28464 Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Fri, 29 Apr 2016 20:48:39 -0400 Subject: [PATCH 1/2] cloud-base-vagrant: Add sshfs to support vagrant-sshfs plugin Adding sshfs into the image will make it so that users won't have to wait for the package to be installed on bringup. --- fedora-cloud-base-vagrant.ks | 3 +++ 1 file changed, 3 insertions(+) diff --git a/fedora-cloud-base-vagrant.ks b/fedora-cloud-base-vagrant.ks index df338d7..f7f1518 100644 --- a/fedora-cloud-base-vagrant.ks +++ b/fedora-cloud-base-vagrant.ks @@ -32,6 +32,9 @@ dnf-yum # users setup. This can actually take a bit of time. Just fold it # in to the base box disk image rsync +# Add fuse-sshfs so that the vagrant-sshfs plugin won't have to +# install it on boot. https://github.com/dustymabe/vagrant-sshfs +fuse-sshfs %end %post --erroronfail From 209b48fd52cec8cafb338cd9eb7a32639c4a26fb Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Tue, 3 May 2016 17:22:29 -0400 Subject: [PATCH 2/2] cloud-base-vagrant: use extlinux to match cloud-base If we don't do this it will try to use grub2 but will fail because we removed the packages from the package set. --- fedora-cloud-base-vagrant.ks | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fedora-cloud-base-vagrant.ks b/fedora-cloud-base-vagrant.ks index f7f1518..855bfee 100644 --- a/fedora-cloud-base-vagrant.ks +++ b/fedora-cloud-base-vagrant.ks @@ -19,7 +19,7 @@ rootpw vagrant # even on VirtualBox virt, we get a primary network device with "eth0" as the name # This simplifies things and allows a single disk image for both supported Vagrant # platforms (virtualbox and kvm) -bootloader --timeout=1 --append="no_timer_check console=tty1 console=ttyS0,115200n8 net.ifnames=0 biosdevname=0" +bootloader --timeout=1 --append="no_timer_check console=tty1 console=ttyS0,115200n8 net.ifnames=0 biosdevname=0" --extlinux %packages # The default koji Vagrantfile configuration uses rsync to sync files between