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 11:00:05 +0000	[thread overview]
Message-ID: <1417431605.29138.5.camel@citrix.com> (raw)
In-Reply-To: <2a9dd806b9991d506ae274ff67fe5821@alukardd.org>

On Mon, 2014-12-01 at 13:54 +0300, Alexey wrote:
> xl list two domains for example:
> (null)                                      67     0     8     --pssd  
> 135229.6
> (null)                                      69     0     4     --ps-d    
> 4172.2
> 
> vif67.0 still exist in my dom0 and i can't "ip link delete" it.
> Attached block device marked as busy also.

What does "xenstore-ls -fp" say? Are the backend xenstore nodes still
present?

> We try to use the last 3.10 kernel, now new nodes use 3.10.61 kernel, 
> but this node on which I can experiment was booted with 3.10.55 kernel.

I meant something newer than 3.10, not just the latest 3.10.

> I attach xl-dmesg after 'q' trigger.

Thanks, seems like each domain has three leaked pages, e.g.:

(XEN) Memory pages belonging to domain 4:
(XEN)     DomPage 0000000000c2b7e6: caf=00000001, taf=7400000000000001
(XEN)     DomPage 0000000000c2aa03: caf=00000001, taf=7400000000000001
(XEN)     DomPage 0000000000cb8397: caf=00000001, taf=7400000000000001

If the vifX.Y device is still in existence then there's a pretty good
chance it's holding a page, likewise any disk backends etc.

Are there any messages in the dom0 dmesg around the time of the guest
supposedly shutting down? How about logs under /var/log/xen.

Ian.

  reply	other threads:[~2014-12-01 11:00 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
2014-12-01 10:54   ` Alexey
2014-12-01 11:00     ` Ian Campbell [this message]
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=1417431605.29138.5.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.