From: Jim Fehlig <jfehlig@novell.com>
To: xen-devel@lists.xensource.com
Cc: John Levon <levon@movementarian.org>
Subject: Re: That xenstored console leak...
Date: Mon, 14 Jan 2008 12:27:10 -0700 [thread overview]
Message-ID: <478BB78E.5020709@novell.com> (raw)
In-Reply-To: <4787C804.4010909@novell.com>
Jim Fehlig wrote:
> John Levon wrote:
>
>> Here's what I'm using to fix it in 3.1. Obviously too risky for 3.2 now,
>> and anyway, there's a much more serious problem in 3.2 - entire /vm/
>> entries are leaked on domU reboot! I haven't got round to debugging that
>> one yet since it's not present in 3.1, but it really should be fixed
>>
>>
>
> I'm unable to reproduce the console leak on 3.2. I have tried rebooting
> managed PV domU's several times with no orphaned console entries - using
> 'xm reboot' and rebooting within the guest itself.
>
> I do however see the entire /vm/<uuid> nodes leaking and agree that this
> is a rather serious bug as it could eventually cause swap thrashing in
> dom0 [1]. E.g. after 3 reboots of PV domU xenstore contains
>
> vm
> faa7647e-142b-74c7-dc72-efd57fe6d0ef-1 = ""
> image = "(linux (kernel ) (args 'mem=512M ') (device_model
> /usr/lib64/xen/bin/qemu\..."
> ostype = "linux"
> ...
> faa7647e-142b-74c7-dc72-efd57fe6d0ef = ""
> image = "(linux (kernel ) (args 'mem=512M ') (device_model
> /usr/lib64/xen/bin/qemu\..."
> ostype = "linux"
> ...
> faa7647e-142b-74c7-dc72-efd57fe6d0ef-2 = ""
> image = "(linux (kernel ) (args 'mem=512M ') (device_model
> /usr/lib64/xen/bin/qemu\..."
> ostype = "linux"
> ...
>
> This leak is much worse than a single device leaking :-(. I'll have a
> look but may be a day or two before I can get to it.
>
> Jim
>
> [1] http://lists.xensource.com/archives/html/xen-devel/2007-05/msg00641.html
>
After some investigation I have found that the /vm/<uuid> leak is caused
by c/s 15957 (later modified by c/s 15967). Reverting these changesets
removes the leak on 3.2 RC4. Further, when reverting c/s 15957 I am not
seeing the issue it claims to fix - i.e. I am not losing the vif mac
address when doing localhost migrations of PV or HVM domU's.
Keir - under what circumstances was vif mac address being lost? I am
unable to reproduce that behavior on RC4 with 15967 and 15957 reverted.
Regards,
Jim
next prev parent reply other threads:[~2008-01-14 19:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 17:39 That xenstored console leak John Levon
2008-01-11 19:24 ` Keir Fraser
2008-01-11 19:48 ` Jim Fehlig
2008-01-11 19:57 ` John Levon
2008-01-14 19:27 ` Jim Fehlig [this message]
2008-01-14 20:08 ` John Levon
2008-01-14 21:29 ` Keir Fraser
2008-01-14 21:48 ` John Levon
2008-01-14 21:54 ` Keir Fraser
2008-01-14 22:55 ` John Levon
2008-01-14 22:59 ` Daniel P. Berrange
2008-01-15 8:08 ` Keir Fraser
2008-01-15 8:06 ` Keir Fraser
2008-01-15 13:42 ` John Levon
2008-01-15 13:54 ` Keir Fraser
2008-01-15 13:57 ` Keir Fraser
2008-01-15 13:59 ` Keir Fraser
2008-01-15 14:31 ` John Levon
2008-01-15 14:37 ` Keir Fraser
2008-01-15 14:38 ` John Levon
2008-01-15 14:42 ` Keir Fraser
2008-01-15 15:59 ` Jim Fehlig
2008-01-15 16:11 ` John Levon
2008-01-15 16:28 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2008-01-14 23:49 Jim Fehlig
2008-01-15 8:10 ` Keir Fraser
2008-01-18 23:14 Jim Fehlig
2008-01-18 23:18 ` Keir Fraser
2008-01-18 23:47 ` Jim Fehlig
2008-01-19 8:11 ` Keir Fraser
2008-01-25 2:00 ` Jim Fehlig
2008-01-25 7:44 ` Keir Fraser
[not found] ` <479A002E.6010802@novell.com>
2008-01-25 15:41 ` John Levon
2008-01-25 16:21 ` Jim Fehlig
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=478BB78E.5020709@novell.com \
--to=jfehlig@novell.com \
--cc=levon@movementarian.org \
--cc=xen-devel@lists.xensource.com \
/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.