Viresh Kumar viresh.kumar@linaro.org writes:

On 11-02-22, 14:01, Alex Bennée wrote:

...

Viresh,

Apologies for the messy nature of my docker repo but there is a new image:

https://github.com/stsquad/dockerfiles/tree/master/crossbuild/bullseye-arm64

which I have confirmed can build current Xen master:

make[4]: Leaving directory '/home/alex.bennee/lsrc/xen/xen.build.arm64-xen-master-for-bullseye/tools/pygrub' make[3]: Leaving directory '/home/alex.bennee/lsrc/xen/xen.build.arm64-xen-master-for-bullseye/tools' make[2]: Leaving directory '/home/alex.bennee/lsrc/xen/xen.build.arm64-xen-master-for-bullseye/tools' make[1]: Leaving directory '/home/alex.bennee/lsrc/xen/xen.build.arm64-xen-master-for-bullseye/tools' fakeroot sh ./tools/misc/mkdeb /home/alex.bennee/lsrc/xen/xen.build.arm64-xen-master-for-bullseye $(make -C xen xenversion --no-print-directory) dpkg-deb: building package 'xen-upstream' in 'xen-upstream-4.17-unstable.deb'. 🕙14:00:03 alex.bennee@4372e168fe23:xen.build.arm64-xen-master-for-bullseye on  xen.build.arm64-xen-master-for-bullseye [?] took 31s ➜ ls -l dist/ total 24667 -rw-r--r-- 1 alex.bennee alex.bennee 20830 Jun 7 2021 COPYING -rw-r--r-- 1 alex.bennee alex.bennee 8632 Jun 7 2021 README drwxr-xr-x 6 alex.bennee alex.bennee 6 Feb 11 13:59 install/ -rwxr-xr-x 1 alex.bennee alex.bennee 658 Jun 7 2021 install.sh* -rw-r--r-- 1 alex.bennee alex.bennee 25213092 Feb 11 14:00 xen-upstream-4.17-unstable.deb

Just to completeness, you need to do this once prior to installing the one from crossbuild:

$ cd distros/debian-bullseye/ $ ../../build.sh $ cd ../../crossbuild/bullseye-arm64/ $ ../../build.sh

Though it still didn't work for me, xl list doesn't work out as expected yet. Lets discuss this once you are online.

Probably the startup daemons have failed - maybe because it was unable to start QEMU?

On 14-02-22, 15:22, Alex Bennée wrote:

To build on that if:

/etc/init.d/xencommons status

Reports failure

For me, it doesn't matter what I do (xl list is working or not), this command doesn't print anything, success or error.

it's usually because qemu has failed to start. I've just built the latest master and after a re-configure and rebuild of QEMU inside my VM:

../../configure --disable-kvm --disable-tcg --enable-xen --target-list=i386-softmmu

and with that built (and pointed to by /etc/default/xencommons):

If I don't point to the right qemu in this file and do '/etc/init.d/xencommons start', then I do get a failure message saying "QEMU not found or something like that", but xl list still works fine. And of course, I don't get the error if I have the right QEMU path set.

root@bullseye:~/lsrc/qemu.git/builds/xen# /etc/init.d/xencommons start Setting domain 0 name, domid and JSON config... Dom0 is already set up Starting xenconsoled... Starting QEMU as disk backend for dom0 root@bullseye:~/lsrc/qemu.git/builds/xen# xl list Name ID Mem VCPUs State Time(s) Domain-0 0 8192 6 r----- 8799.3