[Users] Installing Windows VMs

In the QuickStart Guide, it implies that you should find a virtual floppy image for virtio-win in the ISO_DOMAIN. Or at least I can find no information on where to find/populate that image before the Guide shows its use. However, in my default 3.3 installation, there was nothing pre-populated in my ISO_DOMAIN. Should there have been? Regards, Bob

----- Original Message -----
From: "Bob Doolittle" <bob@doolittle.us.com> To: users@ovirt.org Sent: Monday, November 4, 2013 6:43:00 PM Subject: [Users] Installing Windows VMs
In the QuickStart Guide, it implies that you should find a virtual floppy image for virtio-win in the ISO_DOMAIN. Or at least I can find no information on where to find/populate that image before the Guide shows its use.
However, in my default 3.3 installation, there was nothing pre-populated in my ISO_DOMAIN. Should there have been?
Regards, Bob
I've never seen that happen on any of my installs. You can grab the drivers at http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/ Greg

On 11/05/2013 04:47 AM, Greg Sheremeta wrote:
----- Original Message -----
From: "Bob Doolittle" <bob@doolittle.us.com> To: users@ovirt.org Sent: Monday, November 4, 2013 6:43:00 PM Subject: [Users] Installing Windows VMs
In the QuickStart Guide, it implies that you should find a virtual floppy image for virtio-win in the ISO_DOMAIN. Or at least I can find no information on where to find/populate that image before the Guide shows its use.
However, in my default 3.3 installation, there was nothing pre-populated in my ISO_DOMAIN. Should there have been?
Regards, Bob
I've never seen that happen on any of my installs.
You can grab the drivers at http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/
I think would be great if anyone is willing to send some patches to pre-populate the iso domain with this package.

Il 05/11/2013 03:47, Greg Sheremeta ha scritto:
----- Original Message -----
From: "Bob Doolittle" <bob@doolittle.us.com> To: users@ovirt.org Sent: Monday, November 4, 2013 6:43:00 PM Subject: [Users] Installing Windows VMs
In the QuickStart Guide, it implies that you should find a virtual floppy image for virtio-win in the ISO_DOMAIN. Or at least I can find no information on where to find/populate that image before the Guide shows its use.
However, in my default 3.3 installation, there was nothing pre-populated in my ISO_DOMAIN. Should there have been?
Regards, Bob
I've never seen that happen on any of my installs.
You can grab the drivers at http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/
Anyone would like to step in for packaging virtio-win so we can add it to ovirt repository? So we can add it as dependency and have ISO_DOMAIN populated.
Greg _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: "Greg Sheremeta" <gshereme@redhat.com>, "Bob Doolittle" <bob@doolittle.us.com> Cc: users@ovirt.org, "Alon Bar-Lev" <alonbl@redhat.com> Sent: Tuesday, November 5, 2013 4:30:11 AM Subject: virtio-win packaging [Was Re: [Users] Installing Windows VMs]
Il 05/11/2013 03:47, Greg Sheremeta ha scritto:
----- Original Message -----
From: "Bob Doolittle" <bob@doolittle.us.com> To: users@ovirt.org Sent: Monday, November 4, 2013 6:43:00 PM Subject: [Users] Installing Windows VMs
In the QuickStart Guide, it implies that you should find a virtual floppy image for virtio-win in the ISO_DOMAIN. Or at least I can find no information on where to find/populate that image before the Guide shows its use.
However, in my default 3.3 installation, there was nothing pre-populated in my ISO_DOMAIN. Should there have been?
Regards, Bob
I've never seen that happen on any of my installs.
You can grab the drivers at http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/
Anyone would like to step in for packaging virtio-win so we can add it to ovirt repository? So we can add it as dependency and have ISO_DOMAIN populated.
I can take it, if alonbl doesn't mind me asking him a few questions about packaging :) Bug 1026930 - Package virtio-win and put it in ovirt repositories (I'll do this) Bug 1026933 - pre-populate ISO domain with virtio-win ISO (depends on 1026930, need someone to take) Greg
Greg _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

----- Original Message -----
From: "Greg Sheremeta" <gshereme@redhat.com> To: "Sandro Bonazzola" <sbonazzo@redhat.com> Cc: "Bob Doolittle" <bob@doolittle.us.com>, users@ovirt.org, "Alon Bar-Lev" <alonbl@redhat.com> Sent: Tuesday, November 5, 2013 6:49:46 PM Subject: Re: virtio-win packaging [Was Re: [Users] Installing Windows VMs]
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: "Greg Sheremeta" <gshereme@redhat.com>, "Bob Doolittle" <bob@doolittle.us.com> Cc: users@ovirt.org, "Alon Bar-Lev" <alonbl@redhat.com> Sent: Tuesday, November 5, 2013 4:30:11 AM Subject: virtio-win packaging [Was Re: [Users] Installing Windows VMs]
Il 05/11/2013 03:47, Greg Sheremeta ha scritto:
----- Original Message -----
From: "Bob Doolittle" <bob@doolittle.us.com> To: users@ovirt.org Sent: Monday, November 4, 2013 6:43:00 PM Subject: [Users] Installing Windows VMs
In the QuickStart Guide, it implies that you should find a virtual floppy image for virtio-win in the ISO_DOMAIN. Or at least I can find no information on where to find/populate that image before the Guide shows its use.
However, in my default 3.3 installation, there was nothing pre-populated in my ISO_DOMAIN. Should there have been?
Regards, Bob
I've never seen that happen on any of my installs.
You can grab the drivers at http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/
Anyone would like to step in for packaging virtio-win so we can add it to ovirt repository? So we can add it as dependency and have ISO_DOMAIN populated.
I can take it, if alonbl doesn't mind me asking him a few questions about packaging :)
No problem, but maybe this work should go into fedora and not ovirt... But first, let's have something working.
Bug 1026930 - Package virtio-win and put it in ovirt repositories (I'll do this) Bug 1026933 - pre-populate ISO domain with virtio-win ISO (depends on 1026930, need someone to take)
Greg
Greg _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

On Tue, 2013-11-05 at 11:49 -0500, Greg Sheremeta wrote:
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: "Greg Sheremeta" <gshereme@redhat.com>, "Bob Doolittle" <bob@doolittle.us.com> Cc: users@ovirt.org, "Alon Bar-Lev" <alonbl@redhat.com> Sent: Tuesday, November 5, 2013 4:30:11 AM Subject: virtio-win packaging [Was Re: [Users] Installing Windows VMs]
Il 05/11/2013 03:47, Greg Sheremeta ha scritto:
----- Original Message -----
From: "Bob Doolittle" <bob@doolittle.us.com> To: users@ovirt.org Sent: Monday, November 4, 2013 6:43:00 PM Subject: [Users] Installing Windows VMs
In the QuickStart Guide, it implies that you should find a virtual floppy image for virtio-win in the ISO_DOMAIN. Or at least I can find no information on where to find/populate that image before the Guide shows its use.
However, in my default 3.3 installation, there was nothing pre-populated in my ISO_DOMAIN. Should there have been?
Regards, Bob
I've never seen that happen on any of my installs.
You can grab the drivers at http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/
Anyone would like to step in for packaging virtio-win so we can add it to ovirt repository? So we can add it as dependency and have ISO_DOMAIN populated.
I can take it, if alonbl doesn't mind me asking him a few questions about packaging :)
Bug 1026930 - Package virtio-win and put it in ovirt repositories (I'll do this)
Very nice, thanks! Will you also package/create the virtual floppy disk? On http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/ there's only the ISO, but not the vfd and installing Windows is much easier with drivers on a floppy then changing the install CDs... Thanks, René
Bug 1026933 - pre-populate ISO domain with virtio-win ISO (depends on 1026930, need someone to take)
Greg
Greg _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

On Tue, Nov 5, 2013 at 11:49 AM, Greg Sheremeta <gshereme@redhat.com> wrote:
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: "Greg Sheremeta" <gshereme@redhat.com>, "Bob Doolittle" < bob@doolittle.us.com> Cc: users@ovirt.org, "Alon Bar-Lev" <alonbl@redhat.com> Sent: Tuesday, November 5, 2013 4:30:11 AM Subject: virtio-win packaging [Was Re: [Users] Installing Windows VMs]
Il 05/11/2013 03:47, Greg Sheremeta ha scritto:
----- Original Message -----
From: "Bob Doolittle" <bob@doolittle.us.com> To: users@ovirt.org Sent: Monday, November 4, 2013 6:43:00 PM Subject: [Users] Installing Windows VMs
In the QuickStart Guide, it implies that you should find a virtual floppy image for virtio-win in the ISO_DOMAIN. Or at least I can find
no
information on where to find/populate that image before the Guide shows its use.
However, in my default 3.3 installation, there was nothing
----- Original Message ----- pre-populated
in my ISO_DOMAIN. Should there have been?
Regards, Bob
I've never seen that happen on any of my installs.
You can grab the drivers at http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/
Anyone would like to step in for packaging virtio-win so we can add it to ovirt repository? So we can add it as dependency and have ISO_DOMAIN populated.
I can take it, if alonbl doesn't mind me asking him a few questions about packaging :)
Bug 1026930 - Package virtio-win and put it in ovirt repositories (I'll do this) Bug 1026933 - pre-populate ISO domain with virtio-win ISO (depends on 1026930, need someone to take)
This is great! Should we also consider pre-populating the Guest Additions, such as the SPICE optimized driver? -Bob

----- Original Message -----
From: "Bob Doolittle" <bob@doolittle.us.com> To: "Greg Sheremeta" <gshereme@redhat.com> Cc: users@ovirt.org Sent: Wednesday, November 6, 2013 8:29:43 AM Subject: Re: [Users] virtio-win packaging [Was Re: Installing Windows VMs]
On Tue, Nov 5, 2013 at 11:49 AM, Greg Sheremeta < gshereme@redhat.com
wrote:
----- Original Message -----
From: "Sandro Bonazzola" < sbonazzo@redhat.com >
To: "Greg Sheremeta" < gshereme@redhat.com >, "Bob Doolittle" < bob@doolittle.us.com >
Cc: users@ovirt.org , "Alon Bar-Lev" < alonbl@redhat.com >
Sent: Tuesday, November 5, 2013 4:30:11 AM
Subject: virtio-win packaging [Was Re: [Users] Installing Windows VMs]
Il 05/11/2013 03:47, Greg Sheremeta ha scritto:
----- Original Message -----
From: "Bob Doolittle" < bob@doolittle.us.com >
To: users@ovirt.org
Sent: Monday, November 4, 2013 6:43:00 PM
Subject: [Users] Installing Windows VMs
In the QuickStart Guide, it implies that you should find a virtual
floppy image for virtio-win in the ISO_DOMAIN. Or at least I can find no
information on where to find/populate that image before the Guide shows
its use.
However, in my default 3.3 installation, there was nothing pre-populated
in my ISO_DOMAIN. Should there have been?
Regards,
Bob
I've never seen that happen on any of my installs.
You can grab the drivers at
http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/
Anyone would like to step in for packaging virtio-win so we can add it to
ovirt repository?
So we can add it as dependency and have ISO_DOMAIN populated.
I can take it, if alonbl doesn't mind me asking him a few questions about packaging :)
Bug 1026930 - Package virtio-win and put it in ovirt repositories (I'll do this)
Bug 1026933 - pre-populate ISO domain with virtio-win ISO (depends on 1026930, need someone to take)
This is great!
Should we also consider pre-populating the Guest Additions, such as the SPICE optimized driver?
Might need to have different manifest in the virtual floppy that the VFD based on the size limitations eg. just enough (virtio-blk,net) in VFD but all in ISO.
-Bob
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

On 11/07/2013 12:50 PM, Andrew Cathrow wrote:
Should we also consider pre-populating the Guest Additions, such as the SPICE optimized driver? Might need to have different manifest in the virtual floppy that the VFD based on the size limitations eg. just enough (virtio-blk,net) in VFD but all in ISO.
Yes, I meant two separate items - the VFD plus the ISO, just as is done with RHEV today. Somehow that never got pushed to the Community. Rather than duplicate work, somebody might want to simply push that code upstream, assuming that's not a problem with RedHat. Also note that since the Quick Start Guide is written to assume these items are pre-populated, that should be considered a bug today. Either the QSG should be updated to remove this note until the functionality is actually present, or we can simply add the func to match the doc (which would be less work in the long run) :) As requested, I have opened a (separate) bug/rfe to track this: https://bugzilla.redhat.com/show_bug.cgi?id=1028489 I am not sure they need to be separate bugs, but I started it this way and somebody can lump this in and close this as a dup if they like. -Bob

----- Original Message -----
From: "Bob Doolittle" <bob@doolittle.us.com> To: "Andrew Cathrow" <acathrow@redhat.com> Cc: users@ovirt.org Sent: Friday, November 8, 2013 10:19:58 AM Subject: Re: [Users] virtio-win packaging [Was Re: Installing Windows VMs]
On 11/07/2013 12:50 PM, Andrew Cathrow wrote:
Should we also consider pre-populating the Guest Additions, such as the SPICE optimized driver? Might need to have different manifest in the virtual floppy that the VFD based on the size limitations eg. just enough (virtio-blk,net) in VFD but all in ISO.
Yes, I meant two separate items - the VFD plus the ISO, just as is done with RHEV today. Somehow that never got pushed to the Community. Rather than duplicate work, somebody might want to simply push that code upstream, assuming that's not a problem with RedHat.
It's just a matter of packaging. The virtio drivers are all pushed on to the fedora site and the spice driver onto spice-space.org. And the tools installers etc are on the ftp site @ ftp://ftp.redhat.com/redhat/rhev-m/3.x/src-zips/
Also note that since the Quick Start Guide is written to assume these items are pre-populated, that should be considered a bug today. Either the QSG should be updated to remove this note until the functionality is actually present, or we can simply add the func to match the doc (which would be less work in the long run) :)
As requested, I have opened a (separate) bug/rfe to track this: https://bugzilla.redhat.com/show_bug.cgi?id=1028489 I am not sure they need to be separate bugs, but I started it this way and somebody can lump this in and close this as a dup if they like.
-Bob
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

On 11/10/2013 09:43 AM, Andrew Cathrow wrote:
It's just a matter of packaging. The virtio drivers are all pushed on to the fedora site and the spice driver onto spice-space.org. And the tools installers etc are on the ftp site @ ftp://ftp.redhat.com/redhat/rhev-m/3.x/src-zips/
Is it not also a matter of wiring in appropriate engine-upload-iso commands into engine-setup or similar, so that the ISO domain is actually populated with this content? -Bob

On 11/10/2013 01:34 PM, Bob Doolittle wrote:
On 11/10/2013 09:43 AM, Andrew Cathrow wrote:
It's just a matter of packaging. The virtio drivers are all pushed on to the fedora site and the spice driver onto spice-space.org. And the tools installers etc are on the ftp site @ ftp://ftp.redhat.com/redhat/rhev-m/3.x/src-zips/
Is it not also a matter of wiring in appropriate engine-upload-iso commands into engine-setup or similar, so that the ISO domain is actually populated with this content?
yes, but that's a trivial plugin. since the installer creates the default nfs iso domain on the engine, it just needs to copy it over to the folder. (or does it create a link so rpm updates of the iso/vfd will be always visible there - sandro?) for other iso domains, currently admin needs to push via iso uploader. thanks, Itamar

On 11/04/2013 09:47 PM, Greg Sheremeta wrote:
I've never seen that happen on any of my installs.
You can grab the drivers at http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/
I'm trying to help somebody update the Quick Start Guide in the interim until these items are pre-populated. But if I go to that link, I see only: http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/virtio-win... In other words, no vfd. Oddly, there was one there in the past: http://web.archive.org/web/20110501124422/http://alt.fedoraproject.org/pub/a... Even more oddly, the old one has what looks like a more recent version number: virtio-win-1.1.16.vfd Can anybody explain how this has transpired? Where did the old vfd go, and why are the version numbers going backwards? Is there an actual vfd in existence today that anybody can safely download and use engine-iso-uploader with? There is also this one, which is actually what I wound up using: https://launchpad.net/kvm-guest-drivers-windows/20120712/20120712/+download/... Are either of these VFDs safe to use? Is one preferred? Guidance please? Thanks, Bob
participants (7)
-
Alon Bar-Lev
-
Andrew Cathrow
-
Bob Doolittle
-
Greg Sheremeta
-
Itamar Heim
-
René Koch (ovido)
-
Sandro Bonazzola