It sounds like you don't have a proper default route on the VM or the netmask is set incorrectly,

which can cause a bad route.

Look at differences between the engine's network config (presuming it can reach outside the hypervisor host)

and the VM's config. The VM should have the same subnet, netmask and default gateway as the engine VM,

if its connected to ovirtmgmt.

"ip a" "ip r" "traceroute" and "ping" are the usual commands to check network connections.

On Thu, Sep 10, 2020 at 6:29 AM <valerio.luccio@nyu.edu> wrote:

I apologize for asking what is probably a very basic question.

I installed and created a self-hosted engine using cockpit on a server. I can reach the self-hosted engine from anywhere within my network.

I then created a new VM selecting the default ovirtmgmt for the network. The VM does not seem to connect to the network via the bridge. I the used the console to manually configured the network card and I have connectivity between the VM, the engine and the server, but not beyond. What am I doing wrong ? Can someone point to a good documentation page on the subject ?

Thanks in advance,
Valerio
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/IFXOOU4DVR66DWEUCR66CJ2LQFUFCN55/