qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [Qemu-devel] Host clock broke loadvm
@ 2009-10-07 21:52 Juan Quintela
  2009-10-08  9:31 ` [Qemu-devel] " Jan Kiszka
  0 siblings, 1 reply; 2+ messages in thread
From: Juan Quintela @ 2009-10-07 21:52 UTC (permalink / raw)
  To: Jan Kiszka, qemu-devel


Hi Jan

Today I found that I am not able to load anymore old saved images (old
means more than 2 days old).  Problem is with host clock.

I need to run qemu with -rtc clock=vm, and then things cames to work
again.

My suspicion is that the saved timers are based from cpu_clock_offset,
and when we run now with host_clock, that value don't exist.

If I don't use -rtc clock=vm, machines will come eventually to life, but
it will take several minutes.

Anthony asked to change pc-11 definition to use vm clock.  What do you
think?  Any other good idea to make a machine saved with clock=vm to
load with clock=host.

I tried the trial:

if (cpu_clock_offset != 0)
   rtc_clock = vm_clock;

after loading an image, but that didn't fixed the problem (I didn't
investigate more).

Do you have a plan to go from here?

Later, Juan.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Qemu-devel] Re: Host clock broke loadvm
  2009-10-07 21:52 [Qemu-devel] Host clock broke loadvm Juan Quintela
@ 2009-10-08  9:31 ` Jan Kiszka
  0 siblings, 0 replies; 2+ messages in thread
From: Jan Kiszka @ 2009-10-08  9:31 UTC (permalink / raw)
  To: Juan Quintela; +Cc: qemu-devel@nongnu.org

Juan Quintela wrote:
> Hi Jan
> 
> Today I found that I am not able to load anymore old saved images (old
> means more than 2 days old).  Problem is with host clock.
> 
> I need to run qemu with -rtc clock=vm, and then things cames to work
> again.
> 
> My suspicion is that the saved timers are based from cpu_clock_offset,
> and when we run now with host_clock, that value don't exist.
> 
> If I don't use -rtc clock=vm, machines will come eventually to life, but
> it will take several minutes.

That makes sense as you cannot simply migrate timers between clocks (in
this case, you would have to patch the timeout value of the rtc timer
after resume).

> 
> Anthony asked to change pc-11 definition to use vm clock.  What do you
> think?

Definitely makes sense, also for other reasons unrelated to save/restore.

>  Any other good idea to make a machine saved with clock=vm to
> load with clock=host.
> 
> I tried the trial:
> 
> if (cpu_clock_offset != 0)
>    rtc_clock = vm_clock;
> 
> after loading an image, but that didn't fixed the problem (I didn't
> investigate more).
> 
> Do you have a plan to go from here?

I would say, first go for clock=vm for pc-11. Until someone comes up
with a good reason to migrate from clock=vm to clock=host, don't try to
be smarter than required.

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2009-10-08  9:31 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-10-07 21:52 [Qemu-devel] Host clock broke loadvm Juan Quintela
2009-10-08  9:31 ` [Qemu-devel] " Jan Kiszka

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).