From debbugs-submit-bounces@debbugs.gnu.org Sat Mar 21 12:44:11 2020 Received: (at 34276) by debbugs.gnu.org; 21 Mar 2020 16:44:11 +0000 Received: from localhost ([127.0.0.1]:47897 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jFhEJ-00071j-Az for submit@debbugs.gnu.org; Sat, 21 Mar 2020 12:44:11 -0400 Received: from relay8-d.mail.gandi.net ([217.70.183.201]:45585) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jFhEG-00071Q-Rx for 34276@debbugs.gnu.org; Sat, 21 Mar 2020 12:44:09 -0400 Received: from webmail.gandi.net (webmail18.sd4.0x35.net [10.200.201.18]) (Authenticated sender: brice@waegenei.re) by relay8-d.mail.gandi.net (Postfix) with ESMTPA id 671C61BF20B; Sat, 21 Mar 2020 16:44:02 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Sat, 21 Mar 2020 16:44:02 +0000 From: Brice Waegeneire To: =?UTF-8?Q?Ludovic_Court=C3=A8s?= Subject: =?UTF-8?Q?Re=3A_bug=2334276=3A_=E2=80=98guix_system_disk-im_age?= =?UTF-8?Q?=E2=80=99_successfully_builds_a_bad_image?= In-Reply-To: <875zex1z05.fsf@gnu.org> References: <877eejfqmb.fsf@nckx> <7a36cb1fc7c68f5d63a324df49170cdc@waegenei.re> <875zex1z05.fsf@gnu.org> Message-ID: X-Sender: brice@waegenei.re User-Agent: Roundcube Webmail/1.3.8 X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 34276 Cc: 34276@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) Hello Ludo, On 2020-03-21 15:58, Ludovic Courtès wrote: > Any idea how to implement it? Is QMP a request/reply kind of interface > like the monitor? Not really or I would have sent a patch instead. QMP is similar to the the monitor in the sense that you can send a command and receive a reply but it give us access to more features; in our case asynchronous events. To get notified by the pvpanic device that a panic occured on the guest it is needed to do the following: 1. Connect to the socket 2. Receive the server greetings 3. Respond with the capabilites request 4. Receive the capabilites respond 5. Listen on GUEST_PANICKED events The QMP specifications are available here[0]. [0]: https://git.qemu.org/?p=qemu.git;a=blob_plain;f=docs/interop/qmp-spec.txt;hb=HEAD Brice.