Re: Booting the FreeBSD kernel as an zImage file needs a patch upgrade ?.

[Julien Grall <julien@xxxxxxx>]

Hi Mario,

On 09/01/2024 00:25, Mario Marietto wrote:
> A great progress,I think :
>
> name="freebsd"
> kernel="/mnt/zroot2/zroot2/OS/Chromebook/freebsd-xen/domU-freebsd/bootloaders/kernel.bin"
>
> extra = "console=hvc0"
> memory=512
> vcpus=1
> disk = [ 'FreeBSD-13.2-RELEASE-armv7.img,raw,xvda' ]
>
> root@devuan-bunsen:/mnt/zroot2/zroot2/OS/Chromebook/freebsd-xen/domU-freebsd#
> ./start-freebsd
>
> Parsing config from freebsd.cfg
> libxl: error: libxl_device.c:1163:device_backend_callback: Domain 1:unable
> to add device with path /
> local/domain/0/backend/vbd/1/51712
> libxl: error: libxl_create.c:1672:domcreate_launch_dm: Domain 1:unable to
> add disk devices
> libxl: error: libxl_device.c:1163:device_backend_callback: Domain 1:unable
> to remove device with pat
> h /local/domain/0/backend/vbd/1/51712
> libxl: error: libxl_domain.c:1530:devices_destroy_cb: Domain
> 1:libxl__devices_destroy failed
> libxl: error: libxl_domain.c:1183:libxl__destroy_domid: Domain
> 1:Non-existent domain
> libxl: error: libxl_domain.c:1137:domain_destroy_callback: Domain 1:Unable
> to destroy guest
> libxl: error: libxl_domain.c:1064:domain_destroy_cb: Domain 1:Destruction
> of domain failed
> freebsd is an invalid domain identifier (rc=-6)
There are not much information in the logs indicating why the disk 
devices couldn't be added. To confirm, have you been able to boot a 
Linux guest on the same setup?
A few more questions:
  - Can you confirm your dom0 setup?
  - Do you have xen-blkback either loaded or built into the kernel?
  - Can you run again with 'xl -vvvv create ...'? The command should be 
more verbose and hopeful give us more details why the device can't be 
added..
Cheers,

--
Julien Grall