Displaying 20 results from an estimated 1000 matches similar to: "[PATCH v4] windows: delay installation of qemu-ga MSI"
2020 Mar 03
2
[PATCH v3] windows: delay installation of qemu-ga MSI
Instead of running firstboot script during early boot schedule a task
delayed for 2 minutes.
During the first boot, after virt-v2v conversion, Windows installs the
drivers injected by virt-v2v. When this installation is finished
Windows enforces some kind of internal reboot. This unfortunately
terminates any running firstboot scripts thus killing the installation
of qemu-ga MSI.
This is just a
2020 Mar 05
1
Re: [PATCH v3] windows: delay installation of qemu-ga MSI
On Thu, Mar 05, 2020 at 08:49:04AM +0000, Richard W.M. Jones wrote:
> On Tue, Mar 03, 2020 at 03:45:49PM +0100, Tomáš Golembiovský wrote:
> > Instead of running firstboot script during early boot schedule a task
> > delayed for 2 minutes.
> >
> > During the first boot, after virt-v2v conversion, Windows installs the
> > drivers injected by virt-v2v. When this
2020 Mar 02
2
Re: [PATCH 1/1] windows: delay installation of qemu-ga MSI
On Mon, Mar 02, 2020 at 12:26:00PM +0100, Tomáš Golembiovský wrote:
> Instead of running firstboot script during early boot schedule a task
> delayed for 1-2 minute.
IIUC, you picked 119 seconds, so effectively 2 minutes. IOW, s/1-2/2/
> During the first boot, after virt-v2v conversion, Windows installs the
> drivers injected by virit-v2v. When this installation is finished
2020 Mar 10
0
Re: [PATCH v4] windows: delay installation of qemu-ga MSI
On Thu, Mar 05, 2020 at 03:37:13PM +0100, Tomáš Golembiovský wrote:
> Instead of running firstboot script during early boot schedule a task
> delayed for 2 minutes.
>
> During the first boot, after virt-v2v conversion, Windows installs the
> drivers injected by virt-v2v. When this installation is finished
> Windows enforces some kind of internal reboot. This unfortunately
>
2020 Mar 05
0
Re: [PATCH v3] windows: delay installation of qemu-ga MSI
On Tue, Mar 03, 2020 at 03:45:49PM +0100, Tomáš Golembiovský wrote:
> Instead of running firstboot script during early boot schedule a task
> delayed for 2 minutes.
>
> During the first boot, after virt-v2v conversion, Windows installs the
> drivers injected by virt-v2v. When this installation is finished
> Windows enforces some kind of internal reboot. This unfortunately
>
2020 Mar 03
0
[PATCH v2] windows: delay installation of qemu-ga MSI
Instead of running firstboot script during early boot schedule a task
delayed for 2 minutes.
During the first boot, after virt-v2v conversion, Windows installs the
drivers injected by virt-v2v. When this installation is finished
Windows enforces some kind of internal reboot. This unfortunately
terminates any running firstboot scripts thus killing the installation
of qemu-ga MSI.
Signed-off-by:
2020 Mar 02
2
[PATCH 0/1] Delay installation of QEMU-GA
This is a replacement for previously posted patch "Delay firstboot scripts to
some later time":
https://www.redhat.com/archives/libguestfs/2019-November/msg00134.html
Instead of delaying all the firstboot scripts we just delay the QEMU-GA
installation that we know is problematic. I will possibly send a similar patch
for RHEV-APT installation later.
Tom?? Golembiovsk? (1):
windows:
2020 Mar 02
0
[PATCH 1/1] windows: delay installation of qemu-ga MSI
Instead of running firstboot script during early boot schedule a task
delayed for 1-2 minute.
During the first boot, after virt-v2v conversion, Windows installs the
drivers injected by virit-v2v. When this installation is finished
Windows enforces some kind of internal reboot. This unfortunately
terminates any running firstboot scritps thus killing the installation
of qemu-ga MSI.
Signed-off-by:
2020 Feb 05
3
[PATCH v2 0/2] Fixes and tweak to the installation of qemu-ga MSI
This, together with the changes to common repo are fixes to the installation
qemu-ga MSI.
There is still an issue that I did not figure yet how to fix. On Windows 10 it
fails to register the QEMU-GA service.
Tomáš Golembiovský (2):
windows: fix detection of qemu-ga installer on RHV
windows: small tweaks of qemu-ga firstboot script
v2v/convert_windows.ml | 8 +++++++-
v2v/windows_virtio.ml
2020 Mar 03
0
Re: [PATCH 1/1] windows: delay installation of qemu-ga MSI
On Mon, Mar 02, 2020 at 11:35:29AM +0000, Daniel P. Berrangé wrote:
> On Mon, Mar 02, 2020 at 12:26:00PM +0100, Tomáš Golembiovský wrote:
> > Instead of running firstboot script during early boot schedule a task
> > delayed for 1-2 minute.
>
> IIUC, you picked 119 seconds, so effectively 2 minutes. IOW, s/1-2/2/
>
Well, the time is rounded down to minutes. It cannot be
2019 Nov 21
7
[PATCH 0/2] Fixes and tweak to the installation of qemu-ga MSI
This, together with the changes to common repo are fixes to the installation
qemu-ga MSI.
There is still an issue that I did not figure yet how to fix. On Windows 10 it
fails to register the QEMU-GA service.
Tomáš Golembiovský (2):
windows: fix detection of qemu-ga installer on RHV
windows: small tweaks of qemu-ga firstboot script
v2v/convert_windows.ml | 8 +++++++-
v2v/windows_virtio.ml
2020 Feb 05
0
[PATCH v2 2/2] windows: small tweaks of qemu-ga firstboot script
- match log file with script name
- restart manually only after successfull install, this also helps
debugging because we can log the installer return code
Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com>
---
v2v/convert_windows.ml | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/v2v/convert_windows.ml b/v2v/convert_windows.ml
index 5b7a5bfe..0fda1d4e
2019 Oct 08
1
[PATCH] v2v: windows: install QEMU Guest Agent MSI
Use firstboot script to install MSI with QEMU-GA from virtio-win ISO or
oVirt/RHV guest tools ISO.
Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com>
---
v2v/convert_windows.ml | 19 +++++++++++++++++++
v2v/windows_virtio.ml | 27 +++++++++++++++++++++++++++
v2v/windows_virtio.mli | 4 ++++
3 files changed, 50 insertions(+)
diff --git a/v2v/convert_windows.ml
2020 Mar 10
1
Re: [PATCH v4] windows: delay installation of qemu-ga MSI
> > diff --git a/common b/common
> > index ea10827b..5371257c 160000
> > --- a/common
> > +++ b/common
> > @@ -1 +1 @@
> > -Subproject commit ea10827b4cfb3cfe5f782421c01d2902e5f73f90
> > +Subproject commit 5371257c3cf27fb09d5f2e31ba378b0e6ccf5df6
>
> I think(?) this hunk was not intended?
>
Yes, that's a mistake. Sorry for that.
Tomas
2015 Feb 27
5
[PATCH 0/4] firstboot: assorted enhancements
This patchset attempts to address a number of shortcomings in the
firstboot infrastructure I came across while working with v2v conversion
of various Windows VMs.
Roman Kagan (4):
firstboot: consolidate line ending conversion
firstboot: enhance firstboot driver script for Windows
firstboot: make script naming descriptive
convert_windows: split firstboot into steps
2016 Jan 20
1
[PATCH] convert_windows: uninstall Parallels Tools on first boot
If present, Parallels Tools may stand in the way of proper running the
windows guests in non-Parallels hypervisors, so we're better off
uninstalling them on the first boot into the new environment.
With this patch, the uninstall records for Parallels Tools are looked up
in the registry and, if found, corresponding firstboot actions are
registered, taking special care that those actions are
2016 May 23
4
[PATCH v3 0/3] SUSE VMDP support
Hi there,
Here is v3 of the remaining patches. Diff to v2:
* Removed the patch related to QXL
* Fixed the firstboot script with Roman's comments
* Fixed ova with subfolders test
* Handle MF-relative path in ova files
* Fixed now unneeded match case as per Richard's comment
Cédric Bosdonnat (3):
customize: fix windows firstboot script
v2v: add support for SUSE VMDP drivers
v2v:
2023 Mar 09
1
[V2V PATCH v2 1/1] convert_windows: add firstboot script to install drivers with pnputil
During conversion we copy the necessary drivers to the directory
"%systemroot%\Drivers\Virtio", adding it to the DevicePath registry
value. As documented in [1], this should be enough for Windows to find
device drivers and successfully install them.
However, it doesn't always happen. Commit 73e009c04 ("v2v: windows:
Document use of pnputil to install drivers.") describes
2023 Mar 08
1
[V2V PATCH 1/1] convert_windows: add firstboot script to install drivers with pnputil
During conversion we copy the necessary drivers to the directory
"%systemroot%\Drivers\Virtio", adding it to the DevicePath registry
value. As documented in [1], this should be enough for Windows to find
device drivers and successfully install them.
However, it doesn't always happen. Commit 73e009c04 ("v2v: windows:
Document use of pnputil to install drivers.") describes
2023 Mar 08
1
[V2V PATCH 1/1] convert_windows: add firstboot script to install drivers with pnputil
On Wed, Mar 08, 2023 at 08:05:35PM +0200, Andrey Drobyshev wrote:
> During conversion we copy the necessary drivers to the directory
> "%systemroot%\Drivers\Virtio", adding it to the DevicePath registry
> value. As documented in [1], this should be enough for Windows to find
> device drivers and successfully install them.
>
> However, it doesn't always happen.