[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: sync guest time

From: Daniel P . Berrangé
Subject: Re: sync guest time
Date: Thu, 30 Apr 2020 13:15:20 +0100
User-agent: Mutt/1.13.3 (2020-01-12)

On Thu, Apr 30, 2020 at 01:52:12PM +0200, Miguel Duarte de Mora Barroso wrote:
> Hi,
> I'm seeing the following issue when attempting to update the guest's
> clock on a running fc32 guest (using guest agent):
> ```
> [root@virt-launcher-vmi-masquerade-mh2xm /]# virsh domtime 1 --pretty
> Time: 2020-04-30 23:27:29
> [root@virt-launcher-vmi-masquerade-mh2xm /]# virsh domtime 1 --sync
> error: internal error: unable to execute QEMU agent command
> 'guest-set-time': hwclock failed to set hardware clock to system time

This error is ultimately coming from the QEMU guest agent inside
your guest. It spawns "hwclock" and this is failing for some reason.
You'll probably need to debug this inside the guest - strace the
QEMU guest agent, see where it fails, and then file a bug against
the distro for it.

> # now, this one works.
> [root@virt-launcher-vmi-masquerade-mh2xm /]# virsh domtime 1 --now
> [root@virt-launcher-vmi-masquerade-44v2x /]# virsh domtime 1 --pretty
> Time: 2020-04-30 11:15:45

This doesn't run hwclock as its merely reading the current time,.

> Is there any workaround I could try ? Am I doing something wrong here ?

I don't think you're doing anything wrong. This just looks like a guest
OS bug to me.

|: 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 :|

reply via email to

[Prev in Thread] Current Thread [Next in Thread]