[Rationale]
virt-manager 3.2 is out for more than a year now and upstream git includes many fixes.
That was brought up upstream in [1] already and the estimation is somewhere around our feature freeze [2]. But we also need time to do this in Debian and test it and so on, therefore to be transparent and prepared I wanted to file an FFe bug right away.
There was no release by upstream in time before Feature Freeze.
But now there is [3] v4.0.0 since last week.
In addition many of the changes in there are also needed for bug 1959976 [4]
And finally today's virt-manager (3.2) in jammy would be an FTBFS without some fixes that are in 4.0 (due to the much newer libvirt version we have) - just another motivation to move to the new version.
[Proposed upload]
Since the release last week Debian packaged 4.0 (thanks).
I have test built this for jammy in a PPA [5].
The full diff out of that is available there [6].
No Delta needed - once the FFe is approved I'd sync the package.
[Tests]
The package has self tests on its own at build and autopkgtest.
On that PPA [5] I was then also running the autopkgtests which passed on all architectures [7-11] on autopkgtest infrastructure.
There are not too many reverse dependencies that we could break, actually just cockpit-machines and image-factory (for virtinst).
- The options used in image-factory (just one call to virt-install) all are still present.
- The calls from cockpit-machines do proper feature checking (app.jsx) to only use what is present and it seems to be ready for the new version.
The tests it has are integration tests not run at build/autopkgtest time so I have no results of them available atm. I have installed cockpit on jammy and run a guest install with the new virt-inst. I saw cockpit spawning
4 0 32881 32860 20 0 303116 90172 poll_s Sl ? 0:01 \_ /usr/bin/python3 /usr/bin/virt-install --connect qemu:///system --quiet --name test --os-variant ubuntu20.04 --memory 2048 --wait -1 --noautoconsole --disk size=8,format=qcow2 --graphics vnc,listen=127.0.0.1 --graphics spice,listen=127.0.0.1 --install os=ubuntu20.04 --unattended profile=jeos,admin-password-file=/tmp/cockpit-machines-756m3w3a-admin-password,user-login=ubuntu,user-password-file=/tmp/cockpit-machines-iuri0r6_-user-password
That successfully created a guest
root@j:~# virsh list --all
Id Name State
----------------------
1 test running
I selected an unattended install which seemed to work fine with the new virt-manager. I attached a screenshot of that [14]
Upgrade log of virt-inst can be found at [12]
Install log of virt-manager can be found at [13]
[References]
[1]: https://listman.redhat.com/archives/virt-tools-list/2022-January/msg00016.html
[2]: https://listman.redhat.com/archives/virt-tools-list/2022-January/msg00017.html
[3]: https://github.com/virt-manager/virt-manager/releases/tag/v4.0.0
[4]: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1959976
[5]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4802/+packages
[6]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4802/+files/virt-manager_1%3A3.2.0-3.1_1%3A4.0.0-1ubuntu1~jammyppa2.diff.gz
[7]: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ci-train-ppa-service-4802/jammy/amd64/v/virt-manager/20220310_090145_cd4f0@/log.gz
[8]: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ci-train-ppa-service-4802/jammy/arm64/v/virt-manager/20220310_090149_9209e@/log.gz
[9]: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ci-train-ppa-service-4802/jammy/armhf/v/virt-manager/20220310_085939_9209e@/log.gz
[10]: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ci-train-ppa-service-4802/jammy/ppc64el/v/virt-manager/20220310_090213_a7fb9@/log.gz
[11]: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ci-train-ppa-service-4802/jammy/s390x/v/virt-manager/20220310_085546_00842@/log.gz
[12]: https://paste.ubuntu.com/p/2S2jmJrxQf/
[13]: https://paste.ubuntu.com/p/xfGFwWG4gs/
[14]: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1961027/+attachment/5567651/+files/virt-inst-4.0-from-cockpit-jammy.png
Can we pre-acknowledge that way to go, or do you (ubuntu-release) need/want to wait until there is a new release and I can provide that usual requested PPA build, full Diff and install log?