search for: vioseri

v2 -> v3 - Don't make a special case for WdfCoInstaller* files. There is a difference of opinion about whether copying these is necessary, but it seems like it is not harmful. Rich.

...amd64/vioscsi.pdb", Some win2k12_64; @@ -464,72 +464,72 @@ let test_virtio_iso_path_matches_guest_os ctx = "vioscsi/w8/x86/vioscsi.inf", Some win8_32; "vioscsi/w8/x86/vioscsi.pdb", Some win8_32; "vioscsi/w8/x86/vioscsi.sys", Some win8_32; - "vioserial/2k12/amd64/WdfCoInstaller01011.dll", None; + "vioserial/2k12/amd64/WdfCoInstaller01011.dll", Some win2k12_64; "vioserial/2k12/amd64/vioser.cat", Some win2k12_64; "vioserial/2k12/amd64/vioser.inf", Some win2k12_64; "vioserial/2k12/amd64/vio...

...ot;vioscsi/w8/amd64/vioscsi.sys", Some win8_64; - "vioscsi/w8/x86/vioscsi.cat", Some win8_32; - "vioscsi/w8/x86/vioscsi.inf", Some win8_32; - "vioscsi/w8/x86/vioscsi.pdb", Some win8_32; - "vioscsi/w8/x86/vioscsi.sys", Some win8_32; - "vioserial/2k12/amd64/WdfCoInstaller01011.dll", None; - "vioserial/2k12/amd64/vioser.cat", Some win2k12_64; - "vioserial/2k12/amd64/vioser.inf", Some win2k12_64; - "vioserial/2k12/amd64/vioser.pdb", Some win2k12_64; - "vioserial/2k12/amd64/vioser.sys"...

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

...ackaged in the rhel virtio-win rpm, I found out that its contents differed significantly from what was packaged in that very same rpm as a driver directory hierarchy. Namely, - there are no qxl drivers on the iso, but they are present in the rpm - there are no balloon, qemupciserial, viorng, vioserial in the rpm, but they are present on the iso - qemupciserial is an inf-only 'driver' which matches all windows versions; it's just one copy at the sub-toplevel directory, so it won't pass the virtio_iso_path_matches_guest_os() criteria - there are a lot of duplica...

...for kernel 6.2 Win8/WS2012 and technically should be compatible with > 6.3). So, we are looking for DriverVer which looks like this one: > DriverVer=XX/YY/ZZZZ,62.AA.BBB.CCCCC > > Still no luck - decrease the target OS version to 61 and repeat. > > For WDF drivers like balloon, vioserial, and rng you can go as far as > you can trying to find an appropriate driver. > > For miniport drivers like netkvm ( Yan, please confirm ), viostor and > vioscsi I wouldn't go too far. For example drivers designed to fork in > specific stacks at kernel version 5.1 (WinXP) can...

Hi, When adding a channel device on a Win2008R2 Guest, I got this new thing within registry : Key Name: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\{6FDE7547-1B65-48ae-B628-80BE62016026}\VIOSerialPort\4&7e8053e&0&02 Class Name: <NO CLASS> Last Write Time: 9/16/2015 - 4:09 PM Value 0 Name: DeviceDesc Type: REG_SZ Data: vport0p2 Value 1 Name: Capabilities Type: REG_DWORD Data: 0xe6 Valu...

...ible with > > > 6.3). So, we are looking for DriverVer which looks like this one: > > > DriverVer=XX/YY/ZZZZ,62.AA.BBB.CCCCC > > > > > > Still no luck - decrease the target OS version to 61 and repeat. > > > > > > For WDF drivers like balloon, vioserial, and rng you can go as far as > > > you can trying to find an appropriate driver. > > > > > > For miniport drivers like netkvm ( Yan, please confirm ), viostor and > > > vioscsi I wouldn't go too far. For example drivers designed to fork in > > >...

...t; > > packaged in that very same rpm as a driver directory hierarchy. > > > > > > Namely, > > > > > > - there are no qxl drivers on the iso, but they are present in the rpm > > > > > > - there are no balloon, qemupciserial, viorng, vioserial in the rpm, > > > but they are present on the iso > > > > > > - qemupciserial is an inf-only 'driver' which matches all windows > > > versions; it's just one copy at the sub-toplevel directory, so it > > > won't pass the...

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

...means that a driver was build for kernel 6.2 Win8/WS2012 and technically should be compatible with 6.3). So, we are looking for DriverVer which looks like this one: DriverVer=XX/YY/ZZZZ,62.AA.BBB.CCCCC Still no luck - decrease the target OS version to 61 and repeat. For WDF drivers like balloon, vioserial, and rng you can go as far as you can trying to find an appropriate driver. For miniport drivers like netkvm ( Yan, please confirm ), viostor and vioscsi I wouldn't go too far. For example drivers designed to fork in specific stacks at kernel version 5.1 (WinXP) can refuse working with kern...

...d technically should be compatible with > > 6.3). So, we are looking for DriverVer which looks like this one: > > DriverVer=XX/YY/ZZZZ,62.AA.BBB.CCCCC > > > > Still no luck - decrease the target OS version to 61 and repeat. > > > > For WDF drivers like balloon, vioserial, and rng you can go as far as > > you can trying to find an appropriate driver. > > > > For miniport drivers like netkvm ( Yan, please confirm ), viostor and > > vioscsi I wouldn't go too far. For example drivers designed to fork in > > specific stacks at kerne...

If the connection is not local, paths of disks will refer to the remote host, which were mistakenly handled as local paths (in the best case failing to open a non-existing disk, and in the worst case opening a different disk!). In case the disks are remote resources like ssh or ceph, nothing guarantees that the hostname can be reached from the local machine, or even that it is actually the same on

Hopefully this time ...

On Tue, Oct 27, 2015 at 09:12:41AM +0000, Richard W.M. Jones wrote: > On Mon, Oct 26, 2015 at 09:00:03PM +0300, Roman Kagan wrote: > > Windows QXL drivers include also qxldd.dll which used to get filtered > > out and not copied over into the guest. As a result QXL driver failed > > to install due to a missing file. > > (* Skip files without specific extensions. *)