Displaying 8 results from an estimated 8 matches for "viorngum".
Did you mean:
viorng
2016 Mar 04
2
[PATCH v2 0/2] v2v: Copy *.dll files since they can be part of the driver (RHBZ#1311373).
Since v1:
- Fix a bug in the calculation of lc_basename. By luck this doesn't
affect anything given the contents of the current ISO.
- Don't copy the WdfCoInstaller*.dll files.
Rich.
2016 Mar 04
2
[PATCH v3 0/2] v2v: Copy *.dll files since they can be part of the
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.
2016 Jun 04
1
[PATCH v2] v2v: copy all driver files into guest
...quot;, Some win2k12_64;
"viorng/2k12/amd64/viorng.inf", Some win2k12_64;
"viorng/2k12/amd64/viorng.pdb", Some win2k12_64;
"viorng/2k12/amd64/viorng.sys", Some win2k12_64;
- "viorng/2k12/amd64/viorngci.dll", None;
- "viorng/2k12/amd64/viorngum.dll", None;
- "viorng/2k12R2/amd64/WdfCoInstaller01011.dll", None;
+ "viorng/2k12/amd64/viorngci.dll", Some win2k12_64;
+ "viorng/2k12/amd64/viorngum.dll", Some win2k12_64;
+ "viorng/2k12R2/amd64/WdfCoInstaller01011.dll", Some win2k12r2_64;...
2015 Nov 17
0
[PATCH 3/3] v2v: windows: Use '*.inf' files to control how Windows drivers are installed.
...quot;, Some win2k12_64;
- "viorng/2k12/amd64/viorng.inf", Some win2k12_64;
- "viorng/2k12/amd64/viorng.pdb", Some win2k12_64;
- "viorng/2k12/amd64/viorng.sys", Some win2k12_64;
- "viorng/2k12/amd64/viorngci.dll", None;
- "viorng/2k12/amd64/viorngum.dll", None;
- "viorng/2k12R2/amd64/WdfCoInstaller01011.dll", None;
- "viorng/2k12R2/amd64/viorng.cat", Some win2k12r2_64;
- "viorng/2k12R2/amd64/viorng.inf", Some win2k12r2_64;
- "viorng/2k12R2/amd64/viorng.pdb", Some win2k12r2_64;
- "...
2015 Nov 17
8
[PATCH 0/3] v2v: windows: Use '*.inf' files to control how Windows drivers are installed.
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
2015 Nov 05
6
[PATCH 0/4] Provide better fake virtio-* test data for virt-v2v.
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
2017 Jun 27
3
[PATCH] libvirt: disallow non-local connections (RHBZ#1347830)
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
2017 Jul 07
4
[PATCH v6 0/3] gobject: Remove gtk-doc (RHBZ#1465665).
Hopefully this time ...