Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-user-avatar domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the really-simple-ssl domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the twentyfifteen domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6121
The Idiot installs the QEMU agent on a Windows 10 VM on Proxmox – Jon Spraggins

The Idiot installs the QEMU agent on a Windows 10 VM on Proxmox

So yeah, this one’s on me.  This should be added to the Windows 10 on Proxmox guide, but I figured a post on it’s own wouldn’t hurt.So what is the QEMU Agent?  Straight from the libvirt website:

It is a daemon program running inside the domain which is supposed to help management applications with executing functions which need assistance of the guest OS. For example, freezing and thawing filesystems, entering suspend.

Essentially, it facilitates certain actions from within Proxmox.  Notably, startup and shutdown.

The How To:

  1. With the VM Shut down, go into the VM’s Options in Proxmox
  2. Check the “Yes” box to enable QEMU
  3. Start the VM
  4. Manually install the vioserial drivers from the virtio image
  5. Install the Qemu Guest Agent virtioimage: guest-agent/qemu-ga-x86.msi (I haven’t had much luck with the x64 version)
  6. Reboot the OS from within the VM
  7. Upon login, open Services.msc.  You’ll notice the QEMU Agent is now a service.  If it’s not started, then start it.
  8. Voilà!  If all goes well, you now have a VM that interacts more closely with Proxmox!

One thought on “The Idiot installs the QEMU agent on a Windows 10 VM on Proxmox”

  1. This article and the main one on Windows 10 in Proxmox really helped me set it up when I was first starting out. Thanks for the guide, a lot more people appreciate it than you might think.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.