ezhik Posted November 11, 2016 Share Posted November 11, 2016 It appears that stopping the array does not issue ACPI shutdown. VMs are hard stopped. unRAID 6.2.4 Quote Link to comment
jonp Posted November 11, 2016 Share Posted November 11, 2016 It appears that stopping the array does not issue ACPI shutdown. VMs are hard stopped. unRAID 6.2.4 What operating system(s) are you using for your guests. Quote Link to comment
ezhik Posted November 11, 2016 Author Share Posted November 11, 2016 It appears that stopping the array does not issue ACPI shutdown. VMs are hard stopped. unRAID 6.2.4 What operating system(s) are you using for your guests. Server 2012 R2. Installed the guest tools. Quote Link to comment
kode54 Posted November 12, 2016 Share Posted November 12, 2016 A hard stop is issued after the disk array shutdown timeout, which defaults to 60 seconds. There is a bug with the option not being configurable properly. Please check where /etc/rc.d/rc.shutdown_local reads the shutdownTimeout variable from. The WebUI tries to assign it to disk.cfg, but I know at least 6.3.0-rc4 sources ident.cfg for this option. Quote Link to comment
ezhik Posted November 12, 2016 Author Share Posted November 12, 2016 My point is I don't even see it attempting to shut down the VM. My timeout is 180 now. I'll give it another try and let you know. Quote Link to comment
jonp Posted November 13, 2016 Share Posted November 13, 2016 It appears that stopping the array does not issue ACPI shutdown. VMs are hard stopped. unRAID 6.2.4 What operating system(s) are you using for your guests. Server 2012 R2. Installed the guest tools. Did you install the Virtio serial driver as well? Sent from my SAMSUNG-SM-G935A using Tapatalk Quote Link to comment
ezhik Posted November 13, 2016 Author Share Posted November 13, 2016 It appears that stopping the array does not issue ACPI shutdown. VMs are hard stopped. unRAID 6.2.4 What operating system(s) are you using for your guests. Server 2012 R2. Installed the guest tools. Did you install the Virtio serial driver as well? Sent from my SAMSUNG-SM-G935A using Tapatalk vioserial? yes. Quote Link to comment
kode54 Posted November 13, 2016 Share Posted November 13, 2016 This may be relevant. Quote Link to comment
ezhik Posted November 13, 2016 Author Share Posted November 13, 2016 This may be relevant. I thought about that one. Quote Link to comment
ezhik Posted November 13, 2016 Author Share Posted November 13, 2016 This may be relevant. I thought about that one. I can confirm that it takes *double* execution of -- root@unraid2:~# virsh -c qemu:///system shutdown vcenter Domain vcenter is being shutdown root@unraid2:~# virsh -c qemu:///system shutdown vcenter Domain vcenter is being shutdown root@unraid2:~# virsh -c qemu:///system shutdown vcenter error: Failed to shutdown domain vcenter error: Requested operation is not valid: domain is not running --- So seems like the first execution is ignored? This is 6.2.4 diagnostics-20161112-2313.zip Quote Link to comment
ezhik Posted November 13, 2016 Author Share Posted November 13, 2016 I figured out what the issue was. Re-installed qemu services. Issues went away. Seems to be working as expected. ShutdownTimeout still should be fixed though. Quote Link to comment
kode54 Posted November 14, 2016 Share Posted November 14, 2016 I just fed double commands to mine, it seems to be a synchronization issue with libvirtd? root@Tower:~# virsh dompmsuspend "Windows 10" disk Domain Windows 10 successfully suspended root@Tower:~# virsh dompmsuspend "Windows 10" disk error: Domain Windows 10 could not be suspended error: Guest agent is not responding: QEMU guest agent is not connected root@Tower:~# virsh list Id Name State ---------------------------------------------------- root@Tower:~# Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.