search for: cc_0100

...N_1AF4&DEV_1001&SUBSYS_00021AF4&REV_00\3&13C0B0C5&0&40 Name: Red Hat VirtIO SCSI controller Hardware IDs: PCI\VEN_1AF4&DEV_1001&SUBSYS_00021AF4&REV_00 PCI\VEN_1AF4&DEV_1001&SUBSYS_00021AF4 PCI\VEN_1AF4&DEV_1001&CC_010000 PCI\VEN_1AF4&DEV_1001&CC_0100 Compatible IDs: PCI\VEN_1AF4&DEV_1001&REV_00 PCI\VEN_1AF4&DEV_1001 PCI\VEN_1AF4&CC_010000 PCI\VEN_1AF4&CC_0100 PCI\VEN_1AF4 PCI\CC_010000 PCI\CC_0100 PCI\VEN_1AF4...

...amp;SUBSYS_00021AF4&REV_00\3&13C0B0C5&0&40 > Name: Red Hat VirtIO SCSI controller > Hardware IDs: > PCI\VEN_1AF4&DEV_1001&SUBSYS_00021AF4&REV_00 > PCI\VEN_1AF4&DEV_1001&SUBSYS_00021AF4 > PCI\VEN_1AF4&DEV_1001&CC_010000 > PCI\VEN_1AF4&DEV_1001&CC_0100 > Compatible IDs: > PCI\VEN_1AF4&DEV_1001&REV_00 > PCI\VEN_1AF4&DEV_1001 > PCI\VEN_1AF4&CC_010000 > PCI\VEN_1AF4&CC_0100 > PCI\VEN_1AF4 > PCI\CC_010000 &...

...owly 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"; Yes - you are quite correct. I went back to the original Windows guest that I used for getting the registry changes, and found that I had transcribed these two strings incorrectly. Here is the fix: https://github.com/libguestfs/libguestfs/commit/938f48f08...

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

...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 to associate the viostor driver with devices from vendor http://pcidatabase.com/vendor_details.php?id=406, which I don't believe was your intent. JP On Tue, Feb 9, 2016 at 12:35 AM, Richard W.M. Jones <rjones@redhat.com&g...

...king 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"; > > Yes - you are quite correct. I went back to the original Windows > guest that I used for getting the registry changes, and found that I > had transcribed these two strings incorrectly. > > Here is the fix: > > > https://gi...

...;ClassGUID", REG_SZ scsi_adapter_guid; - "CompatibleIDs", REG_MULTI_SZ [ - "PCI\\VEN_1AF4&DEV_1001&REV_00"; - "PCI\\VEN_1AF4&DEV_1001"; - "PCI\\VEN_1AF4&CC_010000"; - "PCI\\VEN_1AF4&CC_0100"; - "PCI\\VEN_1AF4"; - "PCI\\CC_010000"; - "PCI\\CC_0100"; - ]; - "Conf...

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