Hi Richard,
On Thu, Sep 28, 2023 at 7:54 PM Richard W.M. Jones
wrote:
> On Thu, Sep 28, 2023 at 07:41:55PM +0800, Ming Xie wrote:
> > Hi Richard,
> >
> > On Thu, Sep 28, 2023 at 6:14 PM Richard W.M. Jones
> wrote:
> >
> > Ming,
> >
> > For some reason the build seems "stuck" at the
Hi Lee,
On Thu, Sep 28, 2023 at 10:55 PM Lee Garrett wrote:
> (resend, as it bounced on tyan-...@redhat.com)
>
> Hi Ming,
>
> On 27.09.23 14:46, Ming Xie wrote:
> > Hi Richard,
> >
> > Sorry, I missed the email, I found out that the ova OS used by the
> customer is
> > win11 uefi, so I tried to
On Mon, Oct 02, 2023 at 01:00:00PM +0800, Ming Xie wrote:
> Hi Richard,
>
> On Fri, Sep 29, 2023 at 5:45 AM Richard W.M. Jones wrote:
>
> On Thu, Sep 28, 2023 at 07:41:55PM +0800, Ming Xie wrote:
> > Hi Richard,
> >
> > On Thu, Sep 28, 2023 at 6:14 PM Richard W.M. Jones
>
Hi Richard,
On Fri, Sep 29, 2023 at 5:45 AM Richard W.M. Jones
wrote:
> On Thu, Sep 28, 2023 at 07:41:55PM +0800, Ming Xie wrote:
> > Hi Richard,
> >
> > On Thu, Sep 28, 2023 at 6:14 PM Richard W.M. Jones
> wrote:
> >
> > Ming,
> >
> > For some reason the build seems "stuck" at the
On Thu, Sep 28, 2023 at 07:41:55PM +0800, Ming Xie wrote:
> Hi Richard,
>
> On Thu, Sep 28, 2023 at 6:14 PM Richard W.M. Jones wrote:
>
> Ming,
>
> For some reason the build seems "stuck" at the moment, but
> if it finishes could you see if this fixes the RHEL 9 case?
>
>
(resend, as it bounced on tyan-...@redhat.com)
Hi Ming,
On 27.09.23 14:46, Ming Xie wrote:
Hi Richard,
Sorry, I missed the email, I found out that the ova OS used by the customer is
win11 uefi, so I tried to reproduce the error today using win11-uefi guest
Steps:
1. Convert win10-efi with
Hi Ming,
On 27.09.23 14:46, Ming Xie wrote:
Hi Richard,
Sorry, I missed the email, I found out that the ova OS used by the customer is
win11 uefi, so I tried to reproduce the error today using win11-uefi guest
Steps:
1. Convert win10-efi with UTC-8 timezone, win11-non-efi with UTC-8
On Thu, Sep 28, 2023 at 07:41:55PM +0800, Ming Xie wrote:
> Hi Richard,
>
> On Thu, Sep 28, 2023 at 6:14 PM Richard W.M. Jones wrote:
>
> Ming,
>
> For some reason the build seems "stuck" at the moment, but
> if it finishes could you see if this fixes the RHEL 9 case?
>
>
Hi Richard,
On Thu, Sep 28, 2023 at 6:14 PM Richard W.M. Jones
wrote:
> Ming,
>
> For some reason the build seems "stuck" at the moment, but
> if it finishes could you see if this fixes the RHEL 9 case?
>
> https://kojihub.stream.centos.org/koji/taskinfo?taskID=2879547
>
Sure, no problem, but
On Thu, Sep 28, 2023 at 04:03:33PM +0800, Ming Xie wrote:
> Yes, I reproduced the problem using rhel9 virt-v2v, because I saw that the
> customer was also using rhel9 virt-v2v (version: 2.2), I saw that you wanted
> to
> solve the problem by fixing the date of the schtask command, but I see
Ming,
For some reason the build seems "stuck" at the moment, but
if it finishes could you see if this fixes the RHEL 9 case?
https://kojihub.stream.centos.org/koji/taskinfo?taskID=2879547
Thanks,
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my
On Wed, Sep 27, 2023 at 08:46:58PM +0800, Ming Xie wrote:
> Hi Richard,
>
> Sorry, I missed the email, I found out that the ova OS used by the
> customer is win11 uefi, so I tried to reproduce the error today using
> win11-uefi guest
>
> Steps:
> 1. Convert win10-efi with UTC-8 timezone,
On Mon, Sep 25, 2023 at 01:25:06PM +0100, Daniel P. Berrangé wrote:
> On Mon, Sep 25, 2023 at 01:14:40PM +0100, Richard W.M. Jones wrote:
> > On Mon, Sep 25, 2023 at 01:09:15PM +0200, Lee Garrett wrote:
> > > On 23.09.23 19:37, Laszlo Ersek wrote:
> > > >On 9/22/23 16:47, Lee Garrett wrote:
> > >
On Mon, Sep 25, 2023 at 01:14:40PM +0100, Richard W.M. Jones wrote:
> On Mon, Sep 25, 2023 at 01:09:15PM +0200, Lee Garrett wrote:
> > On 23.09.23 19:37, Laszlo Ersek wrote:
> > >On 9/22/23 16:47, Lee Garrett wrote:
> > >>On 22.09.23 14:54, Richard W.M. Jones wrote:
> > >>>On Fri, Sep 22, 2023 at
On Mon, Sep 25, 2023 at 01:09:15PM +0200, Lee Garrett wrote:
> On 23.09.23 19:37, Laszlo Ersek wrote:
> >On 9/22/23 16:47, Lee Garrett wrote:
> >>On 22.09.23 14:54, Richard W.M. Jones wrote:
> >>>On Fri, Sep 22, 2023 at 11:40:03AM +0100, Richard W.M. Jones wrote:
> On Thu, Sep 21, 2023 at
On 23.09.23 19:37, Laszlo Ersek wrote:
On 9/22/23 16:47, Lee Garrett wrote:
On 22.09.23 14:54, Richard W.M. Jones wrote:
On Fri, Sep 22, 2023 at 11:40:03AM +0100, Richard W.M. Jones wrote:
On Thu, Sep 21, 2023 at 07:47:52PM +0200, Lee Garrett wrote:
On 21.09.23 19:43, Richard W.M. Jones
On 9/22/23 16:47, Lee Garrett wrote:
> On 22.09.23 14:54, Richard W.M. Jones wrote:
>> On Fri, Sep 22, 2023 at 11:40:03AM +0100, Richard W.M. Jones wrote:
>>> On Thu, Sep 21, 2023 at 07:47:52PM +0200, Lee Garrett wrote:
On 21.09.23 19:43, Richard W.M. Jones wrote:
> So this is probably
On Fri, Sep 22, 2023 at 05:27:25PM +0200, Lee Garrett wrote:
> On 22.09.23 16:47, Lee Garrett wrote:
> >On 22.09.23 14:54, Richard W.M. Jones wrote:
> >>On Fri, Sep 22, 2023 at 11:40:03AM +0100, Richard W.M. Jones wrote:
> >>>On Thu, Sep 21, 2023 at 07:47:52PM +0200, Lee Garrett wrote:
> On
On 22.09.23 16:47, Lee Garrett wrote:
On 22.09.23 14:54, Richard W.M. Jones wrote:
On Fri, Sep 22, 2023 at 11:40:03AM +0100, Richard W.M. Jones wrote:
On Thu, Sep 21, 2023 at 07:47:52PM +0200, Lee Garrett wrote:
On 21.09.23 19:43, Richard W.M. Jones wrote:
So this is probably another
On 22.09.23 14:54, Richard W.M. Jones wrote:
On Fri, Sep 22, 2023 at 11:40:03AM +0100, Richard W.M. Jones wrote:
On Thu, Sep 21, 2023 at 07:47:52PM +0200, Lee Garrett wrote:
On 21.09.23 19:43, Richard W.M. Jones wrote:
So this is probably another instance or variation of the timezone
On Fri, Sep 22, 2023 at 11:40:03AM +0100, Richard W.M. Jones wrote:
> On Thu, Sep 21, 2023 at 07:47:52PM +0200, Lee Garrett wrote:
> > On 21.09.23 19:43, Richard W.M. Jones wrote:
> > >So this is probably another instance or variation of the timezone
> > >formatting problem (of schtasks). Which
On Thu, Sep 21, 2023 at 07:47:52PM +0200, Lee Garrett wrote:
> On 21.09.23 19:43, Richard W.M. Jones wrote:
> >So this is probably another instance or variation of the timezone
> >formatting problem (of schtasks). Which version of virt-v2v is this?
> >I want to check that you have a version with
On 21.09.23 19:43, Richard W.M. Jones wrote:
On Thu, Sep 21, 2023 at 06:24:40PM +0200, Lee Garrett wrote:
On 21.09.23 18:08, Richard W.M. Jones wrote:
On Thu, Sep 21, 2023 at 04:50:26PM +0200, Lee Garrett wrote:
After testing it again today, the guest agent is still not
installed, however
On Thu, Sep 21, 2023 at 06:24:40PM +0200, Lee Garrett wrote:
> On 21.09.23 18:08, Richard W.M. Jones wrote:
> >On Thu, Sep 21, 2023 at 04:50:26PM +0200, Lee Garrett wrote:
> >>After testing it again today, the guest agent is still not
> >>installed, however this time the C:\Program
>
On 21.09.23 18:08, Richard W.M. Jones wrote:
On Thu, Sep 21, 2023 at 04:50:26PM +0200, Lee Garrett wrote:
After testing it again today, the guest agent is still not
installed, however this time the C:\Program
Files\Guestfs\Firstboot\log.txt exists:
starting firstboot service
running
On Thu, Sep 21, 2023 at 04:50:26PM +0200, Lee Garrett wrote:
> After testing it again today, the guest agent is still not
> installed, however this time the C:\Program
> Files\Guestfs\Firstboot\log.txt exists:
>
> starting firstboot service
> running "C:\Program
After testing it again today, the guest agent is still not installed, however
this time the C:\Program Files\Guestfs\Firstboot\log.txt exists:
starting firstboot service
running "C:\Program Files\Guestfs\Firstboot\scripts\5000-0001-wait-pnp.bat"
1 file(s) moved.
Wait for PnP to complete
If we suspect that the whole firstboot mechanism might not be working
with the new version of Windows, one way to test it (on this one, or a
freshly installed Windows VM) would be:
$ virt-customize -a windows.img --firstboot-command 'echo hello'
and see if "hello" is written in some form to
Hi,
On 11.09.23 15:13, Richard W.M. Jones wrote:
On Sun, Sep 10, 2023 at 11:34:22AM +0100, Richard W.M. Jones wrote:
This message got caught in moderation because the attachment
was large. I put the attachment here:
http://oirase.annexia.org/tmp/2023-lgarrett-virt-v2v-debug-output.txt
-
On Sun, Sep 10, 2023 at 11:34:22AM +0100, Richard W.M. Jones wrote:
> This message got caught in moderation because the attachment
> was large. I put the attachment here:
>
> http://oirase.annexia.org/tmp/2023-lgarrett-virt-v2v-debug-output.txt
>
> - Forwarded message from Lee Garrett
This message got caught in moderation because the attachment
was large. I put the attachment here:
http://oirase.annexia.org/tmp/2023-lgarrett-virt-v2v-debug-output.txt
- Forwarded message from Lee Garrett -
Date: Sun, 10 Sep 2023 00:09:17 +0200
From: Lee Garrett
To:
31 matches
Mail list logo
