Re: cannot kill (null) domains

[Brad Spencer <brad%anduin.eldar.org@localhost>]

Petr Topiarz <topiarz%post.cz@localhost> writes:

> Hello folks,
>
> I run NetBSD 8_stable amd64 and upgraded xen from the old 4.1 to 4.8 and 
> face this issue. I do not know  when it happened but there seem to be 
> two (null) paused and dying domains which consume memory and I cannot 
> kill them. These two domains cannot be unpaused or destroyed, they 
> ignore all commands. Any way to get rid of them?
>
> Thank you, Petr
>
> Here is the xen version:
>
> # pkg_info |grep xen
> xenkernel48-4.8.3   Xen 4.8.x Kernel
> xentools48-4.8.3nb5 Userland Tools for Xen 4.8.x
>
> Here you can see the list command:
>
> # xl list
> Name                                        ID   Mem VCPUs State   Time(s)
> Domain-0                                     0  4096     1 r-----   75701.8
> lin-orange                                   1  5000     1 -b----   46265.8
> (null)                                       2  2641     1 --ps-d   10254.3
> (null)                                       3  2248     1 --ps-d   12449.9
> net-web                                      4  2000     1 -b----    9425.8
> lin-tritius                                  5 10000     2 -b----   86002.0
> net8-proxy                                   8  2000     1 -b----    3115.6
> net8-compiler                                9  4000     2 -b----    7516.3
> net8-web                                    10  4000     2 -b----    7672.0
> win-red                                     12  4999     1 -b----    5550.6
> win-aegidius                                13  3999     1 -b----      32.7
> win-les                                     14  3999     1 -b----      18.6


I see this with HVM style guests.  If these are or were HVM guest zones
look for a hung qemu process.  I typically end up having to kill those
off to get the (null) zones to clear out.  This happened in 4.5 and
happens in 4.8.




-- 
Brad Spencer - brad%anduin.eldar.org@localhost - KC8VKS - http://anduin.eldar.org