From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29426 invoked by alias); 28 Sep 2016 15:18:17 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 29415 invoked by uid 89); 28 Sep 2016 15:18:17 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-4.7 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy= X-HELO: mx5.ptsecurity.com Received: from mx5.ptsecurity.com (HELO mx5.ptsecurity.com) (45.58.112.35) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 28 Sep 2016 15:18:16 +0000 Received: from dc1-mail-01.ptsecurity.ru (10.0.52.111) by ny-mx-01.ptsecurity.ru (10.6.20.6) with Microsoft SMTP Server (TLS) id 15.1.466.34; Wed, 28 Sep 2016 18:18:14 +0300 Received: from [10.0.72.136] (10.0.72.136) by dc1-mail-01.ptsecurity.ru (10.0.52.111) with Microsoft SMTP Server (TLS) id 15.1.466.34; Wed, 28 Sep 2016 18:18:12 +0300 Subject: Re: Custom core file To: Jan Kratochvil References: <20160928145850.GA20365@host1.jankratochvil.net> CC: From: Nikolay Martyanov Message-ID: Date: Wed, 28 Sep 2016 15:18:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160928145850.GA20365@host1.jankratochvil.net> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-ClientProxiedBy: dc1-mail-01.ptsecurity.ru (10.0.52.111) To dc1-mail-01.ptsecurity.ru (10.0.52.111) X-SW-Source: 2016-09/txt/msg00069.txt.bz2 On 09/28/2016 05:58 PM, Jan Kratochvil wrote: > On Wed, 28 Sep 2016 15:31:12 +0200, Nikolay Martyanov wrote: >> I have a self-written bare-metal hypervisor for x86 arch and I'd like to >> perform postmortem debugging of it's core (not VM, hypervisor itself!). >> So the idea is to save physical memory state and later use GDB to interpret >> it. > I still do not understand what is the goal. > > "not VM, hypervisor itself!" would say that running "/usr/bin/gcore "+getpid() > on the hypervisor process would do the job. Bare-metal hypervisor doesn't have a representation in process tree of any guest VM. I do not have running OS where I can do `/usr/bin/gcore`. It's Xen alike hypervisor =) > But then "the idea is to save physical memory state" would suggest me you want > to dump the guest VM - like what guest kdump does or what is in guest Linux > kernel /proc/kcore (where it is without the physical memory). > > > Jan Idea is very similar to `kdump`, you are right. But instead of Linux kernel I have a hypervisor running on a bare-metal. So, in some point of view, I try to implement my own kdump. And it will dump not Linux kernel mem, but mem of hypervisor.