January 23, 20197 yr I am running two Windows 10 VMs. On one of the VMs I am able to install the 64 bit version of qemu guest agent. On the other VM I can only install an older version of the 32 bit qemu guest agent. This is the error I get: Any suggestions on how to solve this? A search of the Internet did not turn up anything useful. mediaserver-diagnostics-20190123-0743.zip
February 22, 20197 yr I guess no one is installing the guest agent. At least I never did. What are the benefits to doin so? @dlandon
February 22, 20197 yr Among other things, you can have unRaid set to hibernate the VM instead of shutting it down when stopping the array. Very useful in case of a power failure, etc
February 22, 20197 yr Author 24 minutes ago, bastl said: I guess no one is installing the guest agent. At least I never did. What are the benefits to doin so? @dlandon You won't be able to shutdown or hibernate the VM from the VM menu. 4 minutes ago, Squid said: Among other things, you can have unRaid set to hibernate the VM instead of shutting it down when stopping the array. Very useful in case of a power failure, etc Correct. I believe shutdown of the VM will also not work.
February 22, 20197 yr 1 minute ago, dlandon said: You won't be able to shutdown or hibernate the VM from the VM menu. Shutdown a VM from the Unraid ui or via commandline works fine without the agent for Windows and for Linux guests i use.
February 22, 20197 yr Shutdowns do work for the menu. The thing for me is that a windows shutdown can take anywhere between 30 seconds and an hour depending on updates to be installed etc. Not a good thing when running on batterySent via telekinesis
February 22, 20197 yr 10 minutes ago, bastl said: Good point, MS updates 😡 Set network connection in windows to metered. It stops SOME of the bad behaviour.
February 22, 20197 yr Author So, back to the original reason for posting. How do I get past the qemu 64 bit install problem? The newer drivers insist on a 64 bit install, but it doesn't work so I have to go back to older drivers and install the 32 bit version.
February 22, 20197 yr I believe it also has to do with the "Balloon" driver stuff that no one uses on Windows because it is buggy and doesn't really work... this shouldn't really help, but there is a new version of this, you can get it here: https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/virtio-win.iso Also, need the XML files from the VM in question... Your libvirt logs has some things I have never seen that seems to pertain... Some of this is normal (at least they show up on mine), but there is also stuff about Qemu monitors and Guest agents being unavailable... This seems like something to do with the VM XML file... ...... 2019-01-23 10:18:40.187+0000: 7155: error : qemuMonitorIO:718 : internal error: End of file from qemu monitor 2019-01-23 10:21:01.170+0000: 7158: error : virDomainDefRejectDuplicateControllers:3966 : XML error: Multiple 'scsi' controllers with index '0' 2019-01-23 10:21:19.120+0000: 7158: error : virDomainDefRejectDuplicateControllers:3966 : XML error: Multiple 'scsi' controllers with index '0' 2019-01-23 10:26:18.213+0000: 7160: warning : qemuDomainObjTaint:7831 : Domain id=3 name='Handyman' uuid=913f649f-9692-6e90-629e-94f6e067c0c0 is tainted: high-privileges 2019-01-23 10:26:18.213+0000: 7160: warning : qemuDomainObjTaint:7831 : Domain id=3 name='Handyman' uuid=913f649f-9692-6e90-629e-94f6e067c0c0 is tainted: host-cpu 2019-01-23 10:30:15.849+0000: 7157: warning : qemuDomainObjTaint:7831 : Domain id=4 name='Handyman' uuid=913f649f-9692-6e90-629e-94f6e067c0c0 is tainted: high-privileges 2019-01-23 10:30:15.849+0000: 7157: warning : qemuDomainObjTaint:7831 : Domain id=4 name='Handyman' uuid=913f649f-9692-6e90-629e-94f6e067c0c0 is tainted: host-cpu 2019-01-23 10:31:50.426+0000: 7159: error : qemuAgentSend:866 : Guest agent is not responding: Guest agent not available for now ......
February 22, 20197 yr Author 29 minutes ago, Warrentheo said: I believe it also has to do with the "Balloon" driver stuff that no one uses on Windows because it is buggy and doesn't really work... this shouldn't really help, but there is a new version of this, you can get it here: https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/virtio-win.iso Also, need the XML files from the VM in question... Your libvirt logs has some things I have never seen that seems to pertain... Some of this is normal (at least they show up on mine), but there is also stuff about Qemu monitors and Guest agents being unavailable... This seems like something to do with the VM XML file... ...... 2019-01-23 10:18:40.187+0000: 7155: error : qemuMonitorIO:718 : internal error: End of file from qemu monitor 2019-01-23 10:21:01.170+0000: 7158: error : virDomainDefRejectDuplicateControllers:3966 : XML error: Multiple 'scsi' controllers with index '0' 2019-01-23 10:21:19.120+0000: 7158: error : virDomainDefRejectDuplicateControllers:3966 : XML error: Multiple 'scsi' controllers with index '0' 2019-01-23 10:26:18.213+0000: 7160: warning : qemuDomainObjTaint:7831 : Domain id=3 name='Handyman' uuid=913f649f-9692-6e90-629e-94f6e067c0c0 is tainted: high-privileges 2019-01-23 10:26:18.213+0000: 7160: warning : qemuDomainObjTaint:7831 : Domain id=3 name='Handyman' uuid=913f649f-9692-6e90-629e-94f6e067c0c0 is tainted: host-cpu 2019-01-23 10:30:15.849+0000: 7157: warning : qemuDomainObjTaint:7831 : Domain id=4 name='Handyman' uuid=913f649f-9692-6e90-629e-94f6e067c0c0 is tainted: high-privileges 2019-01-23 10:30:15.849+0000: 7157: warning : qemuDomainObjTaint:7831 : Domain id=4 name='Handyman' uuid=913f649f-9692-6e90-629e-94f6e067c0c0 is tainted: host-cpu 2019-01-23 10:31:50.426+0000: 7159: error : qemuAgentSend:866 : Guest agent is not responding: Guest agent not available for now ...... Thanks. I'll take a look at the new drivers. I fixed the scsi error. I hadn't changed my xml with the editor in a long time and apparently messed things up with some manual editing. Changing things with the editor straightened things out.
February 22, 20197 yr Author 1 hour ago, Warrentheo said: I believe it also has to do with the "Balloon" driver stuff that no one uses on Windows because it is buggy and doesn't really work... If this is true, then I have a conundrum. I pass through a pci GPU to that VM and according to the VM editor help: If you are passing through a PCI device, only the initial memory value is used and the max memory value is ignored. Not only does that apply, but the editor disables the balloon device: <memballoon model='none'/> So I can't pass through a pci device and install the newer 64 bit qemu guest agent because there is no balloon device? Seems like a bit of a conflict.
February 22, 20197 yr Mine also is: <memballoon model='none'/> And NVidia GTX1070 passthrough is working fine for me for months now... Basically the Balloon devices should be ignored for Windows, it just is not designed for it to work that well without major headaches on the part of the user... Edit: and the Sub Answer to that is that "Min Memory" and "Max Memory" should always be the same on Windows VM's... Edited February 22, 20197 yr by Warrentheo
February 22, 20197 yr Author Manually added the balloon device to the xml and got the driver working, but still the same issue with the 64 bit qemu driver. I always thought it was the serial driver that was needed for the guest agent. 4 minutes ago, Warrentheo said: Edit: and the Sub Answer to that is that "Min Memory" and "Max Memory" should always be the same on Windows VM's... It makes sense. This is what I always do on Windows VMs. I just may have to stick with an older 32 bit guest agent and not worry about it.
February 22, 20197 yr 7 minutes ago, dlandon said: Manually added the balloon device to the xml and got the driver working, but still the same issue with the 64 bit qemu driver. I always thought it was the serial driver that was needed for the guest agent. It makes sense. This is what I always do on Windows VMs. I just may have to stick with an older 32 bit guest agent and not worry about it. In one sense, it doesn't really matter if all you use it for is for the host to notify of system shutdown/reboot/hibernate... The 32-bit should work fine for that... That said, the 64-bit version not installing points to some other issue that should not be happening, and might be a symptom of something else that might bite you in the butt later... This would bother the hell out of me 😛 But I suppose it is up to you 😉 Edit: Silly question, but are you sure you installed the 64-bit version of windows? Edited February 22, 20197 yr by Warrentheo
February 22, 20197 yr Author 30 minutes ago, Warrentheo said: Edit: Silly question, but are you sure you installed the 64-bit version of windows? Yes. The latest qemu guest agent for 32 bit complains that it won't install on a 64 bit machine.
May 3, 20197 yr I'm getting the same error when attempting to install qemu-ga-x64.msi on either of my Win10 VMs with GPU passthrough(rx560/rx570). Installs fine on a clean install headless VM. Any more suggestions?
May 3, 20197 yr 5 minutes ago, WashingtonMatt said: I'm getting the same error when attempting to install qemu-ga-x64.msi on either of my Win10 VMs with GPU passthrough(rx560/rx570). Installs fine on a clean install headless VM. Any more suggestions? Install headless (vnc and later rdp) then add GPU afterwards? I've always happened to do my installs this way and never had an issue with installing the agent (win7,win10,server2016 etc).
May 3, 20197 yr Yes, that will certainly be the process in the future, however, I'd really like to avoid rebuilding my VMs if possible.
December 3, 20196 yr I don't know what changed, but But I was mucking around with this again, and the agent installed on one VM. I thought I had figured out, but failed on the 2nd VM. I applied the 1903 update, and then the agent installed on the 2nd VM. First VM didn't have 1903 yet... so I dunno, but it's finally installed and working. Ymmv :shrug:
Archived
This topic is now archived and is closed to further replies.