<div dir="ltr">Hi Ladi,<br><div class="gmail_extra"><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class=""><br>
<br>
</span>It is the same issue though, I have checked the timestamp in your BSOD<br>
screenshot. The driver running on the system at the time of crash was<br>
a build targeted at Win8 or newer. </blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<span class=""><br>
>> The other thing<br>
>> is that the crash happens after the install, upon first reboot.<br>
>> The<br>
>> contents of the Windows guest tools ISO<br>
>> are copied to the Windows Deployment server from where they are installed.<br>
<br>
</span>Can you feed only the Win7 subset of the ISO to WDS? Sorry, I am not<br>
familiar with WDS enough to be more helpful.<br>
<br>
The problem with all the virtio-win releases so far is that the<br>
drivers don't declare the minimum Windows version they support. So<br>
Windows (or in this case WDS?) is free to choose any of them, usually<br>
going after the highest version which tends to be the Win8 variety.<br>
This will also be fixed soon.<br></blockquote><div><br></div><div>We will try just the win 7 drivers that shipped with 3.6.3 rather than the <br></div><div>SHA-2 signed FC23 drivers and I'll get back to you. I have a question:</div><div>if I try to build a Win2k12 server via WDS, I assume I will have to add </div><div>the 2k12 drivers and then remove them again if I go to build a Win 7 VM</div><div>as Win 7 will presumably try to pick up the 2k12 driver? Or can they co-exist?</div><div>WDS has a build process whenever drivers are added (e.g., for KVM, VMWare</div><div>etc) for available drivers. Do you know when the fix will be available? </div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<span class=""><br>
>> When I try an alternative install using a Win 7 ISO, rather than PXE boot,<br>
>> it fails at a different point. This is using<br>
>> the oVirt Windows guest tools ISO that is in the 3.6.3 repos. When it<br>
>> comes to installing to disk, I change the CD<br>
>> to the guest tools ISO and browse to the win7 drivers<br>
>> (ovirt-tools-setup/drivers/virtio/viostor/w7/amd64/, which has<br>
>> the viostor drivers), but then the installer complains it cannot install<br>
>> on the disk, even though it can successfully<br>
>> create partitons on it (see attached screenshot).<br>
<br>
</span>What does it say when you click "Show details"?<br></blockquote><div><br></div><div>It just says: Windows is unable to install to the selected location. Error: 0x80300001 (see attached)</div><div><br></div><div>I've tried a variety of different ways to do this, by deleting all partitions, allowing Windows to create</div><div>them again, formatting them etc. I've tried both the viostor and vioscsi drivers with the same result.</div><div>No matter what partition I select (System or Primary) it always produces the same error.</div><div><br></div><div>Any ideas on when the newly signed drivers will be available?</div><div><br></div><div>Kind regards,</div><div><br></div><div>Cam</div><div><br></div></div></div></div>