[Pkg-xen-devel] Xen 4.14 is in Debian unstable | Please test! | Bullseye plans

[Hans van Kranenburg]

Hi!

On 12/3/20 10:56 PM, Alexander Dahl wrote:
> Hei hei,
> 
> On Tue, Nov 24, 2020 at 05:41:42PM +0100, Hans van Kranenburg wrote:
>> If you're running Debian testing with Xen, then expect the change to
>> arrive on your system in a few days. When using HVM, don't rush and pull
>> the packages from unstable, since qemu still needs a rebuild to depend
>> on libxen-4.14 instead of libxen-4.11 (more about that later...).
> 
> That's the case here, running on bullseye/testing.
> 
>> -- Help testing! --
>>
>> Any help with testing is appreciated, especially since there are so many
>> combinations of hardware, different architectures and use cases (using
>> legacy BIOS or EFI, PV, PVH, HVM, different boot loaders like pvgrub,
>> pygrub, etc etc).
> 
> x86_64 host here, and some old 32 bit virtual machines, no weird
> network or hardware pass through setup, rather simple.  HVM and pvgrub
> based DomU VMs run fine so far.  pygrub based VMs, both 32 bit and 64
> bit fail with the following error:
> 
>   Traceback (most recent call last):
>     File "/usr/lib/xen-4.14/bin/pygrub", line 27, in <module>
>       import xenfsimage
>   ModuleNotFoundError: No module named 'xenfsimage'

Ok, so you're running Debian testing, and our Xen 4.14 package migrated
into there, and Debian testing has python 3.8 as python3-defaults:

https://packages.debian.org/src:python3-defaults

Exact hits
Source Package python3-defaults

    jessie (python): 3.4.2-2
    Binary packages: [show 16 binary packages]
    stretch (python): 3.5.3-1
    Binary packages: [show 16 binary packages]
    buster (python): 3.7.3-1
    Binary packages: [show 18 binary packages]
    bullseye (python): 3.8.6-1
    Binary packages: [show 18 binary packages]
    sid (python): 3.9.0-3
    Binary packages: [show 18 binary packages]

And what do we have in the packages that just migrated to testing:

xenfsimage.cpython-39-x86_64-linux-gnu.so

So, apparently there's some thing that causes xenfsimage to end up with
such a monstrous name, and if you have python 3.9 as default (in
unstable) it will find it, and for testing with 3.8, it will not.

I have no idea what's going on here. We probably should find out.

>> IRC: #debian-xen @ OFTC
> 
> Joined that for now.
> 
>> Bugs: https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=xen
> 
> Should I file a new bug for the above mentioned problem?  Or is that
> covered by #975062 already?

It should be a different issue yes.

Hans