From: Vadim Rozenfeld <vrozenfe@redhat.com>
To: Philipp Hahn <hahn@univention.de>
Cc: Tobias Birkefeld <Birkefeld@univention.de>,
Yan Vugenfirer <yvugenfi@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Cole Robinson <crobinso@redhat.com>
Subject: Re: [Qemu-devel] VirtIO windows driver: viostor.sys not post-installable
Date: Tue, 02 Jun 2015 08:30:17 +1000 [thread overview]
Message-ID: <1433197817.25870.27.camel@oscar> (raw)
In-Reply-To: <556C59CD.8020401@univention.de>
On Mon, 2015-06-01 at 15:10 +0200, Philipp Hahn wrote:
> Hello,
>
> On 31.05.2015 12:58, Vadim Rozenfeld wrote:
> > On Sun, 2015-05-31 at 11:26 +0300, Yan Vugenfirer wrote:
> >>> On May 29, 2015, at 5:43 PM, Philipp Hahn <hahn@univention.de>
> >>> wrote:
> ...
> >>> we tried to migrate some Windows 2008 and 2012 VMs from Xen to KVM,
> >>> but
> >>> installing the VirtIO viostor.sys driver fails, because the
> >>> signature of
> >>> the driver doesn't seem to match what's stored in the
> >>> corresponding .cat
> >>> file.
> ...
> >> Can you send the error message you are getting from Windows? If
> >> possible attach setupapi.log as well (search your system
> >> for setupapi.*, the location might be different for different OS
> >> versions).
>
> I attached them to <https://bugzilla.redhat.com/show_bug.cgi?id=1226928>
>
> > Do you use the same installation media for v2v and a fresh install, or
> > vfd for a fresh install and iso for v2v conversion?
>
> If the drivers are installed during the initial setup, both ISO and VFD
> work - after navigating into the right sub directory and enabling "show
> not matching drivers". No BSOD.
>
> Using the same ISO after doing the install using the emulated IDE, the
> drivers are rejected with:
>
> > Processing inf : vioscsi.inf
> > Adding the driver package failed : The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.
> >
> > Processing inf : viostor.inf
> > Adding the driver package failed : The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.
>
>
> >>> Are there some Linux tools to work with the .cat files and
> >>> signatures to make sure they match?
>
> Answering my own question: .crt files are DER encoded. "dumpasn1" shows
> them to contain PKCS#7 data.
>
> >> Vadim and I monitor qemu-devel, you can also open bug in
> >> bugzilla.redhat.com for virtio-win component or report an issue
> >> here: https://github.com/YanVugenfirer/kvm-guest-drivers-windows/issues
>
> I filed <https://bugzilla.redhat.com/show_bug.cgi?id=1226928>. If
> anything is still missing, just ask.
>
Thanks,
Vadim.
> Thanks for the fast help and for any more help in advance
> Philipp Hahn
prev parent reply other threads:[~2015-06-01 22:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 14:43 [Qemu-devel] VirtIO windows driver: viostor.sys not post-installable Philipp Hahn
2015-05-29 17:41 ` Cole Robinson
2015-05-31 8:26 ` Yan Vugenfirer
2015-05-31 10:58 ` Vadim Rozenfeld
2015-06-01 13:10 ` Philipp Hahn
2015-06-01 22:30 ` Vadim Rozenfeld [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1433197817.25870.27.camel@oscar \
--to=vrozenfe@redhat.com \
--cc=Birkefeld@univention.de \
--cc=crobinso@redhat.com \
--cc=hahn@univention.de \
--cc=qemu-devel@nongnu.org \
--cc=yvugenfi@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).