Displaying 3 results from an estimated 3 matches for "44v2x".
Did you mean:
442
2020 Apr 30
2
sync guest time
...e-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
# 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 is the simplest reproducer I could come with; the original issue
is this call to libvirt's `setTIme` in [0].
Is there any workaround I could try ? Am I doing something wrong here ?
[0] - https://github.com/kubevirt/kubevirt/blo...
2020 Apr 30
0
Re: sync guest time
...ou'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...
2020 Apr 30
1
Re: sync guest time
...g
specified ?
I'm not sure if this (removing the DOMAIN_TIME_SYNC) is a fix, an ugly
hack, or a disaster waiting to happen.
>
> > # 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 j...