Eran Rom il.ibm.com> writes:
> > When Host and Guest ran 2.6.27 with kvm-87 (both qemu-kvm and kvm-kmod), the
> > problem persisted. Thus, I am looking for a kernel fix that is not
> part of KVM,
> > any lead? Am confined to use 2.6.27
> Marcelo Tosatti wrote on 16/07/2009 01:19:40:
> Is it an
Glauber Costa redhat.com> writes:
>
> > This was happening with kvmclock back then when it did not handle
> > cpu frequency changes. What are the details of the host hw?
> >
> > Glauber, any clues?
> maybe it is exactly that. 2.6.27 is a little bit old, and probably does not
> have the fixes.
>
Glauber Costa redhat.com> writes:
> > This was happening with kvmclock back then when it did not handle
> > cpu frequency changes. What are the details of the host hw?
> >
> > Glauber, any clues?
> maybe it is exactly that. 2.6.27 is a little bit old, and probably does not
> have the fixes.
>
W
On Tue, Jul 07, 2009 at 05:12:16PM -0300, Marcelo Tosatti wrote:
> On Tue, Jul 07, 2009 at 09:58:46AM +, Eran Rom wrote:
> > Eran Rom il.ibm.com> writes:
> >
> > >
> > > Eran Rom il.ibm.com> writes:
> > >
> > > Still getting a misbehaving clock:
> > > guest uses kvmclock with kernel 2.6.27
On Tue, Jul 07, 2009 at 09:58:46AM +, Eran Rom wrote:
> Eran Rom il.ibm.com> writes:
>
> >
> > Eran Rom il.ibm.com> writes:
> >
> > Still getting a misbehaving clock:
> > guest uses kvmclock with kernel 2.6.27
> > host kernel is 2.6.27 with kvm-qemu-87 & kvm-kmod-87
> >
> > getting:
> > .
Eran Rom il.ibm.com> writes:
>
> Eran Rom il.ibm.com> writes:
>
> Still getting a misbehaving clock:
> guest uses kvmclock with kernel 2.6.27
> host kernel is 2.6.27 with kvm-qemu-87 & kvm-kmod-87
>
> getting:
> ...
> now = 2128043797
> now = 2138048010
> now = 1
Eran Rom il.ibm.com> writes:
>
> Avi Kivity redhat.com> writes:
>
> > 2.6.27 has kvmclock.
> >
> Thanks a lot!
> Will try the kvmclock
> Eran
>
Still getting a misbehaving clock:
guest uses kvmclock with kernel 2.6.27
host kernel is 2.6.27 with kvm-qemu-87 & kvm-kmod-87
doing:
now = gettim
Avi Kivity redhat.com> writes:
> 2.6.27 has kvmclock.
>
Thanks a lot!
Will try the kvmclock
Eran
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On 06/29/2009 10:11 PM, Eran Rom wrote:
Nevertheless, the tsc clock is not reliable,
the host can scale it, or
go into
deep sleep state.
indeed my current clock source is tsc
You won't get accurate timing with tsc.
So either use newer kernel with kvmclock (pv)
or change the clock
Dor Laor redhat.com> writes:
>
> On 06/25/2009 04:25 PM, Eran Rom wrote:
> > Behavior:
> > Running a code doing:
> > t1 = gettimeofday
> > t2 = gettimeofday
> > while t2-t1< 5 minutes {
> > sleep(1)
> > t2 = gettimeofday
> > }
> >
> > Ran it 10 times, each time in a 'newly launched' V
On 06/25/2009 04:25 PM, Eran Rom wrote:
Hi All,
Am a newbie (to kvm, linux kernel, git, etc.) so apologize in advance for
missing/inaccurate info.
I am experiencing inconsistent behavior of guest gettimeofday, described below.
I have seen prior reference to the problem, however, it was not clear
On 06/25/2009 04:25 PM, Eran Rom wrote:
Hi All,
Am a newbie (to kvm, linux kernel, git, etc.) so apologize in advance for
missing/inaccurate info.
I am experiencing inconsistent behavior of guest gettimeofday, described below.
I have seen prior reference to the problem, however, it was not clear
Hi All,
Am a newbie (to kvm, linux kernel, git, etc.) so apologize in advance for
missing/inaccurate info.
I am experiencing inconsistent behavior of guest gettimeofday, described below.
I have seen prior reference to the problem, however, it was not clear whether
the issue was solved or not and wh
13 matches
Mail list logo
