On Tue, May 15, 2018 at 03:15:17PM +1000, [email protected] wrote:
> It seems that there is some sort of race condition related to kvm on one
> of my servers where starting kvm virtual machines will cause networking to
> stop. [...]
>
> This first happened in March, so I think it was some Debian update in that
> time period that introduced the issue. [...]
>
> Any suggestions for what to investigate?
10-to-1 it's systemd doing something stupid. So I'd start looking there.
Are you running qmeu yourself, or using libvirt? libvirt on debian should Just
Work. I run VMs on several machines here and haven't noticed any problems with
VMs not starting properly after reboot or - worse - messing with my network
config (that just shouldn't happen. at all. ever.)
How is the server's network configured? using the NIC directly (e.g. on old
style eth0 or the not-at-all-"new"-any-more consistent device naming style
like enp2s0), or a bridge device like br0?
Іt's generally best to use bridge devices on both the host and the VMs for
virtualisation.
e.g. in /etc/network/interfaces
auto br0
iface br0 inet static
address x.x.x.y
netmask 255.255.255.0
network x.x.x.x.0
broadcast x.x.x.x.255
bridge_ports eth0
bridge_stp off
bridge_maxwait 0
bridge_fd 0
bridge_hello 2
bridge_maxage 12
craig
--
craig sanders <[email protected]>
_______________________________________________
luv-main mailing list
[email protected]
https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
