Why its so difficult change network config without restart host (hypervisor)

[HBG]

If a hypervisor its for mission critical why cant change network configuration in real-time without restart a host (Hypervisor). Others hypervisors like VMWare ESXI and Xen Server can do it that only restarting network daemon, not the host completely. I know that others daemons like pveproxy depend that, but restart a daemon took few seconds or minutes. Restart a professional server took several minutes to restart and put online again. The scenario its not default with a central storage and a cluster. I can heard that is a security measure dont touch network files in real-time.

 

[PigLover]

+1. The single most annoying thing about Proxmox.

 

[LnxBil]

I have to say, I never used the GUI for that. Just do the plain old Debian network configuration that is available for decades.

IMHO: The reboot in PVE after network change is mostly for preventing something bad in corner cases.

 

[HBG]

Sounds good, but you can do it in gui in ESXI and XenServer, what is the diference with Proxmox. Perhaps both of them are based in Red Hat (Better approaching to enterprise level). Is a troublesome cumber that afraids several future clients. Is simple put a capcha o some warning remember the danger that you can possible do it if you are wrong or make a mistake. Im consider reboot a host hypervisor a waste of time in a mission critical environment.

 

[tom]

Changing network without restart is available since quite some time, seems you run an outdated version?

See documentation on https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_network_configuration

Just make sure that you have ifupdown2 installed (the GUI will tell you this).