I believe this problem also exists in F25. There are upsides to having a vm do the networking and I have used that scheme for something like a decade. The point is that libvirt should start up and start its VM's correctly. If you cannot depend on the system starting correctly then very quickly you cannot depend on the system at all and then your backing out to your switches and network cables and power supplies ..... My guess is that its related to libvirt trying to start before the xen subsystems have come up.
On 07/26/2017 09:32 AM, Dominik Psenner
wrote:
-- Alvin Starr || land: (905)513-7688 Netvel Inc. || Cell: (416)806-0133 alvin@xxxxxxxxxx || |
_______________________________________________ libvirt-users mailing list libvirt-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvirt-users