On 9/11/07 04:49, "John Levon" <levon@xxxxxxxxxxxxxxxxx> wrote:
> It's the below changeset - no code to reset the domid exists any more.
> It seems suboptimal to me? Shouldn't refreshShutdown (or somewhere,
> anyway) remove domid?
Does this only happen for your special screwed domains that don't actually
die?
You can use the 'q' debug key to Xen to get it to print out per-domain info,
including a list of held pages (if there's only one or two pages held) and
their reference counts.
-- Keir
> I noticed this whilst having another, more serious problem: sometimes,
> domains are never released, with a page still referenced (presumably?):
>
>>>> xc.domain_getinfo(21, 1)
> [{'paused': 0, 'cpu_time': 4895498373L, 'ssidref': 0, 'hvm': 0,
> 'shutdown_reason': 0, 'dying': 1, 'mem_kb': 4L, 'domid': 22,
> 'max_vcpu_id': 0, 'crashed': 0, 'running': 0, 'maxmem_kb': 1048576L,
> 'shutdown': 0, 'online_vcpus': 1, 'handle': [75, 158, 234, 68, 113, 241,
> 195, 238, 113, 125, 31, 198, 154, 74, 44, 188], 'blocked': 1}]
>
> None of the user-space daemons seem to be the culprit. I'm still trying
> to find out why xen thinks a page is still held. Note that this domain
> is still using flip instead of copy - I know that's not the default,
> could a bug there have crept in?
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home