Displaying 20 results from an estimated 1000 matches similar to: "Emailing: 0002-use-single-registry-change-for-all-supported-windows.patch"
2016 Apr 05
22
[PATCH 0/7] Add support for SUSE virtio windows drivers
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
2010 May 16
1
FW: Emailing: 0002-use-single-registry-change-for-all-supported-windows.patch
Attached is a fixed version of the patch.
> -----Original Message-----
> From: Richard W.M. Jones [mailto:rjones at redhat.com]
> Sent: Friday, May 14, 2010 10:23 AM
> To: Amos Benari
> Cc: libguestfs at redhat.com
> Subject: Re: [Libguestfs] Emailing: 0002-use-single-registry-change-
> for-all-supported-windows.patch
>
> > From: unknown <Amos at .(none)>
2016 Apr 06
8
[PATCH 0/4] v2v: simplify Windows registry patching
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
2017 Mar 14
3
Red Hat VirtIO SCSI pass-through controller
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
2014 Dec 02
1
[PATCH NOT TO BE APPLIED] v2v: windows: Make registry changes to all ControlSets, not
[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.
2010 May 06
1
[PATCH v2v] Pre-convert Windows guests.
This is my lightly tested patch which allows pre-conversion
of Windows guests.
You also need to supply rhsrvany.exe and firstboot scripts.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
2015 Oct 05
18
[PATCH 0/6] v2v: assorted improvements to tests for windows
This series makes several enhancements to tests for v2v conversion of
Windows guests. Specifically, it
- adds a number of files which imitate the stuff that is supposed to
be present on the host when the actual conversion is performed, but
may not be there when the tests are run. This includes certain
tools and virtio drivers
- fixes the test for windows conversion to actually
2010 Aug 16
2
[PATCH 1/2] Allow absolute paths in virt-v2v.conf
This patch allows paths in virt-v2v.conf to be either relative or absolute. If
relative, they are relative to software-root.
This allows virt-v2v.conf to use files provided by packages independent of
virt-v2v.
---
lib/Sys/VirtV2V/Config.pm | 10 ++++++----
1 files changed, 6 insertions(+), 4 deletions(-)
diff --git a/lib/Sys/VirtV2V/Config.pm b/lib/Sys/VirtV2V/Config.pm
index f703152..121e774
2016 May 12
24
[PATCH 00/11] Getting it work with SLES / openSUSE
Hi there!
I know it's been a while since I posted my first version of some patches.
But here I have rebased them on top of Roman's work and added a few other ones.
Cédric Bosdonnat (11):
v2v: also search for windows virtio drivers in symlinks
Update packagelist for SLES
customize: fix windows firstboot script
customize: change windows firstboot path
customize: add support for
2016 May 18
21
[PATCH v2 00/11] Getting it work with SLES / openSUSE
Hi all,
v2 includes all comments from Pino and Richard. I also removed the
mkdir /run/lvm in the init since it only failed in one case and couldn't
reproduce it anymore.
Cédric Bosdonnat (11):
v2v: also search for windows virtio drivers in symlinks
Update packagelist for SLES and openSUSE
customize: fix windows firstboot script
customize: change windows firstboot path
customize:
2023 Mar 06
1
[PATCH common] mlcustomize: Add accessors for block driver priority list
When injecting virtio-win drivers, allow the list of block drivers
that we search to be modified.
---
mlcustomize/inject_virtio_win.ml | 12 +++++++++---
mlcustomize/inject_virtio_win.mli | 10 ++++++++++
2 files changed, 19 insertions(+), 3 deletions(-)
diff --git a/mlcustomize/inject_virtio_win.ml b/mlcustomize/inject_virtio_win.ml
index 4e977b3..2a7c742 100644
---
2010 Oct 19
1
[PATCH] Fix Windows conversion when ControlSet001 isn't the CurrentControlSet
If a Windows boot fails and the user boots the last known good configuration,
ControlSet001 will be marked as failed and no longer used. However, virt-v2v
would only install viostor to ControlSet001, meaning it will fail to boot this
guest after conversion.
This patch looks up the current controlset and always installs registry keys to
the correct one.
Fixes RHBZ#644254
---
2011 Jan 25
1
[PATCH] Fix a Windows conversion error when C:\Temp exists in the guest
We were unconditionally creating /temp/v2v in the guest, and later using
case_sensitive_path to look the path up again. If C:\Temp already existed, this
would lead to unpredictable results.
Fixes RHBZ#672521
---
lib/Sys/VirtV2V/Converter/Windows.pm | 21 ++++++++++++++-------
1 files changed, 14 insertions(+), 7 deletions(-)
diff --git a/lib/Sys/VirtV2V/Converter/Windows.pm
2016 Apr 05
0
[PATCH 4/7] v2v: extract reusable parts of viostor regedits
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
+++
2016 Apr 05
2
Re: [PATCH 1/7] v2v: check next free oem%d.inf in /Windows/Inf
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
2014 Aug 10
2
About the return value of value_value
Hi,
I have been working on a Python application that uses hivex. Meanwhile I have
encountered some Python bindings issues which could be fixed.
The next issue I see now is about the value_value function. This is briefly
documented as: "return data length, data type and data of a value".
For Perl, Python and OCaml, this is not true. A tuple is returned for both
without the length
2014 Aug 10
2
New Python API? (was: Re: About the return value of value_value)
(renaming subject as I am partially getting off-topic)
On Sunday 10 August 2014 16:26:07 Richard W.M. Jones wrote:
> > The next issue I see now is about the value_value function. This is
> > briefly documented as: "return data length, data type and data of a
> > value".
> >
> > For Perl, Python and OCaml, this is not true. A tuple is returned
> >
2023 Mar 07
4
[COMMON PATCH v2 0/4] Bring support for virtio-scsi back to Windows
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
2015 Nov 05
6
[PATCH 0/4] Provide better fake virtio-* test data for virt-v2v.
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
2023 Mar 10
4
[COMMON PATCH v3 0/4] Bring support for virtio-scsi back to Windows
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