Re: [ovirt-users] vioscsi.sys BSOD with Win 7

2016-09-29 Thread Ladi Prosek 
On Wed, May 11, 2016 at 5:45 PM, Ladi Prosek <lpro...@redhat.com> wrote:
> On Wed, May 11, 2016 at 1:46 PM, Cam Mac <iuco...@gmail.com> wrote:
>> Hi Ladi,
>>
>>>
>>>
>>> We will try just the win 7 drivers that shipped with 3.6.3 rather than the
>>> SHA-2 signed FC23 drivers and I'll get back to you. I have a question:
>>> if I try to build a Win2k12 server via WDS, I assume I will have to add
>>> the 2k12 drivers and then remove them again if I go to build a Win 7 VM
>>> as Win 7 will presumably try to pick up the 2k12 driver? Or can they
>>> co-exist?
>>> WDS has a build process whenever drivers are added (e.g., for KVM, VMWare
>>> etc) for available drivers. Do you know when the fix will be available?
>>>
>>
>> Sorry for replying to my own post, but it turns out that there should be a
>> way in WDS to
>> set separate build directories for Win 7 and 2012, so please disregard that
>> question.
>>
>> The build appears to be going well so far, no BSODs.
>>
>> Thanks very much for the help Ladi!
>
> No worries, I'm glad that you're not blocked anymore.
>
>> Any ideas on when the newly signed drivers will be available?
>
> Shouldn't take more than a few weeks, I'll keep you posted.

Just a quick update, hope it's ok to reply to this old thread.

It took longer than expected but virtio-win-0.1.126-1.noarch has just
been released and it fixes both the signing issue (no more SHA-2
signatures) and the versioning issue (minimum target Windows version
is now declared by all drivers which should prevent the version
mixups).

Thanks,
Ladi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] vioscsi.sys BSOD with Win 7

2016-05-16 Thread Ladi Prosek 
On Wed, May 11, 2016 at 1:46 PM, Cam Mac  wrote:
> Hi Ladi,
>
>>
>>
>> We will try just the win 7 drivers that shipped with 3.6.3 rather than the
>> SHA-2 signed FC23 drivers and I'll get back to you. I have a question:
>> if I try to build a Win2k12 server via WDS, I assume I will have to add
>> the 2k12 drivers and then remove them again if I go to build a Win 7 VM
>> as Win 7 will presumably try to pick up the 2k12 driver? Or can they
>> co-exist?
>> WDS has a build process whenever drivers are added (e.g., for KVM, VMWare
>> etc) for available drivers. Do you know when the fix will be available?
>>
>
> Sorry for replying to my own post, but it turns out that there should be a
> way in WDS to
> set separate build directories for Win 7 and 2012, so please disregard that
> question.
>
> The build appears to be going well so far, no BSODs.
>
> Thanks very much for the help Ladi!

No worries, I'm glad that you're not blocked anymore.

> Any ideas on when the newly signed drivers will be available?

Shouldn't take more than a few weeks, I'll keep you posted.

Thanks,
Ladi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] vioscsi.sys BSOD with Win 7

2016-05-16 Thread Ladi Prosek 
On Wed, May 11, 2016 at 8:55 AM, Tomas Jelinek  wrote:
> Hi Ladi,
>
> 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-iso-3.6-3.fc23.noarch.rpm

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.

> 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)

Thanks,
Ladi

> thank you,
> Tomas
>
> - Original Message -
>> From: "Arman Khalatyan" 
>> To: "Cam Mac" 
>> Cc: "Tomas Jelinek" , "users" 
>> 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" :
>>
>> > Hi Tomas,
>> >
>> > The install went ok, but Windows complains:
>> >
>> > "File: \windows\system32\drivers\vioscsi.sys
>> > status: 0xc428
>> > Windows cannot verify the digital signature for this file"
>> >
>> > Regards,
>> >
>> > Campbell
>> >
>> > On Tue, May 10, 2016 at 6:29 PM, Cam Mac  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 
>> >> 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" 
>> >>> > 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
>> >
>> >
>>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] vioscsi.sys BSOD with Win 7

2016-05-16 Thread Ladi Prosek 
On Wed, May 11, 2016 at 11:18 AM, Cam Mac  wrote:
> Oops forgot attachment.
>
> On Wed, May 11, 2016 at 10:17 AM, Cam Mac  wrote:
>>>
>>>
>>> > 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-iso-3.6-3.fc23.noarch.rpm
>>>
>>> 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.

No worries. I forgot to mention that this will be fixed in a future
driver release, either by dual-signing the binaries with both SHA-1
and SHA-2 or only SHA-1. Requiring the Windows hotfix is a workaround
until then.

>>>
>>> > 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.

It is the same issue though, I have checked the timestamp in your BSOD
screenshot. The driver running on the system at the time of crash was
a build targeted at Win8 or newer.

>> 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.

Can you feed only the Win7 subset of the ISO to WDS? Sorry, I am not
familiar with WDS enough to be more helpful.

The problem with all the virtio-win releases so far is that the
drivers don't declare the minimum Windows version they support. So
Windows (or in this case WDS?) is free to choose any of them, usually
going after the highest version which tends to be the Win8 variety.
This will also be fixed soon.

>> 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).

What does it say when you click "Show details"?

>> Thanks,
>>
>> Cam
>>
>>
>>> >
>>> > - Original Message -
>>> >> From: "Arman Khalatyan" 
>>> >> To: "Cam Mac" 
>>> >> Cc: "Tomas Jelinek" , "users" 
>>> >> 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" :
>>> >>
>>> >> > Hi Tomas,
>>> >> >
>>> >> > The install went ok, but Windows complains:
>>> >> >
>>> >> > "File: \windows\system32\drivers\vioscsi.sys
>>> >> > status: 0xc428
>>> >> > Windows cannot verify the digital signature for this file"
>>> >> >
>>> >> > Regards,
>>> >> >
>>> >> > Campbell
>>> >> >
>>> >> > On Tue, May 10, 2016 at 6:29 PM, Cam Mac  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
>>> >> >> 
>>> >> >> 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" 
>>> >> >>> > 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