search for: viostor

I think one - maybe final? - problem. How can I tell the difference between drivers for "client" versions of Windows (eg. Windows 7) and server versions of Windows (eg. Windows 2008 Server)? It seems in many or most cases the drivers are identical, eg: $ md5sum viostor/2k12/amd64/* viostor/w8/amd64/* bbe250c13bf891fd7292ccab9908a63a viostor/2k12/amd64/viostor.cat c2fdfc6a47fdc9dd25242441cdf1a68e viostor/2k12/amd64/viostor.inf 5ca2cadca2214b90196755dab06676f4 viostor/2k12/amd64/viostor.pdb 80c5ea60a69f37e965cb277383abd067 viostor/2k12/amd64/viostor.sys bbe250c...

On Tue, Nov 17, 2015 at 08:49:54PM +0000, Richard W.M. Jones wrote: > There was a copy and paste error. It should have read: > > $ md5sum viostor/2k8/amd64/* viostor/w7/amd64/* > d1132fbd27c98f25ea71a6eb4037b2f8 viostor/2k8/amd64/viostor.cat > defccbe48aca1cd97fee4d7b16053b72 viostor/2k8/amd64/viostor.inf > 6da6120368c097806e4ac7fc6b940810 viostor/2k8/amd64/viostor.pdb > 63b05edfb75d9dc60e82ab3c0bfee701 viostor/2k8/amd64/vios...

...nk one - maybe final? - problem. How can I tell the difference > between drivers for "client" versions of Windows (eg. Windows 7) > and server versions of Windows (eg. Windows 2008 Server)? > > It seems in many or most cases the drivers are identical, eg: > > $ md5sum viostor/2k12/amd64/* viostor/w8/amd64/* > bbe250c13bf891fd7292ccab9908a63a viostor/2k12/amd64/viostor.cat > c2fdfc6a47fdc9dd25242441cdf1a68e viostor/2k12/amd64/viostor.inf > 5ca2cadca2214b90196755dab06676f4 viostor/2k12/amd64/viostor.pdb > 80c5ea60a69f37e965cb277383abd067 viostor/2k12/amd64...

...m. How can I tell the difference > > between drivers for "client" versions of Windows (eg. Windows 7) > > and server versions of Windows (eg. Windows 2008 Server)? > > > > It seems in many or most cases the drivers are identical, eg: > > > > $ md5sum viostor/2k12/amd64/* viostor/w8/amd64/* > > bbe250c13bf891fd7292ccab9908a63a viostor/2k12/amd64/viostor.cat > > c2fdfc6a47fdc9dd25242441cdf1a68e viostor/2k12/amd64/viostor.inf > > 5ca2cadca2214b90196755dab06676f4 viostor/2k12/amd64/viostor.pdb > > 80c5ea60a69f37e965cb277383abd067...

.../xp/x86/WdfCoInstaller01009.dll", None; - "vioserial/xp/x86/vioser.cat", Some winxp_32; - "vioserial/xp/x86/vioser.inf", Some winxp_32; - "vioserial/xp/x86/vioser.pdb", Some winxp_32; - "vioserial/xp/x86/vioser.sys", Some winxp_32; - "viostor/2k12/amd64/viostor.cat", Some win2k12_64; - "viostor/2k12/amd64/viostor.inf", Some win2k12_64; - "viostor/2k12/amd64/viostor.pdb", Some win2k12_64; - "viostor/2k12/amd64/viostor.sys", Some win2k12_64; - "viostor/2k12R2/amd64/viostor.cat", Som...

...nce > > > between drivers for "client" versions of Windows (eg. Windows 7) > > > and server versions of Windows (eg. Windows 2008 Server)? > > > > > > It seems in many or most cases the drivers are identical, eg: > > > > > > $ md5sum viostor/2k12/amd64/* viostor/w8/amd64/* > > > bbe250c13bf891fd7292ccab9908a63a viostor/2k12/amd64/viostor.cat > > > c2fdfc6a47fdc9dd25242441cdf1a68e viostor/2k12/amd64/viostor.inf > > > 5ca2cadca2214b90196755dab06676f4 viostor/2k12/amd64/viostor.pdb > > > 80c5ea60a69f...

https://github.com/rwmjones/libguestfs/tree/rewrite-virtio-copy-drivers Instead of trying to split and parse elements from virtio-win paths, use the '*.inf' files supplied with the drivers to control how Windows drivers are installed. The following emails best explain how this works: https://www.redhat.com/archives/libguestfs/2015-October/msg00352.html

Patch 1 moves the v2v/fake-virtio-win and v2v/fake-virt-tools directories to the recently created test-data/ hierarchy. This is just refactoring with no functional change at all. Patches 2-4 then extend the available (fake) virtio-win drivers: - Patch 2 adds all of the drivers from the virtio-win RPM. - Patch 3 adds all of the drivers from the virtio-win ISO (which are different from the

There was a copy and paste error. It should have read: $ md5sum viostor/2k8/amd64/* viostor/w7/amd64/* d1132fbd27c98f25ea71a6eb4037b2f8 viostor/2k8/amd64/viostor.cat defccbe48aca1cd97fee4d7b16053b72 viostor/2k8/amd64/viostor.inf 6da6120368c097806e4ac7fc6b940810 viostor/2k8/amd64/viostor.pdb 63b05edfb75d9dc60e82ab3c0bfee701 viostor/2k8/amd64/viostor.sys af0cca02244f...

If a Windows boot fails and the user boots the last known good configuration, ControlSet001 will be marked as failed and no longer used. However, virt-v2v would only install viostor to ControlSet001, meaning it will fail to boot this guest after conversion. This patch looks up the current controlset and always installs registry keys to the correct one. Fixes RHBZ#644254 --- lib/Sys/VirtV2V/Converter/Windows.pm | 27 ++++++++++++++++----------- 1 files changed, 16 insertio...

if it works thank god for notepad2 (If it's not then be patience, I am just a windows user). Amos. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0002-use-single-registry-change-for-all-supported-windows.patch Type: application/octet-stream Size: 10635 bytes Desc: not available URL:

On Thu, Oct 29, 2015 at 11:05:42AM +1100, Vadim Rozenfeld wrote: > On Wed, 2015-10-28 at 14:53 +0300, Roman Kagan wrote: > > 1) tell which devices can be configured > Not sure that I fully understated your question. but if you are going to > create some sort of off-line automatic virtio-win drivers update > utility, then it shouldn't be too complicated. Firs of all you will

...change- > for-all-supported-windows.patch > > > From: unknown <Amos at .(none)> > > In ~/.gitconfig set: > > [user] > name = Your Name > email = your at email.example.com > > > [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\viostor\Enum] > > - > "0"="PCI\\\\VEN_1AF4&DEV_1001&SUBSYS_00021AF4&REV_00\\\\3&13c0b0c5&0&2 > 0 > " > > +"0"="PCI\\VEN_1AF4&DEV_1001&SUBSYS_00021AF4&REV_00\\3&13c0b0c5&0&20" > > This change...

...ows_virtio.ml | 311 ++++++++++++++++++++++++++++---------------------- 1 file changed, 176 insertions(+), 135 deletions(-) diff --git a/v2v/windows_virtio.ml b/v2v/windows_virtio.ml index 14ffc51..8a0b529 100644 --- a/v2v/windows_virtio.ml +++ b/v2v/windows_virtio.ml @@ -146,48 +146,50 @@ and add_viostor_to_critical_device_database g root current_cs = * NB: All these edits are in the HKLM\SYSTEM hive. No other * hive may be modified here. *) + let driver = "viostor.sys" in + let driver_name = Filename.chop_extension driver in let regedits = [ [ current_cs; "C...

[Partly using the mailing list as a backup again ...] This commit changes virt-v2v to make registry changes to all ControlSets, not just the CurrentControlSet. Not sure what difference if any this would make. Rich.

...g virt-v2v under CentOS 7, I use the new libguestfs-1.27.48-1.1, and when I try to import my Windows 2008 (running perfectly using virt-manager) in my cloud oVirt, I encounter this issue : ........ libguestfs: trace: mkdir_p = 0 libguestfs: trace: case_sensitive_path "/Windows/system32/drivers/viostor.sys" libguestfs: trace: case_sensitive_path = "/Windows/System32/drivers/viostor.sys" libguestfs: trace: cp "/usr/share/virtio-win/drivers/amd64/Win2008/viostor.sys" "/Windows/System32/drivers/viostor.sys" libguestfs: trace: cp = -1 (error) libguestfs: trace: hive...

This patch allows paths in virt-v2v.conf to be either relative or absolute. If relative, they are relative to software-root. This allows virt-v2v.conf to use files provided by packages independent of virt-v2v. --- lib/Sys/VirtV2V/Config.pm | 10 ++++++---- 1 files changed, 6 insertions(+), 4 deletions(-) diff --git a/lib/Sys/VirtV2V/Config.pm b/lib/Sys/VirtV2V/Config.pm index f703152..121e774

...ead1 DESCRIPTION + +Sys::VirtV2V::Converter::Windows does the "pre-conversion" steps +required to get a Windows guest to boot on KVM. Unlike the associated +L<Sys::VirtV2V::Converter::Linux(3)> module, this doesn't do a full +conversion of Windows. Instead it just installs the viostor (Windows +virtio block) driver, so that the Windows guest will be able to boot +on the target. A "RunOnce" script is also added to the VM which does +all the rest of the conversion the first time the Windows VM is booted +on KVM. + +Note when reading the code: this module just "dire...

...nf | 6 ------ 1 files changed, 0 insertions(+), 6 deletions(-) diff --git a/v2v/virt-v2v.conf b/v2v/virt-v2v.conf index 9fbb1cc..c3dfd30 100644 --- a/v2v/virt-v2v.conf +++ b/v2v/virt-v2v.conf @@ -153,12 +153,6 @@ <app os='windows' major='6' arch='x86_64' name='viostor'> <path>windows/2008/x86_64/viostor.sys</path> </app> - <app os='windows' major='6' minor='1' arch='i386' name='viostor'> - <path>windows/7/i386/viostor.sys</path> - </app> - <app os='windo...

The way we patch the Windows registry in order to allow it to boot off a virtio-blk drive was initially conceived by comparing the state with virtio-blk driver properly installed, to that without. However, we don't want to replicate the Windows PnP system; rather we need to apply just enough edits to make the system boot, and then let the Windows PnP manager figure out the rest. This series