Opennebula 6.2.0-1.ce kvm-node on master cant ping google.com

Community Support General
1

I am able to run vm’s on all my nodes as well as the master. Vm’s running on the master cannot ping google.com but the same vm migrated to other nodes or recreated on any other node is able to ping google.com.

I’m running the following version.
opennebula | 6.2.0-1.ce | Index of /repo/6.2/Ubuntu/20.04 stable/opennebula amd64 Packages

I’m not sure what’s happend but previously I was able ping from any vm.

Can anyone give any direction as I don’t know where to go from here, I don’t really want to trash the master and reinstall.

Thanks in advance
Dennis

2

Hello @DennisTait,

You can check few things here:

  • Check if the VM is correctly contextualized.
  • Check your physical network, e.g: if you are using bridge networking, check the bridge exists and is correctly configured.
  • Check your DNS, maybe you can try ping 8.8.8.8.
3

Hi @ahuertas Thanks for getting back to me, this problem is doing my head in.
The problem must be on my master node host where I have one, sunstone and kvm-node installed.

Can you help me with the process to check my physical network is configured properly?: I am using bridge networking, it exists because it’s used when I live migrate.

Here is another view of my issue.
I deployed a vm to the master node host, as you can see I can’t ssh or ping the vm from my laptop on the same network.

linux@DESKTOP-QTDQ0CJ:~$ ssh linux@192.168.1.100
^C
linux@DESKTOP-QTDQ0CJ:~$ ping 192.168.1.100
PING 192.168.1.100 (192.168.1.100) 56(84) bytes of data.
^C
--- 192.168.1.100 ping statistics ---
9 packets transmitted, 0 received, 100% packet loss, time 8137ms

After live migrating the vm to a worker node host I can ssh and ping the vm.

```linux@DESKTOP-QTDQ0CJ:~$ ssh linux@192.168.1.100
linux@192.168.1.100's password:
Last login: Fri Mar 18 13:50:17 2022
[linux@localhost ~]$ logout
Connection to 192.168.1.100 closed.

linux@DESKTOP-QTDQ0CJ:~$ ping 192.168.1.100
PING 192.168.1.100 (192.168.1.100) 56(84) bytes of data.
64 bytes from 192.168.1.100: icmp_seq=1 ttl=64 time=6.50 ms
64 bytes from 192.168.1.100: icmp_seq=2 ttl=64 time=6.57 ms
64 bytes from 192.168.1.100: icmp_seq=3 ttl=64 time=120 ms
^C
--- 192.168.1.100 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 6.504/44.366/120.021/53.495 ms
linux@DESKTOP-QTDQ0CJ:~$
4

Hello @DennisTait,

Check that in the master node, you have the bridge correctly configured with the desired IP and also that the VM is attached to it, you can use the command brctl.

Best,
Álex.