We already ship lib/systemd/system-sleep/hibinit-agent that does post things in hibinit-resume to workaround things. Including stuff about networking, due to previous issues with xen-netfront.
Given we already restart systemd-networkd, I wonder if we should do better and not keep xen-netfront loaded in the kernel across suspend and resume.
as in
1) extend hibinit-agent.system-sleep to also have pre command
2) in the pre step unload xen-netfront
3) in the post step only load xen-netfront
4) potentially still stop systemd-networkd in pre; which will be restarted after loading xen-netfront in post
Since xen-netfront is causing us issues; and we are already unloading and reloading it; it makes sense to unload it before suspending altogether.
We already ship lib/systemd/ system- sleep/hibinit- agent that does post things in hibinit-resume to workaround things. Including stuff about networking, due to previous issues with xen-netfront.
Given we already restart systemd-networkd, I wonder if we should do better and not keep xen-netfront loaded in the kernel across suspend and resume.
as in agent.system- sleep to also have pre command
1) extend hibinit-
2) in the pre step unload xen-netfront
3) in the post step only load xen-netfront
4) potentially still stop systemd-networkd in pre; which will be restarted after loading xen-netfront in post
Since xen-netfront is causing us issues; and we are already unloading and reloading it; it makes sense to unload it before suspending altogether.