All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Sergei Lyubski <slyubski@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: The question about migration/checkpointing
Date: Mon, 29 Jul 2024 09:58:45 +0100	[thread overview]
Message-ID: <877cd41smy.fsf@draig.linaro.org> (raw)
In-Reply-To: <CAMLUMH6dRAg+s9jzfVg3ihbE42yO1PssYLnKm-o99aEkpD8QyQ@mail.gmail.com> (Sergei Lyubski's message of "Fri, 26 Jul 2024 12:41:47 -0700")

Sergei Lyubski <slyubski@gmail.com> writes:

>   Hi guys,
>
> My name is Sergey. My company uses QEMU for  CPU performance simulation/evaluaton.
> Sorry, I found  your emails in QEMU  relatively recent commits  into ram.c .  Why ram.c . Because I see some weirdness in
> the  behavior.
>   
> Our goal is :
>      a)  To boot  Linux , to launch some  TEST/SPEC, to drop a few checkpoints.
>      b)  To resume  execution from  those checkpoints, to attach a performance simulator and
>            to evaluate performance at the "hot" code  areas.
>
>   How we tried to do it .
>
>      a) run QEMU with -monitor telnet options
>      b) connect  to QEMU with telnet 
>      c)  after  LINUX  booted  in  QEMU monitor (telnet)  executed
>             migrate -d file://<FULL  CKPT PATH> 
>             quit
>       d)  run QEMU  with option -incoming file://<FULL CKPT PATH>
>
>   Now !!
>
>   If  I  drop the checkpoint  when running  on linux a long ( endless) test which  prints on      the console,  everything works (!)
>  and  the console is properly restored.
>    
>   When I drop  the checkpoint  when the linux console is in shell  prompt, the restoration does  not  work.
>    I see either error message  from  ram_load_precopy()
>        error_report("Unknown combination of migration flags: 0x%x",
>   flags);

I suspect seeing the value of flags will help with any diagnosis.

>
>        or
>
>    the console is locked, QEMU restarts and  runs  (ps, top).   The only  solution is to kill 
>    QEMU .  After that,  QEMU console is distorted and requires to type
>    RESET.

Are you able to attach with gdb and get a backtrace?

>
>     Could you please comment on the above issues. 
>     If you need more info I can send you my screen shots.
>     Please note that  that the similar behavior is observed on  both
>      qemu 9.0  ( stable-9.0)  and
>      qemu 8.x
>
> Thanks in advance.
> Sergey Lyubskiy

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


      reply	other threads:[~2024-07-29  8:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-26 19:41 The question about migration/checkpointing Sergei Lyubski
2024-07-29  8:58 ` Alex Bennée [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877cd41smy.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=slyubski@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.