[Pkg-xen-devel] Bug#922033: Bug#922033: xen: driver domain does not work

[Hans van Kranenburg]

On 2/13/19 2:17 AM, Marek Marczykowski-Górecki wrote:
> On Wed, Feb 13, 2019 at 02:07:22AM +0100, Hans van Kranenburg wrote:
>> xen-utils-common 4.11 does not depend on xen-utils 4.11, so it can be
>> missing.
> 
> Oh... so maybe search for latest one and error out if none is there?
> Or, create yet another binary package which depends on both, intended to
> be installed in guest (description of xen-utils-common says it's for
> dom0 only), and ship xendriverdomain service there?

I have never used Xen stuff inside a domU, but only the idea that
xen-utils-common with all the dom0 stuff is also supposed to be
installed inside a domU while trying these things has only frightened
me. And it seems that feeling wasn't completely misguided.

>> What if you try running /usr/lib/xen-4.8/bin/xl directly instead, for fun?
> 
> 4.8 is not there, but 4.11 is and it works.

Eh, yeah, 4.11, obviously.

> After printing some errors
> which I believe are unrelated to Debian packaging:
> 
>     root at d10test:/home/user# /usr/lib/xen-4.11/bin/xl devd
>     libxl: error: libxl.c:363:libxl_get_physinfo: getting physinfo: Permission denied
>     libxl: error: libxl_utils.c:820:libxl_cpu_bitmap_alloc: failed to retrieve the maximum number of cpus
>     libxl: error: libxl_utils.c:820:libxl_cpu_bitmap_alloc: failed to retrieve the maximum number of cpus
>     libxl: error: libxl_utils.c:820:libxl_cpu_bitmap_alloc: failed to retrieve the maximum number of cpus
>     root at d10test:/home/user# ps aux|grep xl\ devd
>     root     25841  0.0  0.1  72144  2228 ?        Ssl  20:09   0:00 /usr/lib/xen-4.11/bin/xl devd

It does something! \o/

Creating new binary packages etc... is not an option anymore during the
Buster freeze.

At some point Ian will probably look at this in the next days, to see
what we still can do for Buster. Any testing you can do and anything you
can find out in the meantime is of course useful.

Thanks,

K