From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= Subject: Re: xen-unstable: commit commit 63753b3e0dc56efb1acf94fa46f3fee7bc59281c leaves HVM guest dangling after shutdown or destroy. Date: Tue, 23 Apr 2013 17:35:09 +0200 Message-ID: <5176AA2D.4020307@citrix.com> References: <881882180.20130420152124@eikelenboom.it> <82be0365-68f4-4d75-88f5-44a59c796a75@email.android.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <82be0365-68f4-4d75-88f5-44a59c796a75@email.android.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Konrad Rzeszutek Wilk Cc: Sander Eikelenboom , Jan Beulich , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 20/04/13 20:56, Konrad Rzeszutek Wilk wrote: > > > Sander Eikelenboom 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). >> >> -- >> >> Sander >