do you know if the upstream virtio drivers are correctly signed? In particular:
http://resources.ovirt.org/pub/ovirt-3.6/rpm/el6/noarch/ovirt-guest-tools-is...
This is one of the first builds signed only with the new SHA-2 based certificate which is not supported on Windows 7 out-of-the-box. Installing a hotfix per:
https://technet.microsoft.com/en-us/library/security/3033929.aspx
will fix it.
Thanks Ladi.
If yes, any idea what can be the issue Cam faces?
As for the original BSOD, the problem there was trying to load Win8 vioscsi.sys on Win7 and should be fixed by pointing Windows to the Win7 subdirectory like you wrote.
Relevant bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1289406 (signing issue) https://bugzilla.redhat.com/show_bug.cgi?id=1296633 (target OS version mismatch)
The crash mentions vioscsi.sys, not viostor.sys, which the second bug report mentioned. The other thing is that the crash happens after the install, upon first reboot. The contents of the Windows guest tools ISO are copied to the Windows Deployment server from where they are installed. When I try an alternative install using a Win 7 ISO, rather than PXE boot, it fails at a different point. This is using the oVirt Windows guest tools ISO that is in the 3.6.3 repos. When it comes to installing to disk, I change the CD to the guest tools ISO and browse to the win7 drivers (ovirt-tools-setup/drivers/virtio/viostor/w7/amd64/, which has the viostor drivers), but then the installer complains it cannot install on the disk, even though it can successfully create partitons on it (see attached screenshot). Thanks, Cam
From: "Arman Khalatyan" <arm2arm@gmail.com> To: "Cam Mac" <iucounu@gmail.com> Cc: "Tomas Jelinek" <tjelinek@redhat.com>, "users" <users@ovirt.org> Sent: Tuesday, May 10, 2016 9:19:49 PM Subject: Re: [ovirt-users] vioscsi.sys BSOD with Win 7
Same bsod was with win2008 server, in order to fix it we changed nics to e1000 and disks to IDE. Now it boots w/o trouble. Am 10.05.2016 7:43 nachm. schrieb "Cam Mac" <iucounu@gmail.com>:
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-is...
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
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...
> ), 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,
----- Original Message ----- process 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