A CentOS 7 host installs CentOS 7 virtual machines inside itself using a
virt-install command, which includes an assigned MAC address. The CentOS 7 host is connected via Ethernet to a hardware firewall/router, which has assigned a static IP address to the MAC address that is given to a specified virtual machine. Machines elsewhere in the same network are able to communicate with the virtual machine when it is installed (
telnet, etc.). However, several days later, the virtual machine is not able to send or receive communications with the rest of the network (no
telnet, etc.) This problem is resolved when the virtual machine is destroyed, and then the same
virt-install command is used to re-install a clone of the virtual machine. This indicates that the connectivity unreliability problem is caused by something INSIDE the virtual machine.
What specifically can be done in order to cause these virtual machines to be able to maintain reliable, lasting connectivity with the rest of the network?
The virtual machines are created by running the following
virt-install command on the host:
virt-install --name=first-centos7 --disk path=/tmp/firstDisk.qcow2,size=241 --graphics none --vcpus=1 --memory=3072 --location /tmp/CentOS-7-x86_64-Minimal-1611.iso --network bridge=br0 --os-type=linux --os-variant=rhel7.0 --mac=52:54:00:ma:ca:dr --initrd-inject=/tmp/vm.ks --extra-args "ks=file:/vm.ks console=ttyS0"
virt-install command be changed? Or should some command inside the resulting virtual machine be changed? Or does something in the host need to be changed in order to enforce reliability for all the guest virtual machines?