You are correct, we still need to package the ISO as RPM package, and get the deps. in
order, so it will be automatically installed as part of the oVirt installation.
The version you should use is:
It's the latest available version, and the one that will be probably released, unless
we'll find some serious issues that will require fixing.
The tools should work on everything from XP to Win 8.1 (XP 32 bit, Vista 32/64 bit (this
is unsupported d/s), Win7 32/64 bit, Win 8 32/64 bit, Win 8.1 32/64 bit), including
Windows Servers 2K3 to 2K8R2 (2K3 32/64 bit, 2K8 32/64 bit, 2K8R2 64 bit). It's not
supposed to work on Windows Server 2K12 and 2K12R2.
Generally the more OS versions you can test this on, the better, but of course getting and
installing every one of these may be time consuming.
The installation process should work fine, and upon the installation all the drivers (but
the VirtIO-SCSI) should be installed, and oVirt Guest Agent and Spice Guest Agent should
be installed and running.
During the installation on some Windows versions you may get a popup message box asking if
it's OK to install drivers. This is normal since the drivers provided to u/s are not
WHQL'd, and may appear up to 4 times (once per each driver).
The un-installation should also work, however note that unlike d/s it doesn't remove
the device drivers from the OS, but only removes the agents and removes the files the the
oVirt folder under "Program Files".
If you have any further questions feel free to ask.
Thanks in advance,
----- Original Message -----
From: "Einav Cohen" <ecohen(a)redhat.com>
To: "Lev Veyde" <lveyde(a)redhat.com>
Cc: devel(a)ovirt.org, "Greg Sheremeta" <gshereme(a)redhat.com>
Sent: Monday, June 30, 2014 4:56:43 PM
Subject: ovirt-3.5 test day: Package oVirt windows guest tools ISO and put it in ovirt
I am assigned to test the feature in $subject as part of the ovirt-3.5 test day.
it says in  to "Talk to Lev" (attached).
So I'm talking :)
- in the BZ  description, it mentions that it would be nice to (a) have the
windows guest tools ISO pre-populated in the ISO domain, but as a first step -
(b) virtio-win should be RPM packaged and put it in ovirt (yum?) repositories.
IIUC - neither (a) nor (b) were done - the ISO was simply put in
(not RPM packaged or anything like that) - correct?
- which ISO should I use for the test-day? the one that appears in comment #5
in  as "master"? "3.5.0 pre release"? something else?
- any particular windows versions that I should test (or, should NOT test)?
- anything else that I should know about this feature? anything in particular
that I should focus on?
 Bug 1026930 - OVIRT35 - [RFE] Package oVirt windows guest tools ISO and put it in