[SOLVED] [KVM] Guest network connection irreparably dies if the host is disconnected
Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
[KVM] Guest network connection irreparably dies if the host is disconnected
Every time I disconnect my host from the Internet, all of my virtual machines lose network access permanently until I reboot the host. This happens on Linux (tested various distros) and Windows guests. Is there a workaround for this? As a last resort I could live with having to reboot the guests, but rebooting the host is overkill. Any kind of forced reboot gives me PTSD flashbacks of my Windows days.
I'm running KVM/QEMU/virt-manager on MX Linux 21.3
Vaguely, it has to do with your network topography and how you set it up. The problem I had was disconnecting a guest caused the host to lose its external IP4 address. Now I keep the guests on their bridge and the external interface separate. I don't know if you're using netplan or network manager or scripts because I'm not familiar with MX Linux, but there's a way to do it. Yes, reboot is overkill and unneeded.
Vaguely, it has to do with your network topography and how you set it up. The problem I had was disconnecting a guest caused the host to lose its external IP4 address. Now I keep the guests on their bridge and the external interface separate. I don't know if you're using netplan or network manager or scripts because I'm not familiar with MX Linux, but there's a way to do it. Yes, reboot is overkill and unneeded.
Pretty sure it's just Network Manager doing everything network wise
Quote:
Originally Posted by yancek
What network settings do you have on KVM? Do you understand the difference in the various settings, particularly between NAT and bridged?
I'm using "Virtual network (default)" as the NIC in virt-manager, which gives VMs IPs in the range 192.168.122.x which is fine with me. I'd rather keep it that way because I'm sure a couple of my VMs will break if I change it (specially those that need port forwarding) but I'll fiddle with the other options if there's no other way to fix it as it is. I don't really understand how they differ exactly, no
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.