[SOLVED] VM shutdown restults in timeout

Discussion in 'Proxmox VE: Installation and configuration' started by andy77, May 16, 2019.

  1. andy77

    andy77 Member
    Proxmox Subscriber

    Joined:
    Jul 6, 2016
    Messages:
    206
    Likes Received:
    5
    Hi everyone,

    I have a problem with VM shutdowns, specificaly Windows Server 2016 VMs.
    When I use the shutdown button in the Web UI, sometimes Server 2016 shuts down without issue, but other times Proxmox gets Error "TASK ERROR: VM quit/powerdown failed - got timeout".

    After following this wiki article, it worked for most, but not for all:
    https://pve.proxmox.com/wiki/Acpi_kvm

    Is there another option to check in Windows Server 2016, and why does the GPO Option work on most, but not on all?

    Thanks in advance for your answers.

    Regards
    Andreas
     
  2. tom

    tom Proxmox Staff Member
    Staff Member

    Joined:
    Aug 29, 2006
    Messages:
    13,460
    Likes Received:
    393
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. andy77

    andy77 Member
    Proxmox Subscriber

    Joined:
    Jul 6, 2016
    Messages:
    206
    Likes Received:
    5
    Thank you, I will try that.
     
  4. andy77

    andy77 Member
    Proxmox Subscriber

    Joined:
    Jul 6, 2016
    Messages:
    206
    Likes Received:
    5
    One more question:

    Can a VM "harm" the Proxmox Nodes or other VMs, if the Guest Agent is activated?

    Regards
    Andreas
     
    #4 andy77, May 17, 2019
    Last edited: May 22, 2019
  5. andy77

    andy77 Member
    Proxmox Subscriber

    Joined:
    Jul 6, 2016
    Messages:
    206
    Likes Received:
    5
    Hi,

    got any idea?


    Regards
    Andreas
     
  6. Stoiko Ivanov

    Stoiko Ivanov Proxmox Staff Member
    Staff Member

    Joined:
    May 2, 2018
    Messages:
    1,198
    Likes Received:
    102
    * The design and function of the qemu-guest-agent is to run commands inside the VM, which are initiated by the hypervisor - see [0,1,2].
    * In theory it is not meant to change the hypervisor, let alone other VMs in any way
    * In practice complex pieces of software have bugs, which can lead to security-exploits (I guess this is what you mean with "harm") in certain cirumstances, this also applies to the qemu-guest-agent (see e.g. [3])

    hope this helps


    [0] https://pve.proxmox.com/wiki/Qemu-guest-agent
    [1] https://wiki.qemu.org/Features/GuestAgent
    [2] https://wiki.libvirt.org/page/Qemu_guest_agent
    [3] https://www.openwall.com/lists/oss-security/2019/05/22/4
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. andy77

    andy77 Member
    Proxmox Subscriber

    Joined:
    Jul 6, 2016
    Messages:
    206
    Likes Received:
    5
    Okay, thanks for your answer.

    So if I always update the windows virtioserial driver and also the guest agent, there shouldn't really be problems, right?

    Regards
    Andreas
     
  8. Stoiko Ivanov

    Stoiko Ivanov Proxmox Staff Member
    Staff Member

    Joined:
    May 2, 2018
    Messages:
    1,198
    Likes Received:
    102
    usually an update to the newest stable version is a good idea.
    That being said, there have been some occasions where windows versions work better with an older virtioserial driver

    so generally speaking - do update, if it doesn't work as expected - maybe try an older stable release

    hope this helps!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. andy77

    andy77 Member
    Proxmox Subscriber

    Joined:
    Jul 6, 2016
    Messages:
    206
    Likes Received:
    5
    Thank you very much.


    Regards
    Andreas
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice