Re: [Xen-devel] xen-unstable: commit commit 63753b3e0dc56efb1acf94fa46f3fee7bc59281c leaves HVM guest dangling after shutdown or destroy.

[Sander Eikelenboom <linux@xxxxxxxxxxxxxx>]

Saturday, April 20, 2013, 8:56:06 PM, you wrote:



> Sander Eikelenboom <linux@xxxxxxxxxxxxxx> 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?

Errr good guess .. yes it seems so, destroying linux guest ends up with the 
"(null)" entry in xl list.
With a windows guest it destroys ok.

>>
>>--
>>
>>Sander



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel