From 17492f0fbfed9d2eeccba01be1dd7d45ca0d60d9 Mon Sep 17 00:00:00 2001 From: Marek Marczykowski Date: Fri, 13 Jan 2012 19:08:57 +0100 Subject: [PATCH] dom0/pm-utils: start NM through systemctl after resume - when available (#404) When using SystemD, NetworkManager is started directly, so use this way. /etc/init.d/qubes_core_netvm doesn't exists in such system... Even when existed - it was already started and SystemD doesn't allow to start it again (unlike upstart/sysvinit). --- dom0/pm-utils/01qubes-suspend-netvm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dom0/pm-utils/01qubes-suspend-netvm b/dom0/pm-utils/01qubes-suspend-netvm index 443dbc1a..264c8faa 100755 --- a/dom0/pm-utils/01qubes-suspend-netvm +++ b/dom0/pm-utils/01qubes-suspend-netvm @@ -25,7 +25,7 @@ suspend_net() resume_net() { for VM in `get_running_netvms`; do - qvm-run -u root --pass_io $VM "modprobe ehci_hcd; modprobe uhci_hcd; service qubes_core_netvm start" + qvm-run -u root --pass_io $VM "modprobe ehci_hcd; modprobe uhci_hcd; [ -x /bin/systemctl ] && systemctl start NetworkManager.service || service qubes_core_netvm start" done # Ignore exit status from netvm... return 0