On 06/26/2013 05:27 AM, Ján ONDREJ (SAL) wrote:
Hello,
On Tue, Jun 25, 2013 at 03:17:06PM -0400, Jamie Fargen wrote:
> On Tue, Jun 25, 2013 at 3:01 PM, Cole Robinson <crobinso(a)redhat.com> wrote:
>
>> On 06/24/2013 02:18 PM, Ján ONDREJ (SAL) wrote:
>> Maybe try altering the guest config with:
>>
>> <clock offset='utc'>
>> <timer name='pit' tickpolicy='delay'/>
>> <timer name='rtc' tickpolicy='catchup'/>
>> </clock>
I have to test it longer time on multiple machines, but I still see clock
skew between -3s to +0.5s in my guest. I have no time guest time
synchronization now (NTPd and timeserver are turned off in windows).
Can I have exact time in windows? Testing on windows 2008R2.
>>
https://bugs.launchpad.net/nova/+bug/1011848
>>
https://bugzilla.redhat.com/show_bug.cgi?id=828332
>>
>> virt-manager/virt-install should be doing this by default.
This is still not default in Fedora 18. My packages:
virt-manager-0.9.5-1.fc18.noarch
libvirt-0.10.2.6-1.fc18.x86_64
Sorry, that sentence was meant to read like: 'virt-manager/virt-install does
not currently set that XML, but it should be.'
Byt, my settings are deprecated. In qemu log I see:
Warning: option deprecated, use lost_tick_policy property of kvm-pit instead.
Hmm. Can you file a fedora libvirt bug with your guest XML, and the contents
of /var/log/libvirt/qemu/$vmname.log ?
Thanks,
Cole