Re: [PLUG] Virtual machine NIC device name

The solution was to use a pattern in /etc/network/interfaces:

yottadbuser@yottadbworkshop:~$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto /e*=eth0
iface eth0 inet dhcp
yottadbuser@yottadbworkshop:~$

Regards

– Bhaskar

On Sun, Jun 28, 2020 at 11:46 AM Rich Freeman <r-plug@thefreemanclan.net> wrote:

On Sun, Jun 28, 2020 at 11:30 AM K.S. Bhaskar via plug
<plug@lists.phillylinux.org> wrote:
>
> I created a Debian 10 virtual machine for users and customers to learn
> database administration and operations (including crash recovery;
> virtual machines being well suited to that). It has a single virtual
> NIC. When I boot it on my Arch Linux laptop with qemu, the virtual NIC
> has the name ens3, whereas when booted with Virtual Box on various
> operating systems, the virtual NIC has the name enp0s3. Since I would
> like the virtual machine to just come up with an IP address obtained
> by DHCP from the virtualization software. This means that they have to
> login from the console and manually edit /etc/network/interfaces. Is
> there any way to configure the virtual machine to just either give the
> NIC a consistent name,
>

You're using different software so getting them to behave identically
without any config tweaks is going to be difficult. I suspect the
difference comes down to how the VM presents the connectivity of the
interface (what PCI slot it is in, etc). If you can control that then
you might get the name to be consistent, assuming the distros you're
running inside use the same udev rules.

> or to tell it “whatever the NIC is called,
> just use DHCP to get an IP address”?

This is the approach I usually take. I typically stick this in my
systemd-networkd config:
cat /etc/systemd/network/static.network
[Match]
Name=e*

[Network]
DHCP=yes

Really though I've found that most distros set up dhcp by default, so
I'm not sure why you even need to fiddle with it.

This is assuming you're using networkd as your network manager.
Obviously the details will vary if you're using something else. A lot
of the legacy distros use their own solutions so there will be
variance if you're using one.

--
Rich

--
Rich