[prev in list] [next in list] [prev in thread] [next in thread]
List: libguestfs
Subject: Re: [Libguestfs] [PATCH v2v 0/5] convert: Find out if Windows guest is expecting BIOS localtime or U
From: Alice Frosi <afrosi () redhat ! com>
Date: 2023-09-26 8:33:22
Message-ID: CABBoX7Mhv9qbdCywvd=J9oX5GAkN8H0j5W=4VxyD_C=Dm-f3vA () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Mon, Sep 25, 2023 at 5:19 PM Daniel P. Berrangé <berrange@redhat.com>
wrote:
> On Mon, Sep 25, 2023 at 04:26:59PM +0200, Alice Frosi wrote:
> > Hi Rich,
> >
> > On Mon, Sep 25, 2023 at 4:10 PM Richard W.M. Jones <rjones@redhat.com>
> > wrote:
> >
> > > [Alice: See patch 2]
> > >
> >
> > I'm not 100% sure about the source of this work. However, we had in
> > KubeVirt people interested in using localtime with Windows [1]. Yes, I
> see
> > that you pointed to that PR in patch 2. The problem with that PR is the
> > migration. What happens if we migrate the VM to a host that is in another
> > timezone? Is it going to break the application running inside the VM?
>
> I would generally expect all hosts to be configured in the same timezone,
> for any given single cloud deployment.
>
> If you really are concerned about this problem though, libvirt lets you
> set this explicitly eg
>
> <clock offset='localtime' timezone='Europe/London'/>
>
>
I don't think we support this option in KubeVirt yet. It might be useful to
extend it. However, I'm not sure if it is the user's responsibility to
choose the TZ or if it should be decided by KubeVirt and not exposed to the
API.
Generally, I don't think we can always assume that all the node in the
cluster are in the same time zone. This could be signaled with some labels
and allow the VM to be scheduled only on the node with that label.
> With regards,
> Daniel
> --
> |: https://berrange.com -o-
> https://www.flickr.com/photos/dberrange :|
> |: https://libvirt.org -o-
> https://fstop138.berrange.com :|
> |: https://entangle-photo.org -o-
> https://www.instagram.com/dberrange :|
>
>
[Attachment #5 (text/html)]
<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Mon, Sep 25, 2023 at 5:19 PM Daniel P. Berrangé <<a \
href="mailto:berrange@redhat.com">berrange@redhat.com</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Mon, Sep 25, 2023 \
at 04:26:59PM +0200, Alice Frosi wrote:<br> > Hi Rich,<br>
> <br>
> On Mon, Sep 25, 2023 at 4:10 PM Richard W.M. Jones <<a \
href="mailto:rjones@redhat.com" target="_blank">rjones@redhat.com</a>><br> > \
wrote:<br> > <br>
> > [Alice: See patch 2]<br>
> ><br>
> <br>
> I'm not 100% sure about the source of this work. However, we had in<br>
> KubeVirt people interested in using localtime with Windows [1]. Yes, I see<br>
> that you pointed to that PR in patch 2. The problem with that PR is the<br>
> migration. What happens if we migrate the VM to a host that is in another<br>
> timezone? Is it going to break the application running inside the VM?<br>
<br>
I would generally expect all hosts to be configured in the same timezone,<br>
for any given single cloud deployment.<br>
<br>
If you really are concerned about this problem though, libvirt lets you<br>
set this explicitly eg<br>
<br>
<clock offset='localtime' timezone='Europe/London'/><br>
<br></blockquote><div><br></div><div>I don't think we support this option in \
KubeVirt yet. It might be useful to extend it. However, I'm not sure if it is the \
user's responsibility to choose the TZ or if it should be decided by KubeVirt and \
not exposed to the API.</div><div><br></div><div>Generally, I don't think we can \
always assume that all the node in the cluster are in the same time zone. This could \
be signaled with some labels and allow the VM to be scheduled only on the node with \
that label.</div><div> <br></div><blockquote class="gmail_quote" style="margin:0px \
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> With \
regards,<br> Daniel<br>
-- <br>
> > <a href="https://berrange.com" rel="noreferrer" \
> > target="_blank">https://berrange.com</a> -o- <a \
> > href="https://www.flickr.com/photos/dberrange" rel="noreferrer" \
> > target="_blank">https://www.flickr.com/photos/dberrange</a> :|<br>
> > <a href="https://libvirt.org" rel="noreferrer" \
> > target="_blank">https://libvirt.org</a> -o- <a \
> > href="https://fstop138.berrange.com" rel="noreferrer" \
> > target="_blank">https://fstop138.berrange.com</a> :|<br>
> > <a href="https://entangle-photo.org" rel="noreferrer" \
> > target="_blank">https://entangle-photo.org</a> -o- <a \
> > href="https://www.instagram.com/dberrange" rel="noreferrer" \
> > target="_blank">https://www.instagram.com/dberrange</a> :|<br>
<br>
</blockquote></div></div>
_______________________________________________
Libguestfs mailing list
Libguestfs@redhat.com
https://listman.redhat.com/mailman/listinfo/libguestfs
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic