yes, the full options on clock is '-rtc driftfix=slew,clock=rt,base=localtime'
zhong...@sangfor.com.cn
From: Paolo Bonzini
Date: 2016-09-20 16:17
To: zhong...@sangfor.com.cn; qemu-devel
CC: Michael S. Tsirkin
Subject: Re: [PATCH]MC146818 RTC: coordinate guest clock base to destina
mem-merge=off \
-post win2008x64_Sangfor123clone
---
> On 20/09/2016 09:19, zhong...@sangfor.com.cn wrote:
> > qemu tracks guest time based on vector [base_rtc, last_update], in which
> > last_update stands for a monotonic tick which is actually uptime of the
> host.
>
> But last_
tc.
Thinks!
the model disrupted.
yes, approach we choose looks a little tediously long. but we'll gain in the
future, when we trying to improve
zhong...@sangfor.com.cn
From: Paolo Bonzini
Date: 2016-09-20 21:12
To: zhong...@sangfor.com.cn; qemu-devel
CC: Michael S. Tsirkin
Subject: Re:
;
-if (version_id <= 2) {
+if (rtc_clock == QEMU_CLOCK_REALTIME || version_id <= 2) {
rtc_set_time(s);
s->offset = 0;
check_update_timer(s);
---
Could you send me the complete patch?
zhong...@sangfor.com.cn
From: zhong...@sangfor.com.cn
Date: 2016-09-21
Yes, it's also work.
So you prefer the latter?
zhong...@sangfor.com.cn
From: Paolo Bonzini
Date: 2016-12-16 18:10
To: Junlian Bell
CC: qemu-devel
Subject: Re: [PATCH 1/1] scsi-disk: passthrough VERIFY command
On 16/12/2016 08:55, Junlian Bell wrote:
> When a scsi-disk object
Thanks again, sincerely.
zhong...@sangfor.com.cn
From: Paolo Bonzini
Date: 2016-09-21 23:15
To: zhong...@sangfor.com.cn; qemu-devel
CC: Michael S. Tsirkin
Subject: Re: [PATCH]MC146818 RTC: coordinate guest clock base to destination
host after migration
On 21/09/2016 09:36, zhong...@sang
Hi, Paolo
This is a simplified patch according to your advice. Would you please reiview
it again.
separation
line
MC146818 RTC: coordinate guest clock base to destination host after migration
qemu tracks guest ti
Hi, Paolo
This is another patch arround RTC. Would you please have a review.
--separation-
MC146818 RTC: Get correct guest time when irq coalesced
When irq coalesce occurred, irq_coalesced actually store the seconds
that the time sa
MC146818 RTC: coordinate guest clock base to destination host after migration
qemu tracks guest time based on vector [base_rtc, last_update], in which
last_update stands for a monotonic tick which is actually uptime of the host.
according to rtc implementation codes of recent releases and upstream
MC146818 RTC: coordinate guest clock base to destination host after migration
qemu tracks guest time based on vector [base_rtc, last_update], in which
last_update stands for a monotonic tick which is actually uptime of the host.
according to rtc implementation codes of recent releases and upstream
>No, it's not seconds. It depends on the interval of the periodic interrupt.
>
>In any case this approach is not acceptable, unfortunately; it causes
>the time to go backwards for the guest as soon as an interrupt is coalesced.
>
>What is the guest that you're seeing issues with?
Yes, it's leng
11 matches
Mail list logo
