davidlt/fedora-kickstarts
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix f23 vagrant atomic host not having eth0 net device name.

Browse Source 
Fixes https://fedorahosted.org/cloud/ticket/141
This commit is contained in:
Dusty Mabe 2015-12-09 11:36:17 -05:00 committed by Colin Walters
parent 2d56c91c07
commit 2878aa0060
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
fedora-cloud-atomic-vagrant.ks
View File

@ -8,6 +8,13 @@ services --disabled=cloud-init,cloud-init-local,cloud-config,cloud-final
user --name=vagrant --password=vagrant user --name=vagrant --password=vagrant
rootpw vagrant rootpw vagrant
# The addition of the net.ifnames=0 and biosdevnames=0 option ensures that
# 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"
%post --erroronfail %post --erroronfail
# Work around cloud-init being both disabled and enabled; need # Work around cloud-init being both disabled and enabled; need