similar to: Re: Help with Win10

On Tue, Feb 09, 2016 at 12:20:35AM -0800, Joshua Pincus wrote: > Hi Rich, > > Thanks for the pointer. It looks like add_viostor_to_driver_database() is > the routine that I need to mimic. I'll try that out in the morning. I've > been staring at this problem for so long that my eyes are crossing. I should note that any doubled \\ that appear in the strings are really

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

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

Hi Rich, Thanks, again, for the pointer. I'm still slowly going through the registry making my changes. I noticed what may be a small bug in your code. Please look at https://github.com/libguestfs/libguestfs/blob/master/v2v/windows_virtio.ml#L230-L231. I think you meant to have those two compat ids be: "PCI\\CC_010000"; "PCI\\CC_0100"; The current IDs in your code try

On Tue, Apr 05, 2016 at 01:47:27PM +0200, Cédric Bosdonnat wrote: > + let oem_inf = set_free_oem_inf g root scsi_adapter_guid "viostor.inf" driverdir in Seems better if it was called *get_next*_free_oem_inf? > > (* There should be a key > * HKLM\SYSTEM\ControlSet001\Control\Class\<scsi_adapter_guid> > @@ -398,6 +378,28 @@ and

There are registry entries that are needed to add some other drivers. Extracting them into a function will help adding SUSE VMDP support. --- v2v/windows_virtio.ml | 311 ++++++++++++++++++++++++++++---------------------- 1 file changed, 176 insertions(+), 135 deletions(-) diff --git a/v2v/windows_virtio.ml b/v2v/windows_virtio.ml index 14ffc51..8a0b529 100644 --- a/v2v/windows_virtio.ml +++

Hi Rich, Thanks for the pointer. It looks like add_viostor_to_driver_database() is the routine that I need to mimic. I'll try that out in the morning. I've been staring at this problem for so long that my eyes are crossing. Thank you very much for the quick reply! JP On Tue, Feb 9, 2016 at 12:11 AM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Mon, Feb 08, 2016 at

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(+),

On Tue, Feb 09, 2016 at 01:50:37PM -0800, Joshua Pincus wrote: > Hi Rich, > > Thanks, again, for the pointer. I'm still slowly going through the > registry making my changes. > > I noticed what may be a small bug in your code. Please look at > https://github.com/libguestfs/libguestfs/blob/master/v2v/windows_virtio.ml#L230-L231. > I think you meant to have those two

On Tue, 2016-04-05 at 13:04 +0100, Richard W.M. Jones wrote: > On Tue, Apr 05, 2016 at 01:47:27PM +0200, Cédric Bosdonnat wrote: > > + let oem_inf = set_free_oem_inf g root scsi_adapter_guid > > "viostor.inf" driverdir in > > Seems better if it was called *get_next*_free_oem_inf? Yes, sounds better. > > (* There should be a key > > *

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

Hello, All! virtio-win.iso contains two different Windows drivers. these Windows Server 2012 R2 drivers have different hardware IDs: \vioscsi\2k12R2\amd64\vioscsi.inf "Red Hat VirtIO SCSI pass-through controller" PCI\VEN_1AF4&DEV_1004&SUBSYS_00081AF4&REV_00 PCI\VEN_1AF4&DEV_1048&SUBSYS_11001AF4&REV_01 \viostor\2k12R2\amd64\viostor.inf "Red Hat VirtIO SCSI

Hi Richard, Thanks for all your help. Turns out that I needed to get a handle on the StartOverride rubbish that MSFT pushed into Win8 and Win10. It was preventing my viostor service from starting at boot, much like what many poor souls found when they tried to enable/disable AHCI in the BIOS of their machines. Do you know which entity is responsible for modifying the registry at boot to

To add this support, the existing code searches for either the viostor or the VMDP (Virtual Machine Driver Pack) files and updates the registry accordingly. Note that VMDP's block driver pvvxblk depends on the ballooning driver pvvxbn. --- v2v/convert_windows.ml | 59 ++++++++++++++++++++------ v2v/windows_virtio.ml | 113 +++++++++++++++++++++++++++++++++++++++++-------- 2 files changed,

From: "Richard W.M. Jones" <rjones at redhat.com> When injecting virtio-win drivers, allow the list of block drivers that we search to be modified. This functionality will be used when we introduce an option for changing the default block driver in virt-v2v. Originally-by: Richard W.M. Jones <rjones at redhat.com> Signed-off-by: Andrey Drobyshev <andrey.drobyshev at

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 there, I've got two questions, and I'll list them in order of importance. (1) Is there a way, or is there any research/development going into unearthing a way, to mount a samba filesystem like any other filesystem under UNIX? And (2), does anyone know of a good X filemanager? What I would really like to do is be able to mount a Samba directory or resource and treat it like any

Hello guys, I was some years ago when I sent something to this list. NUT is a great tool but lacks SNMP management. It can access a device using SNMP but I found no way to read NUT values using SNMP. It would be very useful in order to integrate with network management software based on SNMP. As I did not find a solution, I wrote it myself. I wrote a MIB file and a SNMP agent for net-snmp

Hello guys, I was some years ago when I sent something to this list. NUT is a great tool but lacks SNMP management. It can access a device using SNMP but I found no way to read NUT values using SNMP. It would be very useful in order to integrate with network management software based on SNMP. As I did not find a solution, I wrote it myself. I wrote a MIB file and a SNMP agent for net-snmp

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