search for: oem1

...eally single \, they are just escaped OCaml strings. It might help to fire up the OCaml interpreter: $ rlwrap ocaml OCaml version 4.02.3 # open Printf;; # printf "PCI\\VEN_1AF4&DEV_1001&REV_00\n";; PCI\VEN_1AF4&DEV_1001&REV_00 - : unit = () # let oem_inf = "oem1.inf";; val oem_inf : string = "oem1.inf" # printf "@%s,%%rhelscsi.devicedesc%%;Red Hat VirtIO SCSI controller\n" oem_inf;; @oem1.inf,%rhelscsi.devicedesc%;Red Hat VirtIO SCSI controller - : unit = () Rich. -- Richard Jones, Virtualization Group, Red Hat http://peopl...

It seems that checking for oem%d.inf in the DeviceIds registry entry doesn't always list all oemXX.inf files. For example we may have oem1.inf free in the registry key, but used in another one. Also extract this into a separate function for later use to setup another driver. --- v2v/windows_virtio.ml | 52 ++++++++++++++++++++++++++------------------------- 1 file changed, 27 insertions(+), 25 deletions(-) diff --git a/v2v/windows_...

...,28 @@ and add_viostor_to_driver_database g root arch current_cs = > @=hex(ffff0012):6f,00,65,00,6d,00,31,00,2e,00,69,00,6e,00,66,00,00,00 > *) > > +(* There should be a key > + * HKLM\SYSTEM\DriverDatabase\DeviceIds\<guid> > + * We want to add: > + * "oem1.inf"=hex(0): > + * but if we find "oem1.inf" we'll add "oem2.inf" (etc). > + *) > +and set_free_oem_inf g root guid driver_inf driverdir = > + let path = [ "DriverDatabase"; "DeviceIds"; guid ] in > + match Windows.get_node g root pa...

...ngs. It might help > to fire up the OCaml interpreter: > > $ rlwrap ocaml > OCaml version 4.02.3 > > # open Printf;; > # printf "PCI\\VEN_1AF4&DEV_1001&REV_00\n";; > PCI\VEN_1AF4&DEV_1001&REV_00 > - : unit = () > # let oem_inf = "oem1.inf";; > val oem_inf : string = "oem1.inf" > # printf "@%s,%%rhelscsi.devicedesc%%;Red Hat VirtIO SCSI controller\n" > oem_inf;; > @oem1.inf,%rhelscsi.devicedesc%;Red Hat VirtIO SCSI controller > - : unit = () > > Rich. > > > -- > Richar...

On Mon, Feb 08, 2016 at 04:50:09PM -0800, Joshua Pincus wrote: > Mr Jones, > > I recently came across your excellent 2010 blog entry, > https://rwmj.wordpress.com/2010/04/30/tip-install-a-device-driver-in-a-windows-vm/. > The blog entry was incredibly useful for Win7. I was wondering if you have > any similar insights for Win10? The CDDB is gone, and it's replacement, or

...rent_cs = > > > > @=hex(ffff0012):6f,00,65,00,6d,00,31,00,2e,00,69,00,6e,00,66,00,00 > > ,00 > > *) > > > > +(* There should be a key > > + * HKLM\SYSTEM\DriverDatabase\DeviceIds\<guid> > > + * We want to add: > > + * "oem1.inf"=hex(0): > > + * but if we find "oem1.inf" we'll add "oem2.inf" (etc). > > + *) > > +and set_free_oem_inf g root guid driver_inf driverdir = > > + let path = [ "DriverDatabase"; "DeviceIds"; guid ] in > > + match W...

Hi there, SUSE ships Virtual Machine Driver Pack for the virtio windows drivers. Get v2v and customize to discover them and use them if available. Cédric Bosdonnat (7): v2v: check next free oem%d.inf in /Windows/Inf v2v: extract controller offset discovery as a function customize: add support for pvvxsvc v2v: extract reusable parts of viostor regedits v2v: adapt the subkey in Enum

...Tue, 2016-04-05 at 15:13 +0300, Roman Kagan wrote: > On Tue, Apr 05, 2016 at 01:47:27PM +0200, Cédric Bosdonnat wrote: > > It seems that checking for oem%d.inf in the DeviceIds registry > > entry > > doesn't always list all oemXX.inf files. For example we may have > > oem1.inf free in the registry key, but used in another one. > > In my experiments this name doesn't have to bear any sense, so > there's > no point doing anything smart about it. What I did was not a strictly scientific approach, rather trying to mimic what seemed to happen ;) &gt...

...full path - C:\windows\temp\~ndtmp~\ndisrd.inf Current miniport full path - C:\windows\temp\~ndtmp~\ndisrd_m.inf Trying to install 'nt_ndisrd'... ...C:\windows\temp\~ndtmp~\ndisrd.inf was copied to C:\windows\inf\oem0.inf ...C:\windows\temp\~ndtmp~\ndisrd_m.inf was copied to C:\windows\inf\oem1.inf fixme:advapi:CheckTokenMembership ((nil) 0x1220c8 0x33f1a4) stub! ..failed. Error code: 0x80070002

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

...(XEN) DMI present. (XEN) Using APIC driver default (XEN) ACPI: RSDP (v000 PTLTD ) @ 0x000f8700 (XEN) ACPI: RSDT (v001 PTLTD RSDT 0x06040000 LTP 0x06040000) @ 0x37ea2f17 (XEN) ACPI: FADT (v004 UNISYS ZORRO 0x06040000 PTL 0x00000008) @ 0x37ede144 (XEN) ACPI: OEM1 (v001 UNISYS OEM1 0x06040000 LTP 0x06040000) @ 0x37ede238 (XEN) ACPI: OEM2 (v001 UNISYS OEM2 0x06040000 LTP 0x06040000) @ 0x37ede268 (XEN) ACPI: WSPT (v001 UNISYS WSPT 0x06040000 LTP 0x06040000) @ 0x37edee64 (XEN) ACPI: SRAT (v001 UNISYS SRAT 0x06040000 LTP 0x06040000) @ 0x37ede...

Is there a little setup display right on the box? Just asking because I have seen that on some boxes. Cheers, Boris. On Sun, Sep 18, 2016 at 12:15 AM, Keith Keller < kkeller at wombat.san-francisco.ca.us> wrote: > On 2016-09-17, Alice Wonder <alice at domblogger.net> wrote: > > > > Okay if it requires DHCP this might be out, I'm currently out of town > >

...68B7B000, 0038 (r1 IBM SERMEGAL 1 MSFT 1000017) (XEN) ACPI: APIC 68B78000, 007E (r3 IBM SERMEGAL 0 MSFT 1000014) (XEN) ACPI: MCFG 68B7A000, 003C (r1 IBM SERMEGAL 1 MSFT 1000018) (XEN) ACPI: OEM0 68B79000, 00E0 (r3 IBM XSECSRAT 100 MSFT 1000022) (XEN) ACPI: OEM1 68B77000, 0030 (r1 IBM IBMERROR 1 MSFT 1000013) (XEN) ACPI: SLIT 68B19000, 0030 (r1 IBM SERMEGAL 1 MSFT 1000020) (XEN) ACPI: SRAT 68B18000, 00C0 (r3 IBM SERMEGAL 1 MSFT 100001A) (XEN) ACPI: SLIC 68B17000, 0176 (r1 IBM SERMEGAL 0 MSFT 100001F) (XEN) ACPI:...

...EG_DWORD 0x00000002_l ]; ] in - reg_import g root regedits; + (reg_import g root regedits; + if (driver_name = "pvvxblk") then + add_pvvxbn_to_driver_database g root arch current_cs driverdir + ); (* A few more keys which we don't add above. Note that "oem1.inf" == @@ -454,6 +474,63 @@ and get_common_regedits g root current_cs adapter_guid driverdir driver driverde driverdesc_key, REG_SZ driverdesc ]; ] +and add_pvvxbn_to_driver_database g root arch current_cs driverdir = + + let driver_name = "pvvxbn" in + + let inf_full...

...3) @ 0x000000009fb36000 (XEN) ACPI: SPCR (v001 INTEL S5000PAL 0x00000000 INTL 0x01000013) @ 0x000000009fb2f000 (XEN) ACPI: HPET (v001 INTEL S5000PAL 0x00000001 INTL 0x01000013) @ 0x000000009fb2e000 (XEN) ACPI: MCFG (v001 INTEL S5000PAL 0x00000001 INTL 0x01000013) @ 0x000000009fb2d000 (XEN) ACPI: OEM1 (v001 INTEL S5000PAL 0x00000001 INTL 0x01000013) @ 0x000000009fb2c000 (XEN) ACPI: SSDT (v002 INTEL EIST 0x00004000 INTL 0x01000013) @ 0x000000009fb2b000 (XEN) ACPI: SSDT (v002 INTEL IPMI 0x00004000 INTL 0x01000013) @ 0x000000009fb2a000 (XEN) ACPI: DSDT (v002 INTEL S5000PAL 0x00000008 IN...

...0] ACPI: APIC 0x000000006006B000 0000DE (v03 IBM SERMEGAL 00000000 MSFT 01000014) [ 0.000000] ACPI: MCFG 0x00000000602FD000 00003C (v01 IBM SERMEGAL 00000001 MSFT 01000018) [ 0.000000] ACPI: OEM0 0x00000000602FC000 0001A0 (v03 IBM XSECSRAT 00000100 MSFT 01000022) [ 0.000000] ACPI: OEM1 0x000000006006A000 000030 (v01 IBM IBMERROR 00000001 MSFT 01000013) [ 0.000000] ACPI: SLIT 0x0000000060069000 000030 (v01 IBM SERMEGAL 00000001 MSFT 01000020) [ 0.000000] ACPI: SRAT 0x0000000060068000 000180 (v03 IBM SERMEGAL 00000001 MSFT 0100001A) [ 0.000000] ACPI: SLIC 0x000000...