5:41 a.m.
Hello to everyone.
I'm trying to use xen as a hypervisor instead of kvm to boot FreeBSD on my ARM
Chromebook where I have installed Devuan 5. A developer said that it can work. In fact he
said :
"That might work. libvirt + virt-manager with the xen accelerator might work on the
ARM Chromebook. That's because as far as I know Xen integration in libvirt is done via
linking to libxl directly and libxl is supported and working on ARM"
Unfortunately something is not working properly. What I did has been to reboot the machine
in xen,enable libvirtd & and virtlogd & and virt-manager &,but this is what
happened :
root@devuan-bunsen:/Dati/virt-manager-4.1.0# ./virt-manager &
[3] 2507
root@devuan-bunsen:/Dati/virt-manager-4.1.0# info : libvirt version: 9.7.0
info : hostname: devuan-bunsen
error : virConnectGetAllDomainStats:12595 : this function is not supported by the
connection driver: virConnectGetAllDomainStats
error : virDomainListAllSnapshots:519 : this function is not supported by the connection
driver: virDomainListAllSnapshots
[3]+ Completed ./virt-manager
root@devuan-bunsen:/mnt/zroot2/zroot2# error : libxlDomainStartPerform:1256 : internal
error: libxenlight failed to create new domain 'FreeBSD-13.2
Traceback (most recent call last):
File "/Dati/virt-manager-4.1.0/./virtManager/asyncjob.py", line 72, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/Dati/virt-manager-4.1.0/./virtManager/createvm.py", line 2008, in
_do_async_install
installer.start_install(guest, meter=meter)
File "/Dati/virt-manager-4.1.0/./virtinst/install/installer.py", line 695, in
start_install
domain = self._create_guest(
^^^^^^^^^^^^^^^^^^^
File "/Dati/virt-manager-4.1.0/./virtinst/install/installer.py", line 637, in
_create_guest
domain = self.conn.createXML(initial_xml or final_xml, 0)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/libvirt.py", line 4481, in createXML
raise libvirtError('virDomainCreateXML() failed')
libvirt.libvirtError: internal error: libxenlight failed to create new domain
'FreeBSD-13.2'
you may also be interested to give a look at this picture :
https://ibb.co/Lh0xkfy
...between the running processes I see this :
# ps ax | grep qemu
1507 ? Sl 0:00 /usr/libexec/xen-qemu-system-i386 -xen-domid 0 -xen-attach -name
dom0 -no graphic -M xenpv -daemonize -monitor none -serial none -parallel none -pidfile
/run/qemu-dom0.pid
The interesting point is that it is using xen-qemu-system-i386. Is it supposed to work on
an ARM architecture ? What's the problem that I may have now ?
7:04 a.m.
New subject: Internal Error: libxenlight failed to create new domain
"FreeBSD-13.2"
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
libxl: libxl_exec.c:117:libxl_report_child_exitstatus: bootloader [2850] exited with error
status 1
libxl: libxl_create.c:1640:domcreate_rebuild_done: Domain 1:cannot (re-)build domain: -3
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 2:bootloader failed - consult
logfile /var/log
/xen/bootloader.2.log
libxl: libxl_exec.c:117:libxl_report_child_exitstatus: bootloader [2879] exited with error
status 1
libxl: libxl_create.c:1640:domcreate_rebuild_done: Domain 2:cannot (re-)build domain: -3
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 3:bootloader failed - consult
logfile /var/log/xen/bootloader.3.log
libxl: libxl_exec.c:117:libxl_report_child_exitstatus: bootloader [2892] exited with error
status 1
libxl: libxl_create.c:1640:domcreate_rebuild_done: Domain 3:cannot (re-)build domain: -3
libxl: libxl_event.c:855:libxl__ev_xswatch_deregister: remove watch for path
@releaseDomain: Descrittore di file errato
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
libxl: libxl_exec.c:117:libxl_report_child_exitstatus: bootloader [3025] exited with error
status 1
libxl: libxl_create.c:1640:domcreate_rebuild_done: Domain 1:cannot (re-)build domain: -3
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 2:bootloader failed - consult
logfile /var/log/xen/bootloader.2.log
libxl: libxl_exec.c:117:libxl_report_child_exitstatus: bootloader [3030] exited with error
status 1
libxl: libxl_create.c:1640:domcreate_rebuild_done: Domain 2:cannot (re-)build domain: -3
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
7:52 a.m.
New subject: Internal Error: libxenlight failed to create new domain
"FreeBSD-13.2"
On 11/29/23 14:04, marietto2008(a)gmail.com 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
8:27 a.m.
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(a)redhat.com>
wrote:
On 11/29/23 14:04, marietto2008(a)gmail.com 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.
9:31 a.m.
I think I found the solution here :
https://blog.roberthallam.org/2020/05/solving-unable-to-find-partition-co...
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(a)gmail.com>
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(a)redhat.com>
wrote:
> On 11/29/23 14:04, marietto2008(a)gmail.com 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.
323
days inactive
323
days old
4 comments
3 participants
participants (3)
-
marietto2008＠gmail.com -
Mario Marietto
-
Michal Prívozník