|
On 12/04/2015 02:16 PM, Colin Walters wrote: > On Mon, Nov 23, 2015, at 10:35 AM, Dusty Mabe wrote: >> >> >> Right, this would affect them all. As you mention below we were >> intending for this ("eth0") to be the case for a long time so I >> figured we should fix it. You are right that this would be a change >> over how we released F23 atomic and it does have implications for >> other environments. > > Based on that, my instinct here is to only do this change for > the Vagrant box. WDYT? Ok can you merge the attached patch then? |
>From 70d102865a2f2b6b0bbcf1b2f25b3bdca71c0f32 Mon Sep 17 00:00:00 2001 From: Dusty Mabe <dusty@xxxxxxxxxxxxx> Date: Wed, 9 Dec 2015 11:36:17 -0500 Subject: [PATCH] Fix f23 vagrant atomic host not having eth0 net device name. Fixes https://fedorahosted.org/cloud/ticket/141 --- fedora-cloud-atomic-vagrant.ks | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/fedora-cloud-atomic-vagrant.ks b/fedora-cloud-atomic-vagrant.ks index 5f5d8ff..0ad0586 100644 --- a/fedora-cloud-atomic-vagrant.ks +++ b/fedora-cloud-atomic-vagrant.ks @@ -8,6 +8,13 @@ services --disabled=cloud-init,cloud-init-local,cloud-config,cloud-final user --name=vagrant --password=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 # Work around cloud-init being both disabled and enabled; need -- 2.4.3
_______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/cloud@xxxxxxxxxxxxxxxxxxxxxxx
