Re: Internal Error: libxenlight failed to create new domain "FreeBSD-13.2"

[Mario Marietto <marietto2008@xxxxxxxxx>]

I think I found the solution here :

https://blog.roberthallam.org/2020/05/solving-unable-to-find-partition-containing-kernel/

I've created a file called menu.lst inside the boot directory of the image file called "debian.img",adding the following content inside :

default 0

timeout 10

title Debian

root (hd0,1)

kernel /boot/vmlinux-6.1.59-stb-xen-cbe+ root=/dev/xvda

initrd /boot/initrd.img-6.1.59-stb-xen-cbe+

and I tried again to boot the image using virt-manager. It gave this error again :

root@devuan-bunsen:/mnt/zroot2/zroot2/OS/Chromebook/FreeBSD-guestOS/linux-xen/debian2/boot# 2023-11-29 15:21:09.266+0000: 2467: error : libxlDomainStartPerform:1256 : internal error: libxenlight failed to create new domain 'debian12'

but giving a look inside the log file and I found this interesting situation ;

Using <class 'grub.GrubConf.GrubConfigFile'> to parse /boot/grub/menu.lst
(B )0 [1;24r [m [?7h [?1h = [H [J [?1h = [1B    pyGRUB  version 0.6
[1B [0m lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
[1B [0m x [0;7m Debian 12                                                             [m [0m x
[1B [0m x [72C [0m x
[1B [0m x [72C [0m x
[1B [0m x [72C [0m x
[1B [0m x [72C [0m x
[1B [0m x [72C [0m x
[1B [0m x [72C [0m x
[1B [0m x [72C [0m x
[1B [0m mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj [1B [70D [0m Use the ↑ and ↓ keys to select which entry is highlighted. [1B [58DPress enter to boot the selected OS, 'e' to edit the [1B [52Dcommands before booting, 'a' to modify the kernel arguments [1B [59Dbefore booting, or 'c' for a command line. [12A [26C [17B [68DWill boot selected entry in 10 seconds [?1h =
[J [17A [73C [17B [68DWill boot selected entry in  9 seconds [?1h =
[J [17A [73C [17B [68DWill boot selected entry in  8 seconds [?1h =
[J [17A [73C [17B [68DWill boot selected entry in  7 seconds [?1h =
[J [17A [73C [17B [68DWill boot selected entry in  6 seconds [?1h =
[J [17A [73C [17B [68DWill boot selected entry in  5 seconds [?1h =
[J [17A [73C [17B [68DWill boot selected entry in  4 seconds [?1h =
[J [17A [73C [17B [68DWill boot selected entry in  3 seconds [?1h =
[J [17A [73C [17B [68DWill boot selected entry in  2 seconds [?1h =
[J [17A [73C [17B [68DWill boot selected entry in  1 seconds [?1l > [24;1H
[?1l >

so,it seems that it tried to boot,but for an unknown reason,it gave the error anyway.

On Wed, Nov 29, 2023 at 3:27 PM Mario Marietto <marietto2008@xxxxxxxxx> wrote:

ok. I tried to fix the broken installation and now the error is changed :

Traceback (most recent call last):
  File "/usr/lib/xen-4.17/bin/pygrub", line 884, in <module>
    raise RuntimeError("Unable to find partition containing kernel")
RuntimeError: Unable to find partition containing kernel

On Wed, Nov 29, 2023 at 2:53 PM Michal Prívozník <mprivozn@xxxxxxxxxx> wrote:

On 11/29/23 14:04, marietto2008@xxxxxxxxx wrote:
> The reason for that error maybe written inside this log messages :
>
> libxl: libxl_event.c:855:libxl__ev_xswatch_deregister: remove watch for path @releaseDomain: Descrittore di file errato
>
> libxl: libxl_event.c:855:libxl__ev_xswatch_deregister: remove watch for path @releaseDomain: Bad file descriptor
>
> libxl: libxl_event.c:855:libxl__ev_xswatch_deregister: remove watch for path @releaseDomain: Bad file descriptor
>
> libxl: libxl_arm.c:1538:libxl__arch_domain_create_info_setdefault: Converting PV guest to PVH.
>
> libxl: libxl_arm.c:1539:libxl__arch_domain_create_info_setdefault: Arm guest are now PVH.
>
> libxl: libxl_arm.c:1540:libxl__arch_domain_create_info_setdefault: Please fix your configuration file/toolstack.
>
> libxl: libxl_bootloader.c:648:bootloader_finished: Domain 1:bootloader failed - consult logfile /var/log
> /xen/bootloader.1.log
>

This tells you to look into the log file. Did you? What is there?

<snip/>
>
> Traceback (most recent call last):
>  File "/usr/lib/xen-4.17/bin/pygrub", line 27, in <module>
>    import xenfsimage
> ImportError: libxenfsimage.so.4.17: cannot open shared object file: No such file or directory

Is this the contents of that file? If so, then your xen installation is
broken because it did not install the .so.

Michal

--

Mario.

--

Mario.

_______________________________________________
Users mailing list -- users@xxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxx