After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 722293 - Recommended default clock/timer settings
Recommended default clock/timer settings
Status: RESOLVED FIXED
Product: gnome-boxes
Classification: Applications
Component: general
unspecified
Other Linux
: Normal normal
: 3.22
Assigned To: GNOME Boxes maintainer(s)
GNOME Boxes maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-01-15 20:11 UTC by Cole Robinson
Modified: 2016-03-31 13:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Cole Robinson 2014-01-15 20:11:30 UTC 
Recently I had an internal discussion with several qemu developers about default VM clock/timer configuration. What they recommended maps to this libvirt XML:

  <clock ...>
    <timer name="rtc" tickpolicy="catchup"/>
    <timer name="pit" tickpolicy="delay"/>
    <timer name="hpet" present="no"/>
  </clock>

This maps to the qemu command line options:

  -rtc driftfix=slew -no-hpet -no-kvm-pit-reinjection

Explicitly this was recommended for all guest OS. Some bits don't affect certain OS, but in those cases they are harmless.

It looks like gnome-boxes is adding the first two bits, but not the hpet disabling.
Comment 1 Zeeshan Ali 2014-01-16 14:33:42 UTC 
This will need new api in libvirt-glib.
Comment 2 Christophe Fergeau 2014-01-16 15:34:09 UTC 
I've implemented the libvirt-glib API at https://bugzilla.gnome.org/show_bug.cgi?id=722293
Waiting until my pending libvirt-glib patches get a review before sending more patches to the libvirt ML (hint ;)
Comment 3 Zeeshan Ali 2014-01-16 16:10:54 UTC 
(In reply to comment #2)
> I've implemented the libvirt-glib API at
> https://bugzilla.gnome.org/show_bug.cgi?id=722293
> Waiting until my pending libvirt-glib patches get a review before sending more
> patches to the libvirt ML (hint ;)

Cool, you are awesome even if you paste the wrong link. :) I should look into your patches.
Comment 5 Zeeshan Ali 2014-10-17 00:40:46 UTC 
Christophe so I understand all needed API is now merged?
Comment 6 Zeeshan Ali 2014-10-17 00:43:06 UTC 
(In reply to comment #5)
> Christophe so I understand all needed API is now merged?

NM, yes all api seems to be in place. Thanks!
Comment 7 Zeeshan Ali 2014-10-17 17:51:01 UTC 
Cole, Any idea if this will solve bug#724616 as well?
Comment 8 Zeeshan Ali 2014-10-17 17:56:48 UTC 
(In reply to comment #7)
> Cole, Any idea if this will solve bug#724616 as well?

NM again. These bugs are very much unrelated.