26 messages in com.xensource.lists.xen-develRe: [Xen-devel] suspending a domain i...
FromSent OnAttachments
Keir Fraser13 May 2004 23:34 
Kip Macy14 May 2004 13:56 
Kip Macy14 May 2004 14:01 
Kip Macy14 May 2004 14:25 
Ian Pratt14 May 2004 14:33 
Kip Macy14 May 2004 14:48 
Kip Macy14 May 2004 15:37 
Kip Macy14 May 2004 15:39 
Ian Pratt14 May 2004 15:48 
Kip Macy14 May 2004 16:14 
Neugebauer, Rolf14 May 2004 16:28 
Kip Macy14 May 2004 17:46 
Kip Macy14 May 2004 18:38 
Kip Macy14 May 2004 21:26 
Kip Macy14 May 2004 22:17 
Keir Fraser15 May 2004 01:15 
Ian Pratt15 May 2004 01:58 
Neugebauer, Rolf15 May 2004 02:39 
Kip Macy15 May 2004 08:50 
Kip Macy15 May 2004 08:57 
Kip Macy15 May 2004 08:59 
Keir Fraser15 May 2004 09:11 
Kip Macy15 May 2004 10:02 
Keir Fraser15 May 2004 10:42 
Kip Macy15 May 2004 11:09 
Keir Fraser15 May 2004 16:21 
Subject:Re: [Xen-devel] suspending a domain in the ngio world
From:Keir Fraser (Keir@cl.cam.ac.uk)
Date:05/15/2004 04:21:22 PM
List:com.xensource.lists.xen-devel

The dd is running in DOM1. The OOM killer is getting run in DOM0. There is clearly a memory leak in the block I/O path.

Now fixed. It turned out to be rather blatant.

On a side note - I don't need suspend/restore, I just need coredump and almost immediately after that PTRACE_STOP. So long as I can stop the domain long enough to write out its state I have what I need.

A pause operation will be coming up soon, as part of a cleanup of the scheduler interface in Xen. This will fix the problem that there's currently no way to stop a domain without having it suspend itself.

-- Keir