• Bug#1100970: pre-approval: qemu 10.0 for trixie

    From Michael Tokarev@21:1/5 to All on Fri Mar 21 09:10:01 2025
    XPost: linux.debian.devel.release

    Package: release.debian.org
    Severity: normal
    X-Debbugs-Cc: pkg-qemu-devel@lists.alioth.debian.org

    Hi!

    I would like to include upstream qemu version 10.0 in trixie.
    Currently, qemu is at release-candidate stage, 10.0.0-rc0, and
    the actual release is planned for 2025-04-15 (or 2025-04-22 if
    a critical bug is found during the release process) -- the same
    day as the planned freeze of trixie. The upstream release
    schedule is at https://wiki.qemu.org/Planning/10.0 .

    Currrently, qemu 10.0.0-rc0 is uploaded to debian experimental,
    and it works quite well so far. Obviously it is possible to
    discover bugs after the uplstream release too, - this is dealt
    in the upstream stable/bugfix releases, with usual schedule
    about every month.

    The reason why I'd love to have 10.0 in trixie (instead of current
    9.2) is the need to support qemu during the trixie life cycle,
    which means back-porting fixes. Qemu is a fast-moving target
    still, and it is increasingly difficult to support older releases
    for long time. I plan to provide a long-term upstream series for
    the qemu version we will ship in debian trixie.

    Qemu is critical for debian infrastructure, this is why I'd love
    to have as strong support background for it as possible.

    At the same time, possible issues in qemu which are found during
    trixie freeze might require extra efforts from everyone, including
    me as qemu maintainer, and the release team. So there's a risk
    here. On the other hand, qemu from trixie is not used to build
    trixie currently, so the risk shouldn't be that much.

    I plan to upload 10.0.0-rc0 to sid tomorrow, once debci tests
    for the current version in experimental are completed.

    Thanks,

    /mjt

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mathias Gibbens@21:1/5 to All on Fri Mar 21 16:40:01 2025
    XPost: linux.debian.devel.release

    Just a heads up that this might impact Incus/LXD. The release of qemu
    9.2 required several updates due to API changes; I haven't looked at
    qemu 10 at all, so I don't know what sort of changes were made in the
    upcoming release.

    I don't think this should block the upload of qemu to unstable, just
    be aware that updates to Incus/LXD might be needed if issues are found
    as we get further into the trixie freeze.

    Mathias

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEE1Bp60H32xfynSJ8cKe7i1uz0QvkFAmfdhusACgkQKe7i1uz0 QvmdGA//QVNFE1NbRrKV4YZ/SZteabckzHb2hMvgQtcNBdt739OlBgGYiLopK9Bk PuSJJpl9MlI/LCck6e75bojlc7QK8GL9RUEceC2Byl0TqEdF3mvc/3aiFA/IJ5w/ KeqBZZM24nVSZ4EmIADf5mOZrUXCA3nCfZ9fthr/Jd+HhhF63CIWJCFhMvBQB5kx W6SuvjGhXDhXFCuwgfW1kK2jAF/c79o5LCCA22/CRsVcGaq5fjV2o0/50RoMdcVx dkk1EG0OIRZ7VWwZqbI4Igp6IuV8ym/wkTEXI5wnO6uKAS9IiLHe1Qc7wuzTP7Hm qjkQA0jykF5XjMr0mA9jZ6/5J6WgbECW43pP8Kjnpd/5rnaejhbzM4dYQf9EfaHe 3cZzB1PE3KBAyntjFPje+RjGdjTxy1p/YMLv0iXN98KjUWBqIZzL7vQd4+OsV28a 4k01HYh6uQRUC5mRxyMWy7DnpPwyrMeAlSOsST1lcpJz2N4CxzZLku9wGaq76yMw y7NZwauZYQSORcAXWrHqHz/VN2Tr96h+QaznpViGXeCaVSG6ssvJmvHuyOpCoXWC ikwXYrFSQcA+jVQF/6/T06OUmtlrAXKycq21BsOnFgdM8XC/5hWJz9AiVn/r/051 s9jxZcwLXhWb/zgxSRqytDxyfpqw0n5R1PjLArJKzgIrIWeBd/4=
    =ws9x
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mathias Gibbens@21:1/5 to Michael Tokarev on Tue Mar 25 15:00:01 2025
    XPost: linux.debian.devel.release

    On Tue, 2025-03-25 at 12:14 +0300, Michael Tokarev wrote:
    21.03.2025 18:34, Mathias Gibbens wrote:
       Just a heads up that this might impact Incus/LXD. The release of qemu 9.2 required several updates due to API changes; I haven't looked at
    qemu 10 at all, so I don't know what sort of changes were made in the upcoming release.

    I was able to find just one update which had to be done for incus for
    qemu 9.2 - the bootindex json property, which were erroneously marked
    as type string in qemu in the past, and 9.2 fixed this by requiring it
    to be integer, as it should've been.  Which other updates were required?

    Yes, fixing argument typing was one of the larger changes[1], along
    with dealing with the removal of virtfs-proxy-helper[2]. The need to
    fix argument types was an obvious change, but the removal of virtfs- proxy-helper wasn't notice until Colin filed a bug about it. There were
    a couple other smaller updates[3,4] as well.

    I did ping Stéphane, and he said he didn't see anything in the
    deprecation list for the qemu 10 release[5] that looks like it will
    affect Incus, but we'll still want to test things once qemu 10 is
    uploaded to unstable.

    Mathias

    [1] -- https://github.com/lxc/incus/pull/1531
    [2] -- https://github.com/lxc/incus/pull/1547
    [3] -- https://github.com/lxc/incus/pull/1601
    [4] -- https://github.com/lxc/incus/pull/1594
    [5] -- https://www.qemu.org/docs/master/about/deprecated.html

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEE1Bp60H32xfynSJ8cKe7i1uz0QvkFAmfitHEACgkQKe7i1uz0 QvktrxAAlTFnBnIdhCGXTXgm9YBKQDnITnylKen0XBHtNmihGCaC8MXlY5CPLwdY sYF5sP8Nj8gQd2eQ7Abd5Yq98QkcNc9f3VSv559eD7yZum3PbZ8ZOneePNEbijDI uXjLcYZYnS0c9A2HtskpR+avuXG0q97WxdEzW+9gWVorDFaUEuUf9P7alr1igUAX yyQYgOKz6FulbSeb1RruXFxUWXqmxyKWmcOPh5PIpk6dJ/8ePZfDfmBfhCvA1LQr DH4pYaPbAg9KJZnlwkgPflrSe4A8fVonlJwTh/kGMIQ90QXcvrc/9eZoJzpryuoU XS6vTPB8EjHOyt/fPbAmPyHhZIs5y+WR1PbXC3SkAn8fnnQjNip6WEk3Li16kWyu v1CWaGllVvwyD+PjxRMt8LvWvhmCiypraUXQaHij9OPjWaQUlKZqkgnKgSew5OgQ yy9cDiTdtwO0BCo3broevhboHNto1rDt0QDg9YzwTIwoNEGTgvEjSEuIQL9hyoX8 4Na6fnmQnkQea8JCmMU6rYJ3k00pS+xNxpOc+ODmvPYwg8cSZKuULv8srLsmRfzF 8zjU9lAommeQ8SOWE0LnDa5pgQVyPFeGCs5euk0+BWesqymdN6OLOVrc7+2F4+cB 8LY9AWl6EE243TkXCmLXyj/u2XtkKR+ewkQU1ZtYUrxnT0FrSWw=
    =QhNz
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul Gevers@21:1/5 to Michael Tokarev on Thu Mar 27 09:00:01 2025
    XPost: linux.debian.devel.release
    To: 1100970@bugs.debian.org

    This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------AXrWMGcOfo6Sdw0T0lSAXUnZ
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64

    SGkgTWljaGFlbCwNCg0KT24gMjEtMDMtMjAyNSAwOTowMCwgTWljaGFlbCBUb2thcmV2IHdy b3RlOg0KPiBJIHBsYW4gdG8gdXBsb2FkIDEwLjAuMC1yYzAgdG8gc2lkIHRvbW9ycm93LCBv bmNlIGRlYmNpIHRlc3RzDQo+IGZvciB0aGUgY3VycmVudCB2ZXJzaW9uIGluIGV4cGVyaW1l bnRhbCBhcmUgY29tcGxldGVkLg0KDQoNCkRvIEkgdW5kZXJzdGFuZCBjb3JyZWN0bHkgeW91 IGNvbnNpZGVyIHRoaXMgcHJlLWFwcHJvdmFsIHJlcXVlc3QganVzdCANCmZvciB0aGUgY2hh bmdlIGZyb20gMTAuMC4wLXJjKiB0byAxMC4wLjAsIHJpZ2h0PyBBcyAxMC4wLjAtcmMxIGlz IG5vdyBpbiANCnVuc3RhYmxlLg0KDQpQYXVsDQoNCg==

    --------------AXrWMGcOfo6Sdw0T0lSAXUnZ--

    -----BEGIN PGP SIGNATURE-----

    wsB5BAABCAAjFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmflA9IFAwAAAAAACgkQnFyZ6wW9dQra Cgf/WU3OC3k6NG1MPt/iEromrriYP9o/EjIhdWsfuB7qHNt4bnOLmmYmRdCeIltps+fCs9YzLm0Y fh8Ftnn7nRiTRSFJ98gmP7+EMlr164DmE3GE+2KagejBzU3OBuZm41IQW/pZ47k9IaTF2g+vW9aq ateZoLUF75H9nrT8TccTAdC3s72kQ4Zpipf9zBrEKzuI1Lb+8hs441x84jE5g+Q+vsjSP3Mq2osS cuod48tYinYTJBRqd/8I4yOCVoeu9HI/bJ1BPR259AGMR7jtcefROW7JaUaC4AAo9RuC8Qt5xVpI XKBBOpCCy1XxaTG4lbXpJxHrL2lnxVTeJW904vQ4Iw==
    =zotQ
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mathias Gibbens@21:1/5 to All on Wed May 7 23:30:01 2025
    XPost: linux.debian.devel.release

    One minor regression involving NVME hotplugging has been identified;
    I've just opened bug #1104889 about this. While not a show-stopper, it
    does make the use of NVME virtual devices impossible in Incus.

    Mathias

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEE1Bp60H32xfynSJ8cKe7i1uz0QvkFAmgbzc8ACgkQKe7i1uz0 QvmusA/8DGvZHYARPFCZ9r63xP0bs2Jm0A8aP3/+5gzJ0R7F+nVALSi8EXyQY6BR JyQwuHUmvDW9hK6Gdfjqajpy9hVzKsH0ygrP3+RjNzlnwTNZ2pKgwfIg47LYAtVo Q/M4ntHPT0o44WIMd91qbSzdTH9hJZdewi93JiXJqooCX8QWc2ZTl7EW1/oOy93Q zLJTPovCDx0DXH22xJfot5rM8ni/mPaIqaeHhsgI+K+PMSWtKEENrMEc4jg7vufl zpfcICsB7ZcV9brqY9ds7xVn83cE6H8We6MyeXp5B5HXd9w5YebHXSWbP+zENagI ctVNZryNtHBRRtghrf2xbxuGwxAMgsYoS+TIxtDGhQ46Uiexhjg9sbcY+Ye53x3O FkT4e014zBqJUfi7neh31/g6+Sp6E3ZqGab3FmMPn4Cnqp8tDdOpVbVj43gGbcO3 pnoHDiWA6qP8PrHtGYlBr/SBbOyciysM0+VKwKTzWLJVNz78JWS7vKcARHsvVGD1 krqrzLyZ2onpDoskqTjbY1Z0dlZpV1Hw5O63n0UZumAn0qlEJodWEPn24h73hF7k SvK/fLaX3WlhBsJAadccxRmh1BiqQ6rGiZAWpTsHG76SOX//VTahhOk1sesoRlrg tTghd4vi2A2fqlF92lfgswKlyN/Xu5160oVOoLa7KJKDESvDypk=
    =Db63
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)