All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Alexey <alukardd@alukardd.org>
Cc: Xen-devel@lists.xen.org
Subject: Re: null domains | xen4.4
Date: Mon, 1 Dec 2014 09:59:18 +0000	[thread overview]
Message-ID: <1417427958.27655.1.camel@citrix.com> (raw)
In-Reply-To: <e2a4f20c920a491592cef78dd006da8a@alukardd.org>

On Mon, 2014-12-01 at 12:48 +0300, Alexey wrote:
> Hi, all!
> 
> We are once again faced with the null-domains problem.
> At this moment we have xen node with 49 null-domains and if I create new 
> domain and shutdown it I w'll get a new one null-domain.
> 
> All blkback and netback kernel process are exists. There is no qemu 
> process running.
> I can't delete any vif or stop disk, which was used by dead domain.

What do you mean here, does a vif or disk still exist for the dead
domain then?

> How we can prevent appearance of null-domains?
> How we can unlock resources of existing null-domains?

A null domain remains when a page owned by that domain is still
referenced from somewhere. The output of the 'q' debug key sometimes
exposes the source of such references. ("xl debug-key q" will send that,
the result appears in "xl dmesg", alternatively Ctrl-A three times on
the serial console then 'q').

> # xl info
> host                   : xen23
> release                : 3.10-3-amd64

Any chance you could try a newer dom0 kernel?

> xen_commandline        : tmem=1 loglvl=all noreboot dom0_mem=5120M 
> dom0_vcpus_pin console=vga vga=current

Are you able to reproduce when tmem is not enabled?

Ian.

  reply	other threads:[~2014-12-01  9:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-01  9:48 null domains | xen4.4 Alexey
2014-12-01  9:59 ` Ian Campbell [this message]
2014-12-01 10:54   ` Alexey
2014-12-01 11:00     ` Ian Campbell
2014-12-01 11:27       ` Alexey

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=1417427958.27655.1.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Xen-devel@lists.xen.org \
    --cc=alukardd@alukardd.org \
    /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.