From: Vadim Rozenfeld <vrozenfe@redhat.com>
To: Yan Vugenfirer <yvugenfi@redhat.com>
Cc: Tobias Birkefeld <Birkefeld@univention.de>,
Cole Robinson <crobinso@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Philipp Hahn <hahn@univention.de>
Subject: Re: [Qemu-devel] VirtIO windows driver: viostor.sys not post-installable
Date: Sun, 31 May 2015 20:58:45 +1000 [thread overview]
Message-ID: <1433069925.572.26.camel@oscar> (raw)
In-Reply-To: <B29987B3-1DA1-4A3B-8E27-B98E01CB4DA6@redhat.com>
On Sun, 2015-05-31 at 11:26 +0300, Yan Vugenfirer wrote:
> Adding Vadim to the thread.
>
> > On May 29, 2015, at 5:43 PM, Philipp Hahn <hahn@univention.de>
> > wrote:
> >
> > Hello,
> >
> > 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).
>
> > On the other hand installing the drivers during a fresh install from
> > the
> > beginning never had any problems.
Do you use the same installation media for v2v and a fresh install, or
vfd for a fresh install and iso for v2v conversion?
Thanks,
Vadim.
> >
> >
> > We use
> > <https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.104-1/virtio-win-0.1.104.iso>
> > but also tried "virtio-win-0.1.103.iso" and "virtio-win-0.1-81.iso".
> >
> > Running the following command on 0.1.104 prints (among others) the
> > following sha1hash:
> > > "C:\Program Files (x86)\Windows Kits\8.1\bin\x86
> > > \signtool.exe" /verify
> > /v /kp E:\NetKVM\2k12\amd64\netkvm.sys
> > ...
> > > Hash of file (sha1): 135E3AA23217610AEE8046F68550B0BA86F4EAE6
> >
> > > "C:\Program Files (x86)\Windows Kits\8.1\bin\x86
> > > \signtool.exe" /verify
> > /v /kp E:\viostor\2k12\amd64\viostor.sys
> > ...
> > > Hash of file (sha1): EF11F5E539EEE0A9DB6DF3710A0DAA35066C5607
> >
> > Looking into the corresponding .cat "Security Catalog File"
> > - netkvm.cat contains the above given hash for netkvm.sys,
> > - viostor.cat contains 55FC4DA2EE96ECC3FD4865680436DCDA6B8C6BDD
> > instead!
> >
> > Running "sha1sum" on Linux print some completely different hashes,
> > so I
> > don't know what the Microsoft tool actually hash:
> >
> > > #
> > > sha1sum /cdrom/NetKVM/2k12/amd64/netkvm.sys /cdrom/viostor/2k12/amd64/viostor.sys
> > > 1aa91c8e1d7680457d92c1875810a79f68af536d
> > > /cdrom/NetKVM/2k12/amd64/netkvm.sys
> > > f39bc2b561091addfcac30e370227c91700d2698
> > > /cdrom/viostor/2k12/amd64/viostor.sys
> >
> > Is this a known issue?
> >
>
>
> There was some mismatch reported between Windows and sha1sum on
> Linux.
>
> >
> > Are there some (working) alternatives?
> >
> > Are there some Linux tools to work with the .cat files and
> > signatures to
> > make sure they match?
> >
> > Is there some better mailing list for VirtIO Windows driver issues?
> >
>
>
> 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
>
>
> >
> >
> > Some more background for our migration procedure:
> >
> > - The VM was installed some years are on Xen.
> > - The GPLPV drivers were added afterwards.
> > - For the migration the GPLPV drivers were disabled and then
> > removed.
> > - A 2nd VirtIO hard-disk was added in KVM to trigger Windows to
> > request
> > the virstor driver.
> >
> > If you need any more data, just ask.
> >
> > Thanks in advance
> > Philipp Hahn
> >
> > PS: data was copied by hand from Windows, so it might contains
> > copy-paste-errors.
> > --
> > Philipp Hahn
> > Open Source Software Engineer
> >
> > Univention GmbH
> > be open.
> > Mary-Somerville-Str. 1
> > D-28359 Bremen
> > Tel.: +49 421 22232-0
> > Fax : +49 421 22232-99
> > hahn@univention.de
> >
> > http://www.univention.de/
> > Geschäftsführer: Peter H. Ganten
> > HRB 20755 Amtsgericht Bremen
> > Steuer-Nr.: 71-597-02876
> >
>
>
next prev parent reply other threads:[~2015-05-31 10:58 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 [this message]
2015-06-01 13:10 ` Philipp Hahn
2015-06-01 22:30 ` Vadim Rozenfeld
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=1433069925.572.26.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.