search for: e325

...GUID. These are defined as service to allow defining how they boot. When Start is set to 00000000, it means that you want them to be started at boot: when Windows needs to find its boot device. I hope this helped! [1]: key {value(type): data} primary_ide_channel { ClassGUID(REG_SZ): {4D36E96A-E325-11CE-BFC1-08002BE10318} Service(REG_SZ): atapi } secondary_ide_channel { ClassGUID(REG_SZ): {4D36E96A-E325-11CE-BFC1-08002BE10318} Service(REG_SZ): atapi } pci#ven_8086&dev_7010 { ClassGUID(REG_SZ): {4D36E96A-E325-11CE-BFC1-08002BE10318} Service(REG_SZ): intelide } pci#ven...

[Partly using the mailing list as a backup again ...] This commit changes virt-v2v to make registry changes to all ControlSets, not just the CurrentControlSet. Not sure what difference if any this would make. Rich.

...se the uninstaller called from firstboot script. *) + g#hivex_node_set_value svc_node "Start" 4_L (le32_of_int 4_L) + ) + ) prl_svcs; + + (* perfrom the equivalent of DelReg from prl_strg.inf: + * HKLM, System\CurrentControlSet\Control\Class\{4d36e967-e325-11ce-bfc1-08002be10318}, LowerFilters, 0x00018002, prl_strg + *) + let strg_cls = Windows.get_node g root + [current_cs; "Control"; "Class"; + "{4d36e967-e325-11ce-bfc1-08002be10318}"] in + match strg_cls with +...

...STEM\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1af4&dev_1001&subsys_00000000] +[HKEY_LOCAL_MACHINE\\SYSTEM\\$current_cs\\Control\\CriticalDeviceDatabase\\pci#ven_1af4&dev_1001&subsys_00000000] "Service"="viostor" "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}" -[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1af4&dev_1001&subsys_00020000] +[HKEY_LOCAL_MACHINE\\SYSTEM\\$current_cs\\Control\\CriticalDeviceDatabase\\pci#ven_1af4&dev_1001&subsys_00020000] "Service"=&qu...

...[ current_cs; "Control"; "CriticalDeviceDatabase"; "pci#ven_1af4&dev_1001&subsys_00000000" ], - [ "Service", REG_SZ "viostor"; + [ "Service", REG_SZ driver_name; "ClassGUID", REG_SZ "{4D36E97B-E325-11CE-BFC1-08002BE10318}" ]; [ current_cs; "Control"; "CriticalDeviceDatabase"; "pci#ven_1af4&dev_1001&subsys_00020000" ], - [ "Service", REG_SZ "viostor"; + [ "Service", REG_SZ driver_name; "Cl...

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

...egedits_w2k3 = ' +; Edits to be made to a Windows 2003 guest to have +; it boot from viostor. + +[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1af4&dev_1001&subsys_00000000] +"Service"="viostor" +"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}" + +[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1af4&dev_1001&subsys_00020000] +"Service"="viostor" +"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}" + +[HKEY_LOCAL_MACHINE\SYSTEM\Co...

...t_virtio_win.ml b/mlcustomize/inject_virtio_win.ml index 4e977b3..ed63fa7 100644 --- a/mlcustomize/inject_virtio_win.ml +++ b/mlcustomize/inject_virtio_win.ml @@ -110,10 +110,10 @@ and get_inspection g root = virtio_win = ""; was_set = false } let scsi_class_guid = "{4D36E97B-E325-11CE-BFC1-08002BE10318}" -let viostor_legacy_pciid = "VEN_1AF4&DEV_1001&SUBSYS_00021AF4&REV_00" -let viostor_modern_pciid = "VEN_1AF4&DEV_1042&SUBSYS_11001AF4&REV_01" -let vioscsi_legacy_pciid = "VEN_1AF4&DEV_1004&SUBSYS_00081AF4&REV...

...et\\Control\\DeviceClasses",20019,0x32e1a4) trace:reg:NtOpenKey <- (nil) trace:reg:NtOpenKey (0x28,L"SYSTEM\\CurrentControlSet\\Services\\Modem\\Enum",20019,0x32e51c) trace:reg:NtOpenKey <- (nil) If you create "DeviceClasses" then it scans 2 keys inside: {4D36E978-E325-11CE-BFC1-08002BE10318} {86E0D1E0-8089-11D0-9CE4-08003E301F73} I don't know what to put there wine-1.1.25

...t_virtio_win.ml b/mlcustomize/inject_virtio_win.ml index 4e977b3..8d72c5d 100644 --- a/mlcustomize/inject_virtio_win.ml +++ b/mlcustomize/inject_virtio_win.ml @@ -110,10 +110,10 @@ and get_inspection g root = virtio_win = ""; was_set = false } let scsi_class_guid = "{4D36E97B-E325-11CE-BFC1-08002BE10318}" -let viostor_legacy_pciid = "VEN_1AF4&DEV_1001&SUBSYS_00021AF4&REV_00" -let viostor_modern_pciid = "VEN_1AF4&DEV_1042&SUBSYS_11001AF4&REV_01" -let vioscsi_legacy_pciid = "VEN_1AF4&DEV_1004&SUBSYS_00081AF4&REV...

Hi, The error line is: *** STOP: 0x0000007B (0xF789AA94, 0xC0000034, 0x00000000, 0x00000000) Nothing more! (Of course there are some inrelevant text line about chkdsk, etc.) > Basically, what's required is the "STOP:" line + the image where it > fails (so, the line below). Image being likely to be NTOSKRNL.EXE > Nothing about NTOSKRNL.EXE on the blue screen! > >

...all device driver software, but the driver software encountered a problem when it tried to run. The problem code is 10. Problem Signature: Problem Event Name:PnPDeviceProblemCode Architecture: x86 Hardware Id: PCI\VEN_1000&DEV_0411&SUBSYS_10081000&REV_00 Setup class GUID: {4d36e97b-e325-11ce-bfc1-08002be10318} PnP problem code: 0000000A Driver name: megasas.sys Driver version: 2.13.0.32 Driver date: 01-19-2008 OS Version: 6.0.6001.2.1.0.272.7 Locale ID: 1033 =====================================================================================================================...

...ot;"; was_set = false; + block_driver_priority = ["virtio_blk"; "vrtioblk"; "viostor"] } + +let get_block_driver_priority t = t.block_driver_priority +let set_block_driver_priority t v = t.block_driver_priority <- v let scsi_class_guid = "{4D36E97B-E325-11CE-BFC1-08002BE10318}" let viostor_legacy_pciid = "VEN_1AF4&DEV_1001&REV_00" @@ -176,14 +183,13 @@ let rec inject_virtio_win_drivers ({ g } as t) reg = else ( (* Can we install the block driver? *) let block : block_type = - let filenames = ["virtio_...

...ot;"; was_set = false; + block_driver_priority = ["virtio_blk"; "vrtioblk"; "viostor"] } + +let get_block_driver_priority t = t.block_driver_priority +let set_block_driver_priority t v = t.block_driver_priority <- v let scsi_class_guid = "{4D36E97B-E325-11CE-BFC1-08002BE10318}" let viostor_legacy_pciid = "VEN_1AF4&DEV_1001&SUBSYS_00021AF4&REV_00" @@ -176,14 +183,13 @@ let rec inject_virtio_win_drivers ({ g } as t) reg = else ( (* Can we install the block driver? *) let block : block_type = - let filena...

Discussion on v1 https://listman.redhat.com/archives/libguestfs/2023-February/030849.html https://listman.redhat.com/archives/libguestfs/2023-March/030917.html v1 -> v2: * Drop the logic where default is switched to "vioscsi". Keep virtio-blk as default. * Adapt the patch suggested by Richard: https://listman.redhat.com/archives/libguestfs/2023-March/030974.html This

Discussion on v2: https://listman.redhat.com/archives/libguestfs/2023-March/030989.html v2 -> v3: * Patch 1/4 ("inject_virtio_win: match only vendor/device/revision"): do not omit PCI Revision ID. Adjust commit message accordingly; * Patch 2/4 ("inject_virtio_win: add Virtio_SCSI to block_type"): add non-empty commit message body. * Patch 4/4

Hi all. I have read carefully all your posts and I am glad to see that some of you workaround this new MS surprise... To solve the problem, I understand that : * if you use the "AD way of deploying printers", the workaround is to use the "Computer ConfigurationPoliciesAdministrative TemplatesPrintersOverride Print Driver Compatibility Execution Setting Reported By Print

Hai Christian, Hm,, you tried that Universal driver and it did not work for you,. .. :-/ That worked fine for me, so its one to have a better look at. I saw you used acl_xattr:ignore system acl also. After you changed smb.conf, did you re-apply also the rights on the shares? Try it in this order, first setup the share and correct the rights. Then correct the rights on the file system,

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

...must add keys into the DriverDatabase. *) - let driver = "viostor.sys" in let driver_name = Filename.chop_extension driver in let inf_full = @@ -229,8 +242,12 @@ and add_viostor_to_driver_database g root arch current_cs driverdir = let scsi_adapter_guid = "{4d36e97b-e325-11ce-bfc1-08002be10318}" in - let driverdesc = "Red Hat VirtIO SCSI controller" in - let provider = "Red Hat, Inc." in + let driverdesc = if (driver_name = "pvvxblk") + then "SUSE Block Driver for Windows" + else "Red Hat VirtIO SCSI cont...