Hi Tomas,

The install went ok, but Windows complains:

"File: \windows\system32\drivers\vioscsi.sys

status: 0xc0000428

Windows cannot verify the digital signature for this file"

Regards,

Campbell

On Tue, May 10, 2016 at 6:29 PM, Cam Mac <iucounu@gmail.com> wrote:

Hi Tomas,

Thanks, I will test that later tonight and let you know.

Regards,

Cam

On Tue, May 10, 2016 at 3:28 PM, Tomas Jelinek <tjelinek@redhat.com> wrote:

Hi,

please try to install this guest tools:
http://resources.ovirt.org/pub/ovirt-3.6/rpm/el6/noarch/ovirt-guest-tools-iso-3.6-3.fc23.noarch.rpm

Also please make sure you point windows to the correct driver in the sub-directory for w7

Tomas

----- Original Message -----
> From: "Cam Mac" <iucounu@gmail.com>
> To: users@ovirt.org
> Sent: Monday, May 9, 2016 7:28:57 PM
> Subject: [ovirt-users] vioscsi.sys BSOD with Win 7
>
> Hi,
>
> I'm running oVirt 3.6.3.4-1.el7.centos and when I install a Win 7 guest VM,
> using VirtIO disk, networking etc, it goes through the install process ok,
> but blue screens upon boot with a vioscsi.sys error (attached). I have tried
> the official version ovirt-guest-tools-iso 3.6.0 0.2_master.fc22, as well as
> some earlier and later versions. I am using a PXE boot method with a Windows
> deployment server, which has the drivers from the oVirt tools ISO installed
> (indeed, it picks up the drive and networking and I can see it installing
> the drivers). I have tried with the generic IDE and rtl8139 config on the
> guest, and it also fails with the same vioscsi.sys error after rebooting
> upon finishing installation even though I'm using IDE as the disk driver.
>
> I have uploaded a win 7 x64 ISO and tried installing that, and it loads the
> VirtIO viostor driver (using the method at:
> https://www.ovirt.org/documentation/how-to/virtual-machines/create-a-windows-7-virtual-machine/
> ), and even manages to partition the disks, but fails to install on the disk
> (screenshot attached).
>
> I've tried temporarily removing the vioscsi files from the install server as
> a last resort, but as expected it fails to install properly, though I
> thought it used the viostor driver instead.
>
> Thanks for any help.
>
> Regards,
>
> Cam
>

> _______________________________________________
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users