commit 3992f9ca911f2228c2e7510b88e8f3a9a35cfd3e
Author: Dusty Mabe <dusty(a)dustymabe.com>
Date: Tue May 3 17:22:29 2016 -0400
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 files changed, 1 insertions(+), 1 deletions(-)
---
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
Show replies by date