looking ahead to Buster (deb10) at freeze, deciding Xen version paired to qemu

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

looking ahead to Buster (deb10) at freeze, deciding Xen version paired to qemu

Mark Pryor
List,

Earlier this month I experimented with an NMU build of Xen-4.9 on Stretch

Of course, its only a private build and I would never expect this to get accepted into current Stretch repo. The idea is to move the build from 4.8 to 4.9, with a few improvements, but keep the package partitions, time stamp, and build trees the same.

I've had good results with my NMU build and I use it daily. When I see the effort the Debian qemu team has made to keep qemu-2.8 current with Security fixes my confidence is raised too. I put a hold on the associated qemu-2.8 build (using libxen-4.9 headers) with `apt-mark hold xxyy`.

However, looking at how Buster packaged Xen with qemu makes me think that now and the next 6 months is a chance to change the direction for the better, moving Xen from 4.8.1 to 4.10.3 (eventually in June 2019) and build qemu with libxen-4.10 headers and libs.

Unfortunately, Buster has chosen xen-4.8.1 with qemu-2.10 for now, although I see no reason this choice can't change.

When xen-4.10 is released is when I will start with this project, unless Debian developers start first. There is no reason for me to build or test 4.10 in Buster now. I'm doing this in Ubuntu Artful.

If anyone is interested in any part of this, support or criticism, join us in
##xen-packaging on Freenode

PryMar56



_______________________________________________
Xen-users mailing list
[hidden email]
https://lists.xen.org/xen-users
Reply | Threaded
Open this post in threaded view
|

Re: looking ahead to Buster (deb10) at freeze, deciding Xen version paired to qemu

Mark Pryor
Its so much trouble to coordinate a build of qemu (qemu-system-x86) with the Debian qemu team that I've found a way to split off a qemuu package from the upstream Xen sources, using the Nmu lib/tools configuration.

I kept the same xen_4.9.1.orig.tar.xz tarball, which is minus tools/qemu* & extras/, then I piggy backed in xen_4.9.1.orig-qemuu.tar.xz

The extra tarball was a snapshot from the qemu-xen.git , staging-4.10.
Some new targets add a new binary (*.deb) for qemuu, and it depends on the libxen-4.9 set.

The Nmu design, coding, build, and test took 8 hours over 2 days. I hope this layout can be seriously considered as the future of Xen in Debian Buster (deb10). I think its much improved over what is there now.


any feedback is welcome,
PryMar56

##xen-packaging on Freenode



On Sunday, October 29, 2017 12:13 PM, Mark Pryor <[hidden email]> wrote:


List,

Earlier this month I experimented with an NMU build of Xen-4.9 on Stretch

Of course, its only a private build and I would never expect this to get accepted into current Stretch repo. The idea is to move the build from 4.8 to 4.9, with a few improvements, but keep the package partitions, time stamp, and build trees the same.

I've had good results with my NMU build and I use it daily. When I see the effort the Debian qemu team has made to keep qemu-2.8 current with Security fixes my confidence is raised too. I put a hold on the associated qemu-2.8 build (using libxen-4.9 headers) with `apt-mark hold xxyy`.

However, looking at how Buster packaged Xen with qemu makes me think that now and the next 6 months is a chance to change the direction for the better, moving Xen from 4.8.1 to 4.10.3 (eventually in June 2019) and build qemu with libxen-4.10 headers and libs.

Unfortunately, Buster has chosen xen-4.8.1 with qemu-2.10 for now, although I see no reason this choice can't change.

When xen-4.10 is released is when I will start with this project, unless Debian developers start first. There is no reason for me to build or test 4.10 in Buster now. I'm doing this in Ubuntu Artful.

If anyone is interested in any part of this, support or criticism, join us in
##xen-packaging on Freenode

PryMar56





_______________________________________________
Xen-users mailing list
[hidden email]
https://lists.xenproject.org/mailman/listinfo/xen-users
Reply | Threaded
Open this post in threaded view
|

Re: looking ahead to Buster (deb10) at freeze, deciding Xen version paired to qemu

Mark Pryor
The next step is
xen-4.10+qemu-2.10 Nmu with qemuu as a separate package:


this is a polished source build with enhancements of the original Ubuntu sources.

PryMar56




On Wednesday, December 20, 2017 3:59 PM, Mark Pryor <[hidden email]> wrote:


Its so much trouble to coordinate a build of qemu (qemu-system-x86) with the Debian qemu team that I've found a way to split off a qemuu package from the upstream Xen sources, using the Nmu lib/tools configuration.

I kept the same xen_4.9.1.orig.tar.xz tarball, which is minus tools/qemu* & extras/, then I piggy backed in xen_4.9.1.orig-qemuu.tar.xz

The extra tarball was a snapshot from the qemu-xen.git , staging-4.10.
Some new targets add a new binary (*.deb) for qemuu, and it depends on the libxen-4.9 set.

The Nmu design, coding, build, and test took 8 hours over 2 days. I hope this layout can be seriously considered as the future of Xen in Debian Buster (deb10). I think its much improved over what is there now.


any feedback is welcome,
PryMar56

##xen-packaging on Freenode



On Sunday, October 29, 2017 12:13 PM, Mark Pryor <[hidden email]> wrote:


List,

Earlier this month I experimented with an NMU build of Xen-4.9 on Stretch

Of course, its only a private build and I would never expect this to get accepted into current Stretch repo. The idea is to move the build from 4.8 to 4.9, with a few improvements, but keep the package partitions, time stamp, and build trees the same.

I've had good results with my NMU build and I use it daily. When I see the effort the Debian qemu team has made to keep qemu-2.8 current with Security fixes my confidence is raised too. I put a hold on the associated qemu-2.8 build (using libxen-4.9 headers) with `apt-mark hold xxyy`.

However, looking at how Buster packaged Xen with qemu makes me think that now and the next 6 months is a chance to change the direction for the better, moving Xen from 4.8.1 to 4.10.3 (eventually in June 2019) and build qemu with libxen-4.10 headers and libs.

Unfortunately, Buster has chosen xen-4.8.1 with qemu-2.10 for now, although I see no reason this choice can't change.

When xen-4.10 is released is when I will start with this project, unless Debian developers start first. There is no reason for me to build or test 4.10 in Buster now. I'm doing this in Ubuntu Artful.

If anyone is interested in any part of this, support or criticism, join us in
##xen-packaging on Freenode

PryMar56







_______________________________________________
Xen-users mailing list
[hidden email]
https://lists.xenproject.org/mailman/listinfo/xen-users