search for: driverv

...ndows NT\CurrentVersion". Let's say it >>> 6.3, which means that it is Win8.1 or WS2012R2, parsing "BuildLabEx" >>> string from the same hive will give you information about the platform >>> bitness. Next you need to go through inf files, and find "DriverVer" >>> string, like this one . taken from from vioscsi.inf >>> >>> DriverVer=08/01/2015,62.72.104.10800 >>> >>> This string contains build time and version stamps. The version stamp >>> looks as follow "62.72.104.10800" >>...

...LM\SOFTWARE\Microsoft\Windows NT\CurrentVersion". Let's say it > 6.3, which means that it is Win8.1 or WS2012R2, parsing "BuildLabEx" > string from the same hive will give you information about the platform > bitness. Next you need to go through inf files, and find "DriverVer" > string, like this one . taken from from vioscsi.inf > > DriverVer=08/01/2015,62.72.104.10800 > > This string contains build time and version stamps. The version stamp > looks as follow "62.72.104.10800" > where 62 means a target Windows kernel version mult...

...Let's say it > > >>> 6.3, which means that it is Win8.1 or WS2012R2, parsing "BuildLabEx" > > >>> string from the same hive will give you information about the platform > > >>> bitness. Next you need to go through inf files, and find "DriverVer" > > >>> string, like this one . taken from from vioscsi.inf > > >>> > > >>> DriverVer=08/01/2015,62.72.104.10800 > > >>> > > >>> This string contains build time and version stamps. The version stamp > > >&...

...rosoft\Windows NT\CurrentVersion". Let's say it > > 6.3, which means that it is Win8.1 or WS2012R2, parsing "BuildLabEx" > > string from the same hive will give you information about the platform > > bitness. Next you need to go through inf files, and find "DriverVer" > > string, like this one . taken from from vioscsi.inf > > > > DriverVer=08/01/2015,62.72.104.10800 > > > > This string contains build time and version stamps. The version stamp > > looks as follow "62.72.104.10800" > > where 62 means a...

...tVersion". Let's say it > >>> 6.3, which means that it is Win8.1 or WS2012R2, parsing "BuildLabEx" > >>> string from the same hive will give you information about the platform > >>> bitness. Next you need to go through inf files, and find "DriverVer" > >>> string, like this one . taken from from vioscsi.inf > >>> > >>> DriverVer=08/01/2015,62.72.104.10800 > >>> > >>> This string contains build time and version stamps. The version stamp > >>> looks as follow "...

On Wed, Oct 28, 2015 at 12:10:19PM +1100, Vadim Rozenfeld wrote: > > > > To sum up, the packaging and naming policy of the virtio-win rpm and the > > > > virtio-win iso therein are different and neither is clear. Hardcoding > > > > the policy in v2v without actually knowing it appears risky at best. > > It's due to historical reasons mostly. The best

...LM\SOFTWARE\Microsoft\Windows NT\CurrentVersion". Let's say it > 6.3, which means that it is Win8.1 or WS2012R2, parsing "BuildLabEx" > string from the same hive will give you information about the platform > bitness. Next you need to go through inf files, and find "DriverVer" > string, like this one . taken from from vioscsi.inf > > DriverVer=08/01/2015,62.72.104.10800 > > This string contains build time and version stamps. The version stamp > looks as follow "62.72.104.10800" > where 62 means a target Windows kernel version mult...

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

...Microsoft\Windows NT\CurrentVersion". Let's say it >> 6.3, which means that it is Win8.1 or WS2012R2, parsing "BuildLabEx" >> string from the same hive will give you information about the platform >> bitness. Next you need to go through inf files, and find "DriverVer" >> string, like this one . taken from from vioscsi.inf >> >> DriverVer=08/01/2015,62.72.104.10800 >> >> This string contains build time and version stamps. The version stamp >> looks as follow "62.72.104.10800" >> where 62 means a target...

...key - "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion". Let's say it 6.3, which means that it is Win8.1 or WS2012R2, parsing "BuildLabEx" string from the same hive will give you information about the platform bitness. Next you need to go through inf files, and find "DriverVer" string, like this one . taken from from vioscsi.inf DriverVer=08/01/2015,62.72.104.10800 This string contains build time and version stamps. The version stamp looks as follow "62.72.104.10800" where 62 means a target Windows kernel version multiplied by 10. In this case it is 6....

...Corporation * ; ; Version: 2.0.0.5 ;**************************************************************** [Version] Signature = "$Windows NT$" CatalogFile = ax88172xp.cat Class = Net ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318} Provider = %ASIX% ;LayoutFile = layout.inf DriverVer = 05/22/2003, 2.0.0.5 [Manufacturer] %ASIX% = USB [ControlFlags] ExcludeFromSelect = USB\VID_0B95&PID_1720 [USB] %AX88172.DeviceDesc% = AX88172.Ndi,USB\VID_0B95&PID_1720 ;**************************************************************** ; Win98 main sections...

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

...f a [*.inf] file from the virtio-win drivers, + * figure out if it's suitable for the specific Windows flavor of the + * current guest. + *) +and virtio_inf_matches_guest_os inf_content inf_name inspect = + let sections = Windows_inf.of_string inf_content in + + (* Try to find the [Version] / DriverVer. *) + let driver_ver = parse_driver_ver inf_name sections in + + (* Try to find the [Manufacturer] line. *) + let driver_arch = parse_manufacturer inf_name sections in + + (* If we got both, we can continue, else give up. *) + match driver_ver, driver_arch with + | None, None | Some _, None...

...xpected = [ + "version", [ + "signature", "\"$WINDOWS NT$\""; + "class", "System"; + "classguid", "{4d36e97d-e325-11ce-bfc1-08002be10318}"; + "provider", "%RHEL%"; + "driverver", "12/04/2014,62.71.104.9600"; + "catalogfile", "Balloon.cat"; + "driverpackagetype", "PlugAndPlay"; + "driverpackagedisplayname", "%BALLOON.DeviceDesc%"; + "pnplockdown", "1"; +...

...or, Boston, MA 02110-1301 USA + */ + +/* Please read libvirt/README file. */ + +#ifdef __GNUC__ +#pragma GCC diagnostic ignored "-Wmissing-prototypes" +#endif + +/*----------------------------------------------------------------------*/ + +CAMLprim value +ocaml_libvirt_get_version (value driverv, value unit) +{ + CAMLparam2 (driverv, unit); + CAMLlocal1 (rv); + const char *driver = Optstring_val (driverv); + unsigned long libVer, typeVer = 0, *typeVer_ptr; + int r; + + typeVer_ptr = driver ? &typeVer : NULL; + NONBLOCKING (r = virGetVersion (&libVer, driver, typeVer_ptr)); +...

libvirt-ocaml is used only by virt-v2v, so move it to this repository, instead of having it around in the common submodule. The removal from common will happen later. Pino Toscano (2): common: Bundle the libvirt-ocaml library for use by virt-v2v build: switch embedded copy of libvirt-ocaml .gitignore | 2 + 3rdparty/libvirt-ocaml/Makefile.am |

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this series switches virt-2v to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not test all