From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47190) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1el7zk-0005sZ-Vn for qemu-devel@nongnu.org; Mon, 12 Feb 2018 01:53:46 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1el7zg-00014s-Un for qemu-devel@nongnu.org; Mon, 12 Feb 2018 01:53:45 -0500 Received: from mail.ispras.ru ([83.149.199.45]:50752) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1el7zg-00012u-Lv for qemu-devel@nongnu.org; Mon, 12 Feb 2018 01:53:40 -0500 From: "Pavel Dovgalyuk" References: <20180207120353.5389.54531.stgit@pasha-VirtualBox> <002401d3a010$8d551280$a7ff3780$@ru> In-Reply-To: Date: Mon, 12 Feb 2018 09:53:37 +0300 Message-ID: <002601d3a3ce$35aee080$a10ca180$@ru> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Content-Language: ru Subject: Re: [Qemu-devel] [RFC PATCH v6 00/20] replay additions List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: 'Ciro Santilli' 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, =?UTF-8?Q?'Alex_Benn=C3=A9e'?= > From: Ciro Santilli [mailto:ciro.santilli@gmail.com]=20 > Awesome! This worked with my test procedure described at: = https://stackoverflow.com/questions/46970215/how-to-use-qemus-determinist= ic-record-and-replay-feature-for-a-linux-kernel-boo > While we are a it, can we clarify the following points the docs? > 1) Usage of the record/replay: mentions that `-net none` is required, = unless a network patch is applied. > But the network section that follows explains how to record network = requests, and I've tested it, so I think the `-net none` / patch = requirement is just outdated and should be removed. > 2) There are mentions of "reverse execution" and "reverse debugging" = on the "Record/replay" section. > Are those supported? If yes, explain there how to use them. Otherwise, = remove the mentions. > I would love to see that feature! Not yet, but they are the next to apply after this series. I'll update the docs. > 3) Is the snapshot feature mentioned in the "Snapshotting" section = something specific to record and replay? > If yes, can we detail further how to use it besides passing = `rrsnapshot=3Dsnapshot_name`? How to create and restore the snapshots? > If not, why does the `rrsnapshot=3Dsnapshot_name` option exist? > 4) Maybe give the required disk and network commands under "Usage of = the record/replay:" > -drive file=3Ddisk.qcow,if=3Dnone,id=3Dimg-direct > -drive = driver=3Dblkreplay,if=3Dnone,image=3Dimg-direct,id=3Dimg-blkreplay > -device ide-hd,drive=3Dimg-blkreplay > -netdev user,id=3Dnet1 -device rtl8139,netdev=3Dnet1 > -object filter-replay,id=3Dreplay,netdev=3Dnet1 > People likely always want those, but it currently requires reading = through the whole doc file to put everything together. Thanks for reviewing, I'll add the documentation update to the series. Pavel Dovgalyuk