On 07/11/2024 2:19 pm, Javi Merino wrote:
> In the qemu-alpine-x86_64-gcc test, we want to test libxenguest built
> with all libraries.  If we add lzo-dev to the alpine:3.18 container,
> libxenguest is linked against it.  However, as the initrd in the
> test-artifacts does not contain lzo, the qemu-alpine-x86_64-gcc gitlab
> CI job fails with:
>
>   + bash /etc/init.d/xencommons start
>   Starting /usr/local/sbin/xenstored...
>   /etc/xen/scripts/launch-xenstore: line 90: echo: write error: Invalid 
> argument
>   Setting domain 0 name, domid and JSON config...
>   Error loading shared library liblzo2.so.2: No such file or directory 
> (needed by /usr/local/lib/libxenguest.so.4.20)
>   Error relocating /usr/local/lib/libxenguest.so.4.20: __lzo_init_v2: symbol 
> not found
>   Error relocating /usr/local/lib/libxenguest.so.4.20: lzo1x_decompress_safe: 
> symbol not found
>   Starting xenconsoled...
>   Starting QEMU as disk backend for dom0
>   + xl list
>   Error loading shared library liblzo2.so.2: No such file or directory 
> (needed by /usr/local/lib/libxenguest.so.4.20)
>   Error relocating /usr/local/lib/libxenguest.so.4.20: __lzo_init_v2: symbol 
> not found
>   Error relocating /usr/local/lib/libxenguest.so.4.20: lzo1x_decompress_safe: 
> symbol not found
>   + xl create -c /root/test.cfg
>   Error loading shared library liblzo2.so.2: No such file or directory 
> (needed by /usr/local/lib/libxenguest.so.4.20)
>   Error relocating /usr/local/lib/libxenguest.so.4.20: __lzo_init_v2: symbol 
> not found
>   Error relocating /usr/local/lib/libxenguest.so.4.20: lzo1x_decompress_safe: 
> symbol not found
>    *   Execution of "/etc/local.d/xen.start" failed.
>
> Add lzo to the initrd that becomes the rootfs to install liblzo2.so.2 .
>
> Signed-off-by: Javi Merino <[email protected]>

Ah - this is a good example of the problem I opined about in
https://lore.kernel.org/xen-devel/[email protected]/T/#u

For now, I'll take this and use it as a test of whether I can drive the
new test-artefacts repo.

Acked-by: Andrew Cooper <[email protected]>

Reply via email to