That was my first thought, so I tried to set up manually the default route and netmask on the VM to match the engine's, but it didn't solve the problem.

Another network question: I have a second network card on the host that is connected to an internal switch, how do I add a bridge for that card to be used by the VMs ? I created a secondary bridge on the host and then I tried to play with the network options on the oVirt portal, but I couldn't figure out to associate the new bridge with an new network. Before anyone thinks that the two issues are related, I did this after failing to solve the first issue.

On 9/10/20 8:00 AM, Edward Berger wrote:

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/

--

As a result of Coronavirus-related precautions, NYU and the Center for Brain Imaging operations will be managed remotely until further notice.

All telephone calls and e-mail correspondence are being monitored remotely during our normal business hours of 9am-5pm, Monday through Friday.

For MRI scanner-related emergency, please contact: Keith Sanzenbach at keith.sanzenbach@nyu.edu and/or Pablo Velasco at pablo.velasco@nyu.edu

For computer/hardware/software emergency, please contact: Valerio Luccio at valerio.luccio@nyu.edu

For TMS/EEG-related emergency, please contact: Chrysa Papadaniil at chrysa@nyu.edu

For CBI-related administrative emergency, please contact: Jennifer Mangan at jennifer.mangan@nyu.edu

Valerio Luccio		(212) 998-8736
Center for Brain Imaging		4 Washington Place, Room 158
New York University		New York, NY 10003

"In an open world, who needs windows or gates ?"