From mboxrd@z Thu Jan  1 00:00:00 1970
From: George Dunlap <george.dunlap@eu.citrix.com>
Subject: Re: xen-unstable: commit commit
 63753b3e0dc56efb1acf94fa46f3fee7bc59281c leaves HVM guest dangling after
 shutdown or destroy.
Date: Tue, 30 Apr 2013 14:58:17 +0100
Message-ID: <517FCDF9.4070303@eu.citrix.com>
References: <881882180.20130420152124@eikelenboom.it>
	<82be0365-68f4-4d75-88f5-44a59c796a75@email.android.com>
	<5176AA2D.4020307@citrix.com>
	<CAFLBxZY0mXfUN0DYJ=CR6zw1e502NZQA-ZfQYdPQgpHSHR8=Sw@mail.gmail.com>
	<20130430135553.GA19986@phenom.dumpdata.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <20130430135553.GA19986@phenom.dumpdata.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Sander Eikelenboom <linux@eikelenboom.it>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>, Jan Beulich <jbeulich@suse.com>, Roger Pau Monne <roger.pau@citrix.com>
List-Id: xen-devel@lists.xenproject.org

On 04/30/2013 02:55 PM, Konrad Rzeszutek Wilk wrote:
> On Wed, Apr 24, 2013 at 10:31:20AM +0100, George Dunlap wrote:
>> On Tue, Apr 23, 2013 at 4:35 PM, Roger Pau Monn=E9 <roger.pau@citrix.com=
> wrote:
>>> On 20/04/13 20:56, Konrad Rzeszutek Wilk wrote:
>>>>
>>>>
>>>> Sander Eikelenboom <linux@eikelenboom.it> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Commit 63753b3e0dc56efb1acf94fa46f3fee7bc59281c x86: allow
>>>>> VCPUOP_register_vcpu_info to work again on PVHVM guests
>>>>>
>>>>> Leaves HVM guests dangling after shutdown or destroy:
>>>>>
>>>>> xl list gives:
>>>>> (null)                                      16     0     4     --p--d
>>>>>    11.5
>>>>> (null)                                      17     0     1     --ps-d
>>>>>    12.0
>>>>>
>>>>> (first was destroyed, second shutdown)
>>>>>
>>>>> The actual xl and qemu processes are gone, so guest only seem to be
>>>>> still registered in the hypervisor.
>>>>>
>>>>> Another thing this seems to trigger (and that perhaps needs fixing) is
>>>>> that a "xl shutdown --all --wait" doesn't wait anymore.
>>>>> It returns immediately, probably due to the "nullified" name ?
>>>>
>>>> Is this only happening with Linux guests?
>>>
>>> AFAIK this seems to happen with guests that use
>>> VCPUOP_register_vcpu_info (I'm seeing the same on FreeBSD).
>>
>> Are we leaving a reference to a page dangling around somewhere?
>
> <nods> That is my thinking. George, if you would not mind - could you add
> this to the list of bugs for Xen 4.3 I am responsible for.

Done.

  -George