Bug 712008

rhevm build ic122
vdsm version vdsm-4.9-73.el6.x86_64

I think the accepted (but kind of long winded) method of making this work is to accept your Hypervisor default for disk type (IDE I believe)... Let the install complete...

Then add a VirtIO device, install the drivers...

Then change the main drive to VirtIO.

I've done this several times and it's worked well so far.

(In reply to comment #0)
> Description of problem:
> 
> Blue screen when trying to install windows7x64 with virtio disk.
> installing Windows7x64 with floppy disk that contain viostor driver for virtio
> disk. 

Hi Tomer,
Could you point me to the Windows distribution media you are using?

> Blue screen happen right after viostor.inf loaded in order to prepare the
> virtio disk to be booting disk for windows installation.

Sorry, I can hardly understand this sentence. Does it happen on install or on boot?

Best regards,
Vadim. 

Btw, the bug has a "regression" keyword. Is it true? Could you check whether
the previous driver was fine?   
> 
> virtio version 1.0.0.45801

In this case, I used with Windows7,but I don't think this is matter.

It's happened before the os installation,the installation wizard ask me to install the driver of virtIO device, in order to identify this "unknown device".

Actually,this the first time that this case running on vds host that base on rhel6. I used with the same driver  virtio version 1.0.0.45801 on vds host that base on rhel5.6 and it's works well.

(In reply to comment #6)
> In this case, I used with Windows7,but I don't think this is matter.
> 

The only one, I can reproduce this problem, was ../qanashead/export/ISOS/windows/Windows7-ent.iso
I need to know whether any other image was used in your case.

> It's happened before the os installation,the installation wizard ask me to
> install the driver of virtIO device, in order to identify this "unknown
> device".
> 
> Actually,this the first time that this case running on vds host that base on
> rhel6. I used with the same driver  virtio version 1.0.0.45801 on vds host that
> base on rhel5.6 and it's works well.

With the same installation image?

Best regards,
Vadim.

I used with image en_windows_7_enterprise_x64_dvd_x15-70749.iso that set in qanashead.

(In reply to comment #6)
> In this case, I used with Windows7,but I don't think this is matter.
> 
> It's happened before the os installation,the installation wizard ask me to
> install the driver of virtIO device, in order to identify this "unknown
> device".
> 
> Actually,this the first time that this case running on vds host that base on
> rhel6. I used with the same driver  virtio version 1.0.0.45801 on vds host that
> base on rhel5.6 and it's works well.

Can you try reproducing this problem with the latest virtio-win-1.2.0-1.el6 drivers from https://brewweb.devel.redhat.com/buildinfo?buildID=163534?

I checked, latest version virtio-win-1.2.0.vfd succeed to solved this bug!

(In reply to comment #10)
> I checked, latest version virtio-win-1.2.0.vfd succeed to solved this bug!

Thank you, Tomer.

I would suggest to close this bug as NOTABUG due to the following reason:
1.0.0.45801 was created for 5.X. There were some HW resources related changes since then. Even though our RelEng team backports the latest drivers into RHEL5.X virtio-win RPM, you probably picked up a very old one. You can try one of the latest from  https://brewweb.devel.redhat.com/buildinfo?buildID=146124,
it should work well on 6.1.

In any case, we should use 6.1 virtio-win drivers when running Windows VMs on top
of 6.1 host.

Cheers,
Vadim.

Seems to be solved for recent versions.