can't get networking to work on KVM/libvirt coreos host on bare metal server

25 views

Skip to first unread message

Frohike Mail

unread,

Apr 20, 2017, 4:34:30 AM4/20/17

to CoreOS User

Hi, I have server on hetzner.de, and on this bare metal server i have installed KVM/libvirt.

I want to create three coreos nodes now, to start to play with Tectonic. to build a container landscape on which I will install openstack to learn.

Now, I have a coreos image created with librit, but when I boot it, I need to install it to disk I assume.

So, when connecting with VNC to the cores, I get the default running cores. But it has no networking configured at all. So I try to get the network running to I can initiate the install to disk process.

So, I created a static.network in /etc/systemd/network

It has this :

[Match]

Name=ens3

[Network]

Address=176.9.23.40/32

Peer=176.9.23.19

DNS=8.8.8.8

Then when I restart with systemctl restart system-networkd, it attaches this IP, when I check this with the command "ip address"

But when I type in "ip route" , it stays empty.

The bare metal host has the following network configuration:

[root@CentOS-73-64-minimal ~]# ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1

link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

inet 127.0.0.1/8 scope host lo

valid_lft forever preferred_lft forever

inet6 ::1/128 scope host

valid_lft forever preferred_lft forever

2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000

link/ether 4c:72:b9:26:e8:0c brd ff:ff:ff:ff:ff:ff

inet 176.9.23.19 peer 176.9.23.1/32 brd 176.9.23.16 scope global eno1

valid_lft forever preferred_lft forever

inet 176.9.23.19/32 scope global eno1

valid_lft forever preferred_lft forever

inet6 fe80::4e72:b9ff:fe26:e80c/64 scope link

valid_lft forever preferred_lft forever

3: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000

link/ether fe:54:00:b7:3f:ec brd ff:ff:ff:ff:ff:ff

inet 176.9.23.19 peer 176.9.23.1/32 brd 176.9.23.19 scope global virbr0

valid_lft forever preferred_lft forever

inet 176.9.23.19/32 scope global virbr0

valid_lft forever preferred_lft forever

inet6 fe80::fc54:ff:fe87:cc24/64 scope link

valid_lft forever preferred_lft forever

6: virbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000

link/ether 52:54:00:1e:79:cb brd ff:ff:ff:ff:ff:ff

7: virbr1-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr1 state DOWN qlen 1000

link/ether 52:54:00:1e:79:cb brd ff:ff:ff:ff:ff:ff

13: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master virbr0 state UNKNOWN qlen 1000

link/ether fe:54:00:b7:3f:ec brd ff:ff:ff:ff:ff:ff

inet6 fe80::fc54:ff:feb7:3fec/64 scope link

valid_lft forever preferred_lft forever

14: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master virbr1 state UNKNOWN qlen 1000

link/ether fe:54:00:23:22:c5 brd ff:ff:ff:ff:ff:ff

inet6 fe80::fc54:ff:fe23:22c5/64 scope link

valid_lft forever preferred_lft forever

17: vnet2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master virbr0 state UNKNOWN qlen 1000

link/ether fe:54:00:dc:f5:fb brd ff:ff:ff:ff:ff:ff

inet6 fe80::fc54:ff:fedc:f5fb/64 scope link

valid_lft forever preferred_lft forever

[root@CentOS-73-64-minimal ~]#

[root@CentOS-73-64-minimal ~]# ip r

default via 176.9.23.1 dev eno1

10.0.0.11 dev virbr0 scope link

169.254.0.0/16 dev eno1 scope link metric 1002

169.254.0.0/16 dev virbr0 scope link metric 1003

176.9.23.1 dev eno1 proto kernel scope link src 176.9.23.19

176.9.23.1 dev virbr0 proto kernel scope link src 176.9.23.19

176.9.23.40 dev virbr0 scope link

David Michael

unread,

Apr 20, 2017, 4:49:37 PM4/20/17

to CoreOS User

On Thu, Apr 20, 2017 at 1:34 AM, Frohike Mail <frohi...@gmail.com> wrote:
> So, when connecting with VNC to the cores, I get the default running cores.
> But it has no networking configured at all. So I try to get the network
> running to I can initiate the install to disk process.

For the list, it sounded like this was fixed in IRC.

> So, I created a static.network in /etc/systemd/network
>
> It has this :
>
> [Match]
> Name=ens3
>
> [Network]
> Address=176.9.23.40/32
> Peer=176.9.23.19
> DNS=8.8.8.8