Hi, @ThierryEscande, thanks for the input here。

It is pretty interesting that I kind also located the same place by following the interrupter path.
https://github.com/liayan/xen-xcp-ng/blob/main/xen/common/domain.c#L250

It quite fits our case atm that issues happened after hitting the limit of 64. Unfortunately, I can not test it yet because our host is stuck in a weird POST status. Will update here later.

Just out of curiosity, I am wondering what is qemu-dp used for. I saw the qemu is more fit for the version in xcp-ng. On the other side, I did see qemu-dp is forked from qemu though.

https://github.com/xcp-ng-rpms/qemu-dp
https://github.com/xcp-ng-rpms/qemu

@olivierlambert , just a project.

@stormi said in could not build xen from xcp-ng-build-env:

git-lfs

You saved my day, big thanks!

Hi @olivierlambert, I just want to re-compile our 8.2 xcp-ng platforms, more specifically, Xen and xapi, want to add some customised stuff. This is my first time compiling xcp-ng, I have no issue with compiling pure Xen though. It would be great if you have such documents too. Thanks in advance.

@lyan samething with xapi compiling

Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.YPjnjY
+ umask 022
+ cd /home/builder/rpmbuild/BUILD
+ cd /home/builder/rpmbuild/BUILD
+ rm -rf xapi-1.249.32
+ /usr/bin/tar -xf /home/builder/rpmbuild/SOURCES/xen-api-1.249.32.tar.gz
/usr/bin/tar: This does not look like a tar archive

gzip: stdin: not in gzip format
/usr/bin/tar: Child returned status 1
/usr/bin/tar: Error is not recoverable: exiting now
error: Bad exit status from /var/tmp/rpm-tmp.YPjnjY (%prep)

@lyan I already changed Xen branch to 8.2

Complete!
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.F8NBO4
+ umask 022
+ cd /home/builder/rpmbuild/BUILD
+ cd /home/builder/rpmbuild/BUILD
+ rm -rf xen-4.13.5
+ /usr/bin/tar -xf /home/builder/rpmbuild/SOURCES/xen-4.13.5.tar.gz
/usr/bin/tar: This does not look like a tar archive

gzip: stdin: not in gzip format
/usr/bin/tar: Child returned status 1
/usr/bin/tar: Error is not recoverable: exiting now
error: Bad exit status from /var/tmp/rpm-tmp.F8NBO4 (%prep)

./run.py -b 8.2 --build-local ../xen --no-exit

I am wondering if this is a known issue.

@olivierlambert nice, out of curiosity, what is the rough timeline for the 9.0 release,

Thanks for the reply, @olivierlambert. I recently hit a bug that Xen could not create msi interrupt for HVM, I noticed that we qemu-dm is using pc-0.1 as the machine model by default, as the starter, I kind of want to change it to i440fx-4.2 which is aligned to the qemu version. I can not change it from the cmd line atm, maybe it is hard-wired in the code?

With default xcp-ng 8.2, I saw the hvm is created with "qemu-dm-3 -machine pc-0.10,accel=xen,"

I checked xe vm-param-setthat there is no such option change "-machine", I tried "other-config" got no such key error.

I am new to xcp-ng, wondering if there is a way to change the machine model for qemu, such as "pc-i440fx-42".

Thanks.

Hi, I saw we are still using 4.13.5-10.42.1 version of Xen in beta, however, I noticed that there was plan to use 4.17.x by https://en.wikipedia.org/wiki/XCP-ng. I am wondering what is the roadmap of xen in xcp-ng eventually? Do we have upgrade plan for Xen?