search for: blnsvr

...2_64; "Balloon/2k12/amd64/balloon.cat", Some win2k12_64; "Balloon/2k12/amd64/balloon.inf", Some win2k12_64; "Balloon/2k12/amd64/balloon.pdb", Some win2k12_64; "Balloon/2k12/amd64/balloon.sys", Some win2k12_64; - "Balloon/2k12/amd64/blnsvr.exe", None; + "Balloon/2k12/amd64/blnsvr.exe", Some win2k12_64; "Balloon/2k12/amd64/blnsvr.pdb", Some win2k12_64; - "Balloon/2k12R2/amd64/WdfCoInstaller01011.dll", None; + "Balloon/2k12R2/amd64/WdfCoInstaller01011.dll", Some win2k12r2_64;...

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.

...b9def49d086d960349d Balloon/2k12/amd64/balloon.cat 0325b7e0552e1567292eb6c1068fee18 Balloon/2k12/amd64/balloon.inf ac2116f04fd678d0e264f34e3bf90d1e Balloon/2k12/amd64/balloon.pdb c975501dd5b43ade3717722b81acbc1f Balloon/2k12/amd64/balloon.sys 56f63afdd992a5395a4d8da6a52e559e Balloon/2k12/amd64/blnsvr.exe c539f2056fb196da377d14180fda195c Balloon/2k12/amd64/blnsvr.pdb d10864c1730172780c2d4be633b9220a Balloon/2k12/amd64/WdfCoInstaller01011.dll d4104f08e674ab9def49d086d960349d Balloon/w8/amd64/balloon.cat 0325b7e0552e1567292eb6c1068fee18 Balloon/w8/amd64/balloon.inf ac2116f04fd678d0e264f34e3bf9...

...None; - "Balloon/2k12/amd64/balloon.cat", Some win2k12_64; - "Balloon/2k12/amd64/balloon.inf", Some win2k12_64; - "Balloon/2k12/amd64/balloon.pdb", Some win2k12_64; - "Balloon/2k12/amd64/balloon.sys", Some win2k12_64; - "Balloon/2k12/amd64/blnsvr.exe", None; - "Balloon/2k12/amd64/blnsvr.pdb", Some win2k12_64; - "Balloon/2k12R2/amd64/WdfCoInstaller01011.dll", None; - "Balloon/2k12R2/amd64/balloon.cat", Some win2k12r2_64; - "Balloon/2k12R2/amd64/balloon.inf", Some win2k12r2_64; - &qu...

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

...Balloon/2k12/amd64/balloon.cat > 0325b7e0552e1567292eb6c1068fee18 Balloon/2k12/amd64/balloon.inf > ac2116f04fd678d0e264f34e3bf90d1e Balloon/2k12/amd64/balloon.pdb > c975501dd5b43ade3717722b81acbc1f Balloon/2k12/amd64/balloon.sys > 56f63afdd992a5395a4d8da6a52e559e Balloon/2k12/amd64/blnsvr.exe > c539f2056fb196da377d14180fda195c Balloon/2k12/amd64/blnsvr.pdb > d10864c1730172780c2d4be633b9220a Balloon/2k12/amd64/WdfCoInstaller01011.dll > d4104f08e674ab9def49d086d960349d Balloon/w8/amd64/balloon.cat > 0325b7e0552e1567292eb6c1068fee18 Balloon/w8/amd64/balloon.inf > ac2...

...balloon.cat > > 0325b7e0552e1567292eb6c1068fee18 Balloon/2k12/amd64/balloon.inf > > ac2116f04fd678d0e264f34e3bf90d1e Balloon/2k12/amd64/balloon.pdb > > c975501dd5b43ade3717722b81acbc1f Balloon/2k12/amd64/balloon.sys > > 56f63afdd992a5395a4d8da6a52e559e Balloon/2k12/amd64/blnsvr.exe > > c539f2056fb196da377d14180fda195c Balloon/2k12/amd64/blnsvr.pdb > > d10864c1730172780c2d4be633b9220a > > Balloon/2k12/amd64/WdfCoInstaller01011.dll > > d4104f08e674ab9def49d086d960349d Balloon/w8/amd64/balloon.cat > > 0325b7e0552e1567292eb6c1068fee18 Balloon/...

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

...; > 0325b7e0552e1567292eb6c1068fee18 Balloon/2k12/amd64/balloon.inf > > > ac2116f04fd678d0e264f34e3bf90d1e Balloon/2k12/amd64/balloon.pdb > > > c975501dd5b43ade3717722b81acbc1f Balloon/2k12/amd64/balloon.sys > > > 56f63afdd992a5395a4d8da6a52e559e Balloon/2k12/amd64/blnsvr.exe > > > c539f2056fb196da377d14180fda195c Balloon/2k12/amd64/blnsvr.pdb > > > d10864c1730172780c2d4be633b9220a > > > Balloon/2k12/amd64/WdfCoInstaller01011.dll > > > d4104f08e674ab9def49d086d960349d Balloon/w8/amd64/balloon.cat > > > 0325b7e0552e15672...

On Tue, Jun 23, 2015 at 09:18:01AM +0300, Shahar Havivi wrote: > On 22.06.15 15:33, Richard W.M. Jones wrote: > > This makes several changes to the handling of virtio-win drivers: > > > > The VIRTIO_WIN_DIR environment variable has been renamed > > VIRTIO_WIN (but you can still use the old name). > > > > You can point the VIRTIO_WIN either at a RHEL

...we don't know what to do: - the netkvm driver directory on virtio-win.iso contains netkvmco.dll (I'm assuming it's coinstaller dll). However, netkvm.inf doesn't mention it, and the driver installs just fine without it. - the balloon driver directory on virtio-win.iso contains blnsvr.exe (and .pdb) which is apparently a usermode service to report memory stats to host via balloon virtio queue. However nothing seems to automatically trigger installation of that service. Thanks, Roman.

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

...iltering of files by suffix is a bad idea in general: the packager of the drivers should be free to ship any files he wants, including docs and text notes. It's only the path that should match against the guest OS flavor and that really matters. E.g. the balloon driver directory also contains blnsvr.exe (and its .pdb) which is a usermode service responsible for feeding the balloon device with the memory stats; it's not a part of the driver per se but it's currently bundled with it. (I'm yet to figure out who's responsible for installing it). > It also causes the tests to f...

...ix is > a bad idea in general: the packager of the drivers should be free to > ship any files he wants, including docs and text notes. It's only the > path that should match against the guest OS flavor and that really > matters. E.g. the balloon driver directory also contains > blnsvr.exe (and its .pdb) which is a usermode service responsible for > feeding the balloon device with the memory stats; it's not a part of the > driver per se but it's currently bundled with it. (I'm yet to figure > out who's responsible for installing it). > > > It a...

On Thu, Oct 29, 2015 at 11:05:42AM +1100, Vadim Rozenfeld 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. Roman is talking about what virt-v2v already does. This is good information:

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. Correct that, and update the tests accordingly. Signed-off-by: Roman Kagan <rkagan@virtuozzo.com> --- v2v/fake-virtio-win/drivers/i386/Win7/qxldd.dll | 1 + v2v/test-v2v-in-place.sh | 1 +

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 ...