Host de destino inalcanzable mientras se hace ping entre 2 máquinas virtuales

Host de destino inalcanzable mientras se hace ping entre 2 máquinas virtuales

Estoy intentando crear una configuración de 2 máquinas virtuales ubicadas en el mismo hipervisor, a cada máquina virtual adjunté la interfaz virtIO desde el hipervisor editando el archivo XML de cada máquina virtual. Creé las máquinas virtuales y obtuve estas interfaces después del archivo adjunto:

ens7: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
    inet 11.198.133.5  netmask 255.0.0.0  broadcast 11.255.255.255
    ether 00:00:11:22:33:40  txqueuelen 1000  (Ethernet)
    RX packets 147  bytes 13980 (13.6 KiB)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 240  bytes 17952 (17.5 KiB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ens7: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
    inet 11.198.133.6  netmask 255.0.0.0  broadcast 11.255.255.255
    ether 00:00:11:22:33:41  txqueuelen 1000  (Ethernet)
    RX packets 57  bytes 8360 (8.1 KiB)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 261  bytes 18666 (18.2 KiB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Cada interfaz para cada VM Mientras hago ping de una VM a otra mediante la IP, aparece el mensaje: Host de destino inalcanzable, pero mientras hago ping en una VM y se ejecutatcpdump -nei ens7 en el otro recibo mensajes:

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ens7, link-type EN10MB (Ethernet), capture size 262144 bytes
12:24:49.749562 00:00:11:22:33:41 > Broadcast, ethertype ARP (0x0806), length 60: Request who-has 11.198.133.5 tell 11.198.133.6, length 46
12:24:49.749576 00:00:11:22:33:40 > 00:00:11:22:33:41, ethertype ARP (0x0806), length 42: Reply 11.198.133.5 is-at 00:00:11:22:33:40, length 28
12:24:50.773503 00:00:11:22:33:41 > Broadcast, ethertype ARP (0x0806), length 60: Request who-has 11.198.133.5 tell 11.198.133.6, length 46
12:24:50.773514 00:00:11:22:33:40 > 00:00:11:22:33:41, ethertype ARP (0x0806), length 42: Reply 11.198.133.5 is-at 00:00:11:22:33:40, length 28
12:24:51.797660 00:00:11:22:33:41 > Broadcast, ethertype ARP (0x0806), length 60: Request who-has 11.198.133.5 tell 11.198.133.6, length 46
12:24:51.797671 00:00:11:22:33:40 > 00:00:11:22:33:41, ethertype ARP (0x0806), length 42: Reply 11.198.133.5 is-at 00:00:11:22:33:40, length 28
12:24:52.821495 00:00:11:22:33:41 > Broadcast, ethertype ARP (0x0806), length 60: Request who-has 11.198.133.5 tell 11.198.133.6, length 46
12:24:52.821505 00:00:11:22:33:40 > 00:00:11:22:33:41, ethertype ARP (0x0806), length 42: Reply 11.198.133.5 is-at 00:00:11:22:33:40, length 28
12:24:53.845496 00:00:11:22:33:41 > Broadcast, ethertype ARP (0x0806), length 60: Request who-has 11.198.133.5 tell 11.198.133.6, length 46
12:24:53.845507 00:00:11:22:33:40 > 00:00:11:22:33:41, ethertype ARP (0x0806), length 42: Reply 11.198.133.5 is-at 00:00:11:22:33:40, length 28
12:24:54.869559 00:00:11:22:33:41 > Broadcast, ethertype ARP (0x0806), length 60: Request who-has 11.198.133.5 tell 11.198.133.6, length 46
12:24:54.869570 00:00:11:22:33:40 > 00:00:11:22:33:41, ethertype ARP (0x0806), length 42: Reply 11.198.133.5 is-at 00:00:11:22:33:40, length 28
12:24:55.893414 00:00:11:22:33:41 > Broadcast, ethertype ARP (0x0806), length 60: Request who-has 11.198.133.5 tell 11.198.133.6, length 46
12:24:55.893424 00:00:11:22:33:40 > 00:00:11:22:33:41, ethertype ARP (0x0806), length 42: Reply 11.198.133.5 is-at 00:00:11:22:33:40, length 28
12:24:56.917488 00:00:11:22:33:41 > Broadcast, ethertype ARP (0x0806), length 60: Request who-has 11.198.133.5 tell 11.198.133.6, length 46
12:24:56.917499 00:00:11:22:33:40 > 00:00:11:22:33:41, ethertype ARP (0x0806), length 42: Reply 11.198.133.5 is-at 00:00:11:22:33:40, length 28
12:24:57.941588 00:00:11:22:33:41 > Broadcast, ethertype ARP (0x0806), length 60: Request who-has 11.198.133.5 tell 11.198.133.6, length 46
12:24:57.941600 00:00:11:22:33:40 > 00:00:11:22:33:41, ethertype ARP (0x0806), length 42: Reply 11.198.133.5 is-at 00:00:11:22:33:40, length 28

¿Por qué el comando ping no funciona mientras tcpdump reconoce los paquetes? Edité el XML de una manera que asigna páginas enormes y el OV nos corrige en el hipervisor.

información relacionada