You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I use a standard linux bridge inside the hypervisor to access both hypervisor and VMs. The hypervisor is reachable but the VM is not.
To Reproduce
Steps to reproduce the behavior:
Deploy SEAPATH Yocto on a standalone machine with a bridge (see inventory below)
Launch a virtual machine connected to that bridge (see inventory below)
Log into the virtual machine with virsh console guest0
Add an IP addr to this machine : sudo ip addr add <vm_ip_addr> dev enp0s2
Try to connect to the vm ssh admin@<vm_ip_addr>
The connection fails
Expected behavior
When the bridge is set up and the VM has an IP address, we should be able to connect with ssh.
Workaround
Use an ovs bridge instead.
Ideas to fix
We must first test if the new version of the linux kernel and RT patch corrects the problem.
If yes, we must ensure that we still have good RT performances in this version
Describe the bug
I use a standard linux bridge inside the hypervisor to access both hypervisor and VMs. The hypervisor is reachable but the VM is not.
To Reproduce
Steps to reproduce the behavior:
virsh console guest0
sudo ip addr add <vm_ip_addr> dev enp0s2
ssh admin@<vm_ip_addr>
Expected behavior
When the bridge is set up and the VM has an IP address, we should be able to connect with ssh.
Workaround
Use an ovs bridge instead.
Ideas to fix
We must first test if the new version of the linux kernel and RT patch corrects the problem.
If yes, we must ensure that we still have good RT performances in this version
Standalone Host inventory
VM inventory
The text was updated successfully, but these errors were encountered: