On 10/4/19 10:00 AM, Ljubomir Ljubojevic wrote:> On 10/4/19 3:03 PM, Chris Adams wrote: >> ... >> See the NetworkManager-config-server package. > Ahh, thanks. I was wondering about it but never investigated.Hmmmm..... Description : This adds a NetworkManager configuration file to make it behave more like the old "network" service. In particular, it stops NetworkManager from automatically running DHCP on unconfigured ethernet devices, and allows connections with static IP addresses to be brought up even on ethernet devices with no carrier. This package is intended to be installed by default for server deployments. ++++++++++ Well, learn something new every day.... nice.? Time to learn a bit more about what it will do, and see about deploying to our KVM hosts.....? I've not had the bridged network issues some seem to have been plagued with, and I have several KVM hosts with bridged networking (with multiple VLANs) using NetworkManager (using nmtui to configure a bridge isn't hard). I decided to configure it that way just ot see how easy or hard it was to do with NM, and to test its stability, and after passing testing under load I popped it into production, running a few Windows 7 guests and a couple of CentOS 7 guests.
On 10/4/19 4:42 PM, Lamar Owen wrote:> On 10/4/19 10:00 AM, Ljubomir Ljubojevic wrote: >> On 10/4/19 3:03 PM, Chris Adams wrote: >>> ... >>> See the NetworkManager-config-server package. >> Ahh, thanks. I was wondering about it but never investigated. > Hmmmm..... > Description : > This adds a NetworkManager configuration file to make it behave more > like the old "network" service. In particular, it stops NetworkManager > from automatically running DHCP on unconfigured ethernet devices, and > allows connections with static IP addresses to be brought up even on > ethernet devices with no carrier. > > This package is intended to be installed by default for server > deployments. > ++++++++++ > Well, learn something new every day.... nice.? Time to learn a bit more > about what it will do, and see about deploying to our KVM hosts.....? > I've not had the bridged network issues some seem to have been plagued > with, and I have several KVM hosts with bridged networking (with > multiple VLANs) using NetworkManager (using nmtui to configure a bridge > isn't hard). I decided to configure it that way just ot see how easy or > hard it was to do with NM, and to test its stability, and after passing > testing under load I popped it into production, running a few Windows 7 > guests and a couple of CentOS 7 guests.It is OK if your KVM host is on LAN cable that never is disconnected or power goes down. But I have a laptop I use first at work where I use LAN and then at home where I use WLAN only, and suspending laptop is same as disconnecting LAN, bridge is disabled and KVM bridged network unhooked, and you can never reinitialize it without at least restarting kvm, and full treatmant is shuting down VM, restarting NM then network then starting VM again... So I just shutdown VM and laptop and boot everey itme I move. Maybe I can change this behavior now.> _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos >-- Ljubomir Ljubojevic (Love is in the Air) PL Computers Serbia, Europe StarOS, Mikrotik and CentOS/RHEL/Linux consultant
On 10/4/19 11:02 AM, Ljubomir Ljubojevic wrote:> ... > It is OK if your KVM host is on LAN cable that never is disconnected > or power goes down. But I have a laptop I use first at work where I > use LAN and then at home where I use WLAN only, and suspending laptop > is same as disconnecting LAN, bridge is disabled and KVM bridged > network unhooked, and you can never reinitialize it without at least > restarting kvm, and full treatmant is shuting down VM, restarting NM > then network then starting VM again... So I just shutdown VM and > laptop and boot everey itme I move. Maybe I can change this behavior now.You and I have nearly identical use cases, interestingly enough.? My laptop that I'm using right now to type this is my development machine for a number of KVM things I do in the data center as well. Since I run it docked with ethernet on my desk, but not docked and on WiFi at home, I've had to do two things: 1.) A real shutdown when I leave work.? For some reason I've never be a fan of suspend/hibernate, and since I use LUKS I'd rather not leave the volume unlocked as it would be in a suspend/hibernate scenario; 2.) NAT-connected VMs in development, since I've never been able to get bridging to work properly over wireless (specification says it can't work, and I think that's true in practice, but I always reserve the right to be wrong!). My laptop is at least as powerful as most of our servers, and it works great for development purposes.