From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39506) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YyOI0-0001q5-EX for qemu-devel@nongnu.org; Fri, 29 May 2015 13:41:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YyOHx-0007nN-8c for qemu-devel@nongnu.org; Fri, 29 May 2015 13:41:48 -0400 Received: from mx1.redhat.com ([209.132.183.28]:35197) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YyOHx-0007lr-22 for qemu-devel@nongnu.org; Fri, 29 May 2015 13:41:45 -0400 Message-ID: <5568A4D5.9050004@redhat.com> Date: Fri, 29 May 2015 13:41:41 -0400 From: Cole Robinson MIME-Version: 1.0 References: <55687B16.8070901@univention.de> In-Reply-To: <55687B16.8070901@univention.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] VirtIO windows driver: viostor.sys not post-installable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Philipp Hahn , Yan Vugenfirer , qemu-devel@nongnu.org Cc: Tobias Birkefeld On 05/29/2015 10:43 AM, Philipp Hahn 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. > > On the other hand installing the drivers during a fresh install from the > beginning never had any problems. > > > We use > > 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? > > 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? > There isn't a specific mailing. For technical issues the closest this is qemu-devel or kvm list, but this seems more like a packaging/build system issue. I'd suggest filing a bug at bugzilla.redhat.com, product=Virtualization Tools, component=virtio-win, and dump all the info you posted above. Vadim is pretty quick to respond in my experience. Thanks, Cole > > 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. >