[Avocado-devel] virtio_blk + Win8 fails

[Lucas Meneghel Rodrigues]

Oh, I forgot to mention that the upstream drivers are unsigned, and some
versions of Windows will refuse to use the unsigned versions. Inside RH
there are isos with signed drivers, but I'll let how to find those as an
exercise to the reader (anyway it's a really bad practice to be sharing
internal links on a public mailing list).

On Thu, Sep 24, 2015 at 10:30 AM Lucas Meneghel Rodrigues <lookkas at gmail.com>
wrote:

>
> virtio-win.iso might be outdated, or the config files for Win8.x86_64
> might be outdated. I haven't tried and I won't be able to try in the near
> future, so I'd defer your question to our friends from the KVM QE team in
> Beijing. I'm copying Suqin, maybe she can forward this to someone who can
> help.
>
> Keep in mind that having default upstream config files that work across
> multiple hosts (qemu versions) is challenging. Besides, the virtio-win.iso
> file that we use for upstream testing might be outdated and someone needs
> to take the time to update and test with upstream config files (coming back
> to the issue that the person might be testing on a RHEL 6 machine and your
> Fedora 23 machine QEMU behaves differently).
>
> I'm going to explain the basic idea behind installing windows with
> avocado-vt using virtio drivers:
>
> 1) The windows VM needs to be able to 'see' the virtio-win.iso.
> 2) The location of the drive has to be provided through the answer file in
> the form of a drive letter, and a path inside this drive letter.
> 3) Sometimes, the order of drives might change inside the vm and this
> makes the install program unable to find the drivers
> 4) Additionally, the virtio-win.iso layout might change from version to
> version and then all of a sudden the install program is also unable to find
> the drivers.
>
> Ficticious Example: The config files provide D:/virtio-win/win8/x86_64,
> but in the actual VM the path is E:/virtio-win/win8/amd64. This will make
> the install to not proceed at all.
>
> So it's likely that you did things right, yet your particular combination
> of host and Windows version and virtio-win.iso layout might not be working
> out as it worked for the person who first added windows 8 config files.
>
> On Thu, Sep 24, 2015 at 8:58 AM Andrei Stepanov <astepano at redhat.com>
> wrote:
>
>> Hello.
>>
>> I am just curious, does anybody can install Windows systems (Win8.x86_64
>> especially) using
>>
>> virtio_blk (drive_format=virtio) ??
>>
>> It fails for me at DiskConfiguration step.
>>
>> ide (drive_format = ide) works fine.
>>
>> I have attached cds:
>>
>> virtio-win.iso
>> winutils.iso
>> _______________________________________________
>> Avocado-devel mailing list
>> Avocado-devel at redhat.com
>> https://www.redhat.com/mailman/listinfo/avocado-devel
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/avocado-devel/attachments/20150924/8996cfab/attachment.htm>