qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Pavel Dovgalyuk" <dovgaluk@ispras.ru>
To: 'Ciro Santilli' <ciro.santilli@gmail.com>
Cc: "'Pavel Dovgalyuk'" <Pavel.Dovgaluk@ispras.ru>,
	qemu-devel@nongnu.org, kwolf@redhat.com,
	"'Peter Maydell'" <peter.maydell@linaro.org>,
	war2jordan@live.com, "'Igor R'" <boost.lists@gmail.com>,
	quintela@redhat.com, jasowang@redhat.com, mst@redhat.com,
	"'Aleksandr Bezzubikov'" <zuban32s@gmail.com>,
	maria.klimushenkova@ispras.ru, kraxel@redhat.com,
	"'Thomas Dullien'" <thomas.dullien@googlemail.com>,
	pbonzini@redhat.com, "'Alex Bennée'" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] [RFC PATCH v6 00/20] replay additions
Date: Mon, 12 Feb 2018 08:47:46 +0300	[thread overview]
Message-ID: <001b01d3a3c5$032e09f0$098a1dd0$@ru> (raw)
In-Reply-To: <CAFXrp_dUAZDYLUTqY0nxbGg7w4TEqD2+rNRPT+47a0B8N1Y6Aw@mail.gmail.com>

I tested ARM only with –kernel and –initrd.

Can you provide the full command line and the disk image?

 

Pavel Dovgalyuk

 

From: Ciro Santilli [mailto:ciro.santilli@gmail.com] 
Sent: Saturday, February 10, 2018 3:09 AM
To: Pavel Dovgalyuk
Cc: Pavel Dovgalyuk; qemu-devel@nongnu.org; kwolf@redhat.com; Peter Maydell; war2jordan@live.com; Igor R; quintela@redhat.com; jasowang@redhat.com; mst@redhat.com; Aleksandr Bezzubikov; maria.klimushenkova@ispras.ru; kraxel@redhat.com; Thomas Dullien; pbonzini@redhat.com; Alex Bennée
Subject: Re: [RFC PATCH v6 00/20] replay additions

 

Also, what command do you use to test on ARM? I'm a bit stuck to get the drive part right, e.g.:

 

-drive file=./buildroot/output.arm~/images/rootfs.ext2,if=scsi,id=img-direct,format=raw \

-drive driver=blkreplay,if=none,image=img-direct,id=img-blkreplay \

-device scsi-hd,drive=img-blkreplay \

 

fails with: qemu-system-arm: -device scsi-hd,drive=img-blkreplay: Conflicts with use by img-direct as 'root', which does not allow 'write' on #block968

 

  reply	other threads:[~2018-02-12  5:47 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-07 12:03 [Qemu-devel] [RFC PATCH v6 00/20] replay additions Pavel Dovgalyuk
2018-02-07 12:03 ` [Qemu-devel] [RFC PATCH v6 01/20] cpu-exec: fix exception_index handling Pavel Dovgalyuk
2018-02-07 12:04 ` [Qemu-devel] [RFC PATCH v6 02/20] block: implement bdrv_snapshot_goto for blkreplay Pavel Dovgalyuk
2018-02-07 12:04 ` [Qemu-devel] [RFC PATCH v6 03/20] blkreplay: create temporary overlay for underlaying devices Pavel Dovgalyuk
2018-02-07 12:04 ` [Qemu-devel] [RFC PATCH v6 04/20] replay: disable default snapshot for record/replay Pavel Dovgalyuk
2018-02-07 12:04 ` [Qemu-devel] [RFC PATCH v6 05/20] replay: fix processing async events Pavel Dovgalyuk
2018-02-07 12:04 ` [Qemu-devel] [RFC PATCH v6 06/20] replay: fixed replay_enable_events Pavel Dovgalyuk
2018-02-07 12:04 ` [Qemu-devel] [RFC PATCH v6 07/20] replay: fix save/load vm for non-empty queue Pavel Dovgalyuk
2018-02-07 12:04 ` [Qemu-devel] [RFC PATCH v6 08/20] replay: added replay log format description Pavel Dovgalyuk
2018-02-07 12:04 ` [Qemu-devel] [RFC PATCH v6 09/20] replay: save prior value of the host clock Pavel Dovgalyuk
2018-02-07 12:04 ` [Qemu-devel] [RFC PATCH v6 10/20] replay/replay.c: bump REPLAY_VERSION again Pavel Dovgalyuk
2018-02-07 12:04 ` [Qemu-devel] [RFC PATCH v6 11/20] replay/replay-internal.c: track holding of replay_lock Pavel Dovgalyuk
2018-02-07 12:05 ` [Qemu-devel] [RFC PATCH v6 12/20] replay: make locking visible outside replay code Pavel Dovgalyuk
2018-02-07 12:05 ` [Qemu-devel] [RFC PATCH v6 13/20] replay: push replay_mutex_lock up the call tree Pavel Dovgalyuk
2018-02-07 12:05 ` [Qemu-devel] [RFC PATCH v6 14/20] replay: don't destroy mutex at exit Pavel Dovgalyuk
2018-02-07 12:05 ` [Qemu-devel] [RFC PATCH v6 15/20] replay: check return values of fwrite Pavel Dovgalyuk
2018-02-07 12:05 ` [Qemu-devel] [RFC PATCH v6 16/20] replay: avoid recursive call of checkpoints Pavel Dovgalyuk
2018-02-07 12:05 ` [Qemu-devel] [RFC PATCH v6 17/20] scripts/replay-dump.py: replay log dumper Pavel Dovgalyuk
2018-02-07 12:05 ` [Qemu-devel] [RFC PATCH v6 18/20] replay: don't process async events when warping the clock Pavel Dovgalyuk
2018-02-07 12:05 ` [Qemu-devel] [RFC PATCH v6 19/20] replay: save vmstate of the asynchronous events Pavel Dovgalyuk
2018-02-07 12:05 ` [Qemu-devel] [RFC PATCH v6 20/20] replay: don't drain/flush bdrv queue while RR is working Pavel Dovgalyuk
2018-02-07 12:15 ` [Qemu-devel] [RFC PATCH v6 00/20] replay additions Ciro Santilli
2018-02-07 12:38   ` Pavel Dovgalyuk
2018-02-08  7:35     ` Ciro Santilli
2018-02-10  0:09       ` Ciro Santilli
2018-02-12  5:47         ` Pavel Dovgalyuk [this message]
2018-02-13  5:58           ` Ciro Santilli
2018-02-13  6:50             ` Pavel Dovgalyuk
2018-02-13  9:07               ` Ciro Santilli
2018-02-13  9:58                 ` Pavel Dovgalyuk
2018-02-13 10:26                   ` Pavel Dovgalyuk
2018-02-13 10:49                     ` Peter Maydell
2018-02-13 10:52                       ` Pavel Dovgalyuk
2018-02-13 11:37                         ` Ciro Santilli
2018-02-13 12:13                           ` Pavel Dovgalyuk
2018-02-14 12:39                       ` Pavel Dovgalyuk
2018-02-19  8:02                         ` Pavel Dovgalyuk
2018-02-19 11:15                           ` Ciro Santilli
2018-02-20  9:46                             ` Pavel Dovgalyuk
2018-02-20 23:59                               ` Ciro Santilli
2018-02-21  6:41                                 ` Pavel Dovgalyuk
2018-02-21 22:40                                   ` Ciro Santilli
2018-02-22  7:06                                     ` Pavel Dovgalyuk
2018-02-22  7:10                                       ` Pavel Dovgalyuk
2018-02-22 17:52                                         ` Ciro Santilli
2018-02-12  6:53       ` Pavel Dovgalyuk
2018-02-14  6:21     ` Ciro Santilli
2018-02-14  9:20       ` Pavel Dovgalyuk
2018-02-07 13:38 ` no-reply

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='001b01d3a3c5$032e09f0$098a1dd0$@ru' \
    --to=dovgaluk@ispras.ru \
    --cc=Pavel.Dovgaluk@ispras.ru \
    --cc=alex.bennee@linaro.org \
    --cc=boost.lists@gmail.com \
    --cc=ciro.santilli@gmail.com \
    --cc=jasowang@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=maria.klimushenkova@ispras.ru \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=thomas.dullien@googlemail.com \
    --cc=war2jordan@live.com \
    --cc=zuban32s@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 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).