<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">Sorry for the late reply. I was off attending the Xen Developer Conference, and then testing out the latest kexec code, and am just getting back to this, On 10/23/13 12:37, Daniel Kiper wrote: </div> <blockquote cite="mid:20131023163740.GV3626@debian70-amd64.local.net-space.pl" type="cite"> <pre wrap="">On Tue, Oct 22, 2013 at 07:03:19PM +0200, Daniel Kiper wrote: </pre> <blockquote type="cite"> <pre wrap="">Hi, Sorry for late reply but I am very busy now. On Thu, Oct 17, 2013 at 03:25:25PM -0400, Don Slutz wrote: </pre> <blockquote type="cite"> <pre wrap="">On 10/16/13 09:49, Petr Tesarik wrote: </pre> <blockquote type="cite"> <pre wrap="">On Tue, 15 Oct 2013 12:02:51 -0400 Don Slutz <a class="moz-txt-link-rfc2396E" href="mailto:dslutz@verizon.com"><dslutz@verizon.com></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">I have some code that allows this. See the following mail thread: <a class="moz-txt-link-freetext" href="http://permalink.gmane.org/gmane.comp.emulators.xen.devel/174807">http://permalink.gmane.org/gmane.comp.emulators.xen.devel/174807</a> The questions are: 1. Does remote access have a specification? 2. Is it supported? </pre> </blockquote> <pre wrap="">I have never even made it to work. But since there's now some new use for it, I wouldn't object reviving the code. </pre> </blockquote> <pre wrap="">Good. </pre> <blockquote type="cite"> <blockquote type="cite"> <pre wrap=""> 3. Should the code be part of xen or crash? </pre> </blockquote> <pre wrap="">I think it should be part of xen, because it needs the xen development files, which would be a new dependency for the crash utility. Also, the development cycle is more aligned with xen than crash. Just my two cents, Petr T </pre> </blockquote> <pre wrap="">That is why I started with it in xen. Not sure where it will end up. </pre> </blockquote> <pre wrap=""> I do not know protocol details but I think that it is worth checking gdbsx tool from Xen (xen/tools/debugger/gdbsx) and gdb protocol spec (you could expose GDB interface from QEMU so it could be useful in HVM case). Maybe crash protocol is very similar or even identical with GDB protocol because a large part of crash is GDB itself. </pre> </blockquote> </blockquote> I can see using gdbsx and gdb. However I have found crash to be easier in lots of cases. I could have used xg from here if I did not already have code based on xenctx. <blockquote cite="mid:20131023163740.GV3626@debian70-amd64.local.net-space.pl" type="cite"> <pre wrap=""> Ugh... I was in a hurry and forgot about final statement. Sorry for that. </pre> </blockquote> No problem. <blockquote cite="mid:20131023163740.GV3626@debian70-amd64.local.net-space.pl" type="cite"> <pre wrap=""> So we could just use existing solutions if they are compatible with protocol used by crash. Daniel </pre> </blockquote> The only existing solution that I know of is: <blockquote>xl dump-core <Domain> <filename> crash <filename> </blockquote> But this way does require disk space, and the delay while writing the file. For me it took ~2 minutes to write out a 3G core file. I also do not see the current registers being saved in the core file. -Don Slutz </body> </html>