-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Tue, Jan 23, 2018 at 02:39:00PM +0000, Simon Gaiser wrote: > Marek Marczykowski-Górecki: > > Hi, > > > > The "8.4.3pre-shim-comet" branch on xenbits.xen.org/xen.git contains a > > backport of PVH to Xen 4.8 (and comet shim as the top 3-4 patches). In > > practice this is mostly about libxl changes (type="pvh" instead of > > device_model_version="none"), but there are also few fixes for other > > code, like ACPI tables builder. Those do fix some existing minor bugs. > > For example wrongly advertised i8042 controller, causing ~1s delay on > > Linux boot. > > > > It seems like the type="pvh" is what Xen is going to support and > > device_model_version="none" is abandoned in new versions. This means > > that it may be harder to backport further PVH-related patches, and also > > upstream our patches to Xen. There is not much changes on libxl side, > > but still. > > This also means that our libvirt patch in its current shape will be > > rejected, and we'll need to maintain it separately. > > > > Changing this that late in the release cycle may not be a good idea, but > > changing it later, or having to maintain duplicated set of patches > > and having additional difficulty with backporting other patches may also > > be a pain. > > > > Simon, can you take a look at this? What do you think about this? And if > > you think it worth changing it now, please create appropriate pull > > requests. > > I think the deciding factor is whether future 4.8.z releases will > include them (so that we can simply update instead of applying single > patches). But unfortunately this seems to be simply not decided yet [1]. > > If they change it, updating now would be much better because to install > the update libxenlight.so, libvirt and core-admin need to be > synchronized.
Yes, this is exactly why I bring this idea right now. Having synchronized update is always a pain (in some corner cases may lead to removing packages). > Since the mail reads like it's more likely that it will be backported and > AFAICS the change to type=pvh is rather small (so not so hard to > backport if it not ends in the official release) I lean towards > including the backports now. What do you think? Well, change to type=pvh is not exactly small. It's 15-something patches touching different libxl files... But it looks it wasn't that hard to backport it from 4.10 (mostly differences because of libxl.c split), generally the code structure is very similar. So, I also lean towards including it now. > [1]: > https://lists.xenproject.org/archives/html/xen-devel/2018-01/msg02004.html - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlpnTLYACgkQ24/THMrX 1ywaUwf/WtSwMtx2bpDPtgoCJ4HZfKGtiX6iLQ1MKFX4U+dJxzXi7qWlNoWqbqZK /JdPK58GP7W3QcXsHfOUuuiow5dYtHYiFBlOIUVdJSnP3S2dO2q/aAkkmKmozkYB Fr055jLWHQxXfwBmQMru4agxLi+We9dbXYx2aOBuAgeSnYIC4WqUPgLOJYdIfbbO pR3dcBd8MSsyBV9qf2Q4HebTOF84UQfrFZBpHhz3P43dRkqLYSFAUDXvche4u0b3 sa3L92bkbI7sBRb1Hs4aT0NTvPSeCowJx6crhWtm5wOlZuKojRZziEkdKsuZ/cuJ YZa1yX6bJiglXtGKPRtb+wdIG43R5g== =pnuI -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/20180123145446.GJ2653%40mail-itl. For more options, visit https://groups.google.com/d/optout.
