Update 12/17/2019: Added logic to wait for VM to be suspended before suspending the shypervisor
Update 12/8/2019: After switching VMs I needed to tweak the pair of scripts. I modified it to make all the magic happen on the hypervisor; the VM simply needs to SSH into the hypervisor and call the script. The hypervisor now also needs access to SSH via public key to the VM to tell it to suspend.
#!/bin/sh #ProxMox suspend script part 1 of 2 #To be run on the VM #All this does is call the suspend script on the hypervisor #This could also just be a bash alias ####### Variables ######### HYPERVISOR= #Name / IP of the hypervisor SSH_USER= #User to SSH into hypervisor as HYPERVISOR_SCRIPT= #Path to part 2 of the script on the hypervisor ####### End Variables ###### #Execute server suspend script ssh $SSH_USER@$HYPERVISOR "$HYPERVISOR_SCRIPT" &
#!/bin/bash
#ProxMox suspend script part 2 of 2
#Script to run on the hypervisor, it waits for VM to suspend and then suspends itself
#It relies on passwordless sudo configured on the VM as well as SSH keys to allow passwordless SSH access to the VM from the hypervisor
#It resumes the VM after it resumes itself
#Called from the VM
########### Variables ###############
VM= #Name/IP of VM to SSH into
VM_SSH_USER= #User to ssh into the vm with
VMID= #VMID of VM you wish to suspend
########### End Variables############
#Tell guest VM to suspend
ssh $VM_SSH_USER@$VM "sudo systemctl suspend"
#Wait until guest VM is suspended, wait 5 seconds between attempts
while [ "$(qm status $VMID)" != "status: suspended" ]
do
echo "Waiting for VM to suspend"
sleep 5
done
#Suspend hypervisor
systemctl suspend
#Resume after shutdown
qm resume $VMID
I have a desktop running ProxMox. My GUI is handled via a virtual machine with physical hardware passed through it. The challenge with this setup is getting suspend & resume to work properly. I got it to work by suspending the VM first, then the host; on resume, I power up the host first, then resume the VM. Doing anything else would cause hardware passthrough problems that would force me to reboot the VM.
I automated the suspend process by using two scripts: one for the VM, and one for the hypervisor. The first script is run on the VM. It makes an SSH command to the hypervisor (thanks to this post) to instruct it to run the second half of the script; then initiates a suspend of the VM.
The second half of the script waits a few seconds to allow the VM to suspend itself, then instructs the hypervisor to also go into suspend. I had to split these into two scripts because once the VM is suspended, it can’t issue any more commands. Suspending the hypervisor must happen after the VM itself is suspended.
Here is script #1 (to be run on the VM) It assumes you have already set up a private/public key pair to allow for passwordless login into the hypervisor from the VM.
#!/bin/sh #ProxMox suspend script part 1 of 2 #Tto be run on the VM so it suspends before the hypervisor does ####### Variables ######### HYPERVISOR=HYPERVISOR_NAME_OR_IP SSH_USER=SSH_USER_ON_HYPERVISOR HYPERVISOR_SCRIPT_LOCATION=NAME_AND_LOCATION_OF_PART2_OF_SCRIPT ####### End Variables ###### #Execute server suspend script, then suspend VM ssh $SSH_USER@$HYPERVISOR $HYPERVISOR_SCRIPT_LOCATION & #Suspend systemctl suspend
Here is script #2 (which script #1 calls), to be run on the hypervisor
#!/bin/bash #ProxMox suspend script part 2 of 2 #Script to run on the hypervisor, it waits for VM to suspend and then suspends itself #It resumes the VM after it resumes itself ########### Variables ############### #Specify VMid you wish to suspend VMID=VMID_OF_VM_YOU_WANT_TO_SUSPEND ########### End Variables############ #Wait 5 seconds before doing anything to allow for VM to suspend sleep 5 #Suspend hypervisor systemctl suspend #Resume after shutdown qm resume $VMID
It works on my machine 🙂