[SOLVED] Archlinux as Proxmox VM Network Adapter issues

evlute · 2015-09-24 14:39:48

Hallo,

today i updated one virtual archlinux maschine in my proxmox host. The adapter name changed
for my virtio network adapter from eth0 to ens18. Netctl or systemd-networkd can't assign
ip addresses to this adapter. I'm not sure why, but after every reboot i have to start the ens18
link. Why isn't the adapter link state automaticaly started?

regards
evlute

Last edited by evlute (2015-10-07 10:44:20)

evlute · 2015-10-01 08:34:15

hello,

i'm on Kernel 4.2.1-1-Arch in my Proxmox VM. The problem still exist after upgrading to a new kernel. I'm not sure if this problem is arch or proxmox related.
If someone got some information how to handle this issue - please let me know.

WorMzy · 2015-10-01 10:56:43

Netctl or systemd-networkd can't assign
ip addresses to this adapter.

Why not? Post the related logs/error messages/configuration files.

evlute · 2015-10-01 14:58:24

The issue is that the network adapter isn't started. i don't know if it's a kernel thing. i have to start him by hand. And because of that netctl can't assign default routing which to the device.
if i knew why the adapter isn't started directly while booting it would be a help. the bootlog doest not say anything to me. Will post it tomorow. Leave the office now.

WorMzy · 2015-10-01 15:04:45

The issue is that the network adapter isn't started

What does this mean? The kernel module isn't loaded?

evlute · 2015-10-01 16:59:13

No the Kernel module is loaded, otherwise i could not start the adapter in the shell, but the adapter is not started by default.
Here is the log: http://paste.pound-python.org/show/DeGy … mhxBu94Av/

WorMzy · 2015-10-01 17:17:37

Please explain how you "start" the adaptor. All I can see regarding ens18 is that it gains a carrier immediately after the Network Service starts.

Oct 01 15:36:01 Archlinux systemd[1]: Started Network Service.
Oct 01 15:36:19 Archlinux systemd-networkd[302]: ens18: Gained carrier

After that there are some messages about being able to configure eth0, which I presume is because you haven't updated your config files since the network adaptor started getting renamed.

Oct 01 15:36:45 Archlinux systemd[1]: sys-subsystem-net-devices-eth0.device: Job sys-subsystem-net-devices-eth0.device/start timed out.
Oct 01 15:36:45 Archlinux systemd[1]: Timed out waiting for device sys-subsystem-net-devices-eth0.device.
Oct 01 15:36:45 Archlinux systemd[1]: Dependency failed for A basic static ethernet connection.
Oct 01 15:36:45 Archlinux systemd[1]: netctl@ethernet\x2dstatic.service: Job netctl@ethernet\x2dstatic.service/start failed with result 'dependency'.
Oct 01 15:36:45 Archlinux systemd[1]: sys-subsystem-net-devices-eth0.device: Job sys-subsystem-net-devices-eth0.device/start failed with result 'timeout'.

At no point is there an attempt to configure ens18.

evlute · 2015-10-01 17:40:02

The problem is - the adapter is configured right :
i changed it from eth0 to ens18 as the kernel changed, and the adapter name changed too.

the thing is - the network adapter ens18 is in an off state while bootin. netctl can't configure the adapter, because the adapter is off.
i have to start the adapter with : ip link set up ens18 and have to manually set an ip.

evlute · 2015-10-05 09:35:16

Ipdated to Kernel 4.2.2-1 and the problem still exists. The network adapter starts in a disabled state and has to be manually activated.

WorMzy · 2015-10-05 09:57:46

Possibly having both systemd-networkd and netctl enabled is causing problems. Disable systemd-networkd and see if that fixes it. If not, post the output of

# systemctl status netctl@ethernet-static.service

evlute · 2015-10-07 10:48:46

the solution is create an empty file
80-net-setup-link.rules in the directory /etc/udev/rules.d - this will overwrite the settings in /usr/lib/udev/rules.d80-net-setup-link.rules

this adapter renaming happend for the most archlinux users in 2013. for my virtualmachines it happend now and the adapter renaming makes no sense for me in my virtual maschines so this solution to leave the virtual adapters as eth[0|number] is the best for me.

Arch Linux

#1 2015-09-24 14:39:48

[SOLVED] Archlinux as Proxmox VM Network Adapter issues

#2 2015-10-01 08:34:15

Re: [SOLVED] Archlinux as Proxmox VM Network Adapter issues

#3 2015-10-01 10:56:43

Re: [SOLVED] Archlinux as Proxmox VM Network Adapter issues

#4 2015-10-01 14:58:24

Re: [SOLVED] Archlinux as Proxmox VM Network Adapter issues

#5 2015-10-01 15:04:45

Re: [SOLVED] Archlinux as Proxmox VM Network Adapter issues

#6 2015-10-01 16:59:13

Re: [SOLVED] Archlinux as Proxmox VM Network Adapter issues

#7 2015-10-01 17:17:37

Re: [SOLVED] Archlinux as Proxmox VM Network Adapter issues

#8 2015-10-01 17:40:02

Re: [SOLVED] Archlinux as Proxmox VM Network Adapter issues

#9 2015-10-05 09:35:16

Re: [SOLVED] Archlinux as Proxmox VM Network Adapter issues

#10 2015-10-05 09:57:46

Re: [SOLVED] Archlinux as Proxmox VM Network Adapter issues

#11 2015-10-07 10:48:46

Re: [SOLVED] Archlinux as Proxmox VM Network Adapter issues

Board footer