All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kip Macy <kmacy@fsmware.com>
To: xen-devel@lists.sourceforge.net
Subject: dumping a domain's core
Date: Sun, 22 Feb 2004 12:46:34 -0800 (PST)	[thread overview]
Message-ID: <20040222124211.T84871@demos.bsdclusters.com> (raw)

When a domain is killed by Xen:
DOM0: (file=memory.c, line=333) Page 11c51000 bad type/count (02000000!=01000000) cnt=1
Killing domain 3
Releasing task 3

it would be nice if it notified DOM0, so that DOM0 could map in the
domain's pages and write them out to disk. Is there an existing
mechanism in place that I can use for notification?


			-Kip





-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click

             reply	other threads:[~2004-02-22 20:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-22 20:46 Kip Macy [this message]
2004-02-22 21:02 ` dumping a domain's core Ian Pratt
2004-02-22 21:17   ` Kip Macy
2004-02-22 21:38     ` Ian Pratt
2004-02-22 22:02       ` DEBUG output starving network requests Kip Macy
2004-02-22 22:23         ` Keir Fraser
2004-02-22 23:35       ` problems with recursively mapping page directory as a page table Kip Macy
2004-02-23 13:15         ` Christian Limpach
2004-02-23 21:02       ` refcount errors then crash on XenoLinux with the latest source Kip Macy
2004-02-23 21:36         ` Kip Macy
2004-02-23 23:35           ` Keir Fraser
2004-02-24  1:11             ` Kip Macy
2004-02-24  3:44               ` Kip Macy
2004-02-24  8:15                 ` Ian Pratt
2004-02-24  8:35                   ` Keir Fraser
2004-02-24 17:21                     ` Kip Macy
2004-02-24 17:45                       ` Ian Pratt
2004-02-24  8:40               ` Keir Fraser

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=20040222124211.T84871@demos.bsdclusters.com \
    --to=kmacy@fsmware.com \
    --cc=xen-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.