Hi Ian, after our conversation on IRC in #debian-xen today, I updated the packaging to the latest 4.10-stable commit (since there's no 4.10.1 release yet) and smoke-tested the package on a testing/unstable dom0 running a PVHv2 guest. Can you please review and sponsor the upload of a first Xen 4.10 package to Debian unstable? The work which has been done to arrive at this point from the previous 4.8 packages is visible at: https://salsa.debian.org/xen-team/debian-xen/commits/master The source package built from that commit (see README.source about how), and signed with my GPG key, ...32180C2A55 is available at: https://syrinx.knorrie.org/~knorrie/xen/ After uploading, we should notify the qemu team to trigger a rebuild of their packages, which will pick up the libxen build dependency. Thanks, Hans -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20180222/cbae4346/attachment.sig>
Hi Hans, First of all, thanks for the great work! I was wondering about a patch I tried to send in a while ago which enables OVMF. It?s a single line in the rules setup and doesn?t have any build-time or run-time dependencies until you actually change a domU configuration to use OVMF. Currently I just rebuild all packages locally and add the line to debian/rules.real: --enable-ovmf --with-system-ovmf=/usr/share/ovmf/OVMF.fd Is this something that could be added to 4.10? Regards, John> On 22 Feb 2018, at 00:57, Hans van Kranenburg <hans at knorrie.org> wrote: > > Hi Ian, > > after our conversation on IRC in #debian-xen today, I updated the > packaging to the latest 4.10-stable commit (since there's no 4.10.1 > release yet) and smoke-tested the package on a testing/unstable dom0 > running a PVHv2 guest. > > Can you please review and sponsor the upload of a first Xen 4.10 package > to Debian unstable? > > The work which has been done to arrive at this point from the previous > 4.8 packages is visible at: > > https://salsa.debian.org/xen-team/debian-xen/commits/master > > The source package built from that commit (see README.source about how), > and signed with my GPG key, ...32180C2A55 is available at: > > https://syrinx.knorrie.org/~knorrie/xen/ > > After uploading, we should notify the qemu team to trigger a rebuild of > their packages, which will pick up the libxen build dependency. > > Thanks, > Hans > > _______________________________________________ > Pkg-xen-devel mailing list > Pkg-xen-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-xen-devel
Hi, On 02/22/2018 01:03 AM, John Keates wrote:> > First of all, thanks for the great work! I was wondering about a patch I tried to send in a while ago which enables OVMF. It?s a single line in the rules setup and doesn?t have any build-time or run-time dependencies until you actually change a domU configuration to use OVMF. > > Currently I just rebuild all packages locally and add the line to debian/rules.real: > > --enable-ovmf --with-system-ovmf=/usr/share/ovmf/OVMF.fd > > Is this something that could be added to 4.10?I guess so. Which packages are your rebuilding? The 4.8 ones or are you creating something based on the new 4.10 packages? I can rtfm https://wiki.xenproject.org/wiki/OVMF but can you also provide some kind of recipe how to set up a tl;dr domU using this as a test case? If so, I can already test it myself already also. For me, the most beautiful thing would be if you send a patch that applies on top of https://salsa.debian.org/xen-team/debian-xen master branch with a test report telling "it works \o/" (explaining what actually works) when running a build made from that (see README.source how to create a package). It's just that there are so many things you can do with Xen, and I don't remotely want to give the impression I understand all of them. (I've been running Xen at work since 2006 but still discovering many new things). Also, another logical question would be if you're willing to help handling future debian bug reports that are related to OVMF after we enable it. ;-) Hans