Description of problem: When installing oVirt Guest Tools on a Windows Server 2012 R2 (x64) VM from the oVirt tools ISO, the installer (ovirt-guest-tools-setup.exe) installs the Balloon Service with the wrong path. It sets the path as follows: C:\Program Files (x86)\oVirt Guest Tools\drivers\Balloon\w2k12R2\amd64\blnsvr.exe" But the correct path (where the files are installed) is here: C:\Program Files (x86)\oVirt Guest Tools\drivers\Balloon\2k12R2\amd64\blnsvr.exe" Note the apparent "typo" in "w2k12R2" vs. "2k12R2". As a result, the Balloon Service fails to start. The ISO I used is found here: http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/oVirt-toolsSetup/4.1-1.fc24/ However, note that this issue has been present beginning with much earlier versions of oVirt Guest Tools, going back to at least oVirt 3.6. It has been mentioned several instances on the oVirt users mailling list, but I was not able to find a corresponding bug. Version-Release number of selected component (if applicable): 4.1-1.fc24 (But it's also in earlier versions as noted above.) How reproducible: 100% Steps to Reproduce: 1. Attach latest (or any version 3.6+) oVirt Guest Tools ISO to VM 2. From VM run executable ovirt-guest-tools-setup.exe on virtual CD drive 3. From Computer Management --> Services, check the Balloon Service. Note that it is not running and it references a non-existent path. Attempting to start it manually will result in an error due to invalid path. Actual results: Balloon Service does not start Expected results: Balloon Service starts automatically Additional info: A workaround is to start a command prompt as Administrator and run the following command: sc config BalloonService binpath= "C:\Program Files (x86)\oVirt Guest Tools\drivers\Balloon\2k12R2\amd64\blnsvr.exe" DisplayName= "Balloon Service" start= auto The Balloon Service will now start.
Sent https://lists.freedesktop.org/archives/spice-devel/2017-January/035215.html upstream for that issue.
Please see my recent comments from related bug: https://bugzilla.redhat.com/show_bug.cgi?id=1416579 As suspected, they have the same underlying issue and are corrected with a recent build of oVirt Guest Tools: http://jenkins.ovirt.org/job/ovirt-wgt_master_create-rpms-fc24-x86_64_created/22/