FYI: can be tested and verified on Canonistack arm64 instance.
As expected:
$ virt-install --name test --ram 1024 --vcpus 2 --disk size=16 --location https://ftp.debian.org/debian/dists/bullseye/main/installer-arm64/ --osinfo debian11 --graphics none --tpm none --boot uefi
...
ERROR internal error: process exited while connecting to monitor: 2022-09-12T06:29:45.846337Z qemu-system-aarch64: Failed to lock byte 100
Domain installation does not appear to have been successful.
With the fix installed we get into an UEFI shell in the guest, there then is a lack of further progress but that is something else (due to the trivial setup used). The problem reported here is fixed by the change as expected.
FYI: can be tested and verified on Canonistack arm64 instance.
As expected: /ftp.debian. org/debian/ dists/bullseye/ main/installer- arm64/ --osinfo debian11 --graphics none --tpm none --boot uefi 12T06:29: 45.846337Z qemu-system- aarch64: Failed to lock byte 100
$ virt-install --name test --ram 1024 --vcpus 2 --disk size=16 --location https:/
...
ERROR internal error: process exited while connecting to monitor: 2022-09-
Domain installation does not appear to have been successful.
In Journal: arm64-libvirt- aavmf-1989078 kernel: audit: type=1400 audit(166296418 5.843:40) : apparmor="DENIED" operation= "file_lock" profile= "libvirt- 10bfeb48- 3d08-4c92- a959-c1f27b2419 78" name="/ usr/share/ AAVMF/AAVMF_ CODE.fd" pid=6034 comm="qemu- system- aar" requested_mask="k" denied_mask="k" fsuid=64055 ouid=0 arm64-libvirt- aavmf-1989078 libvirtd[4970]: internal error: qemu unexpectedly closed the monitor: 2022-09- 12T06:29: 45.846337Z qemu-system- aarch64: Failed to lock byte 100
Sep 12 06:29:45 cpaelzer-
Sep 12 06:29:45 cpaelzer-
With the fix installed we get into an UEFI shell in the guest, there then is a lack of further progress but that is something else (due to the trivial setup used). The problem reported here is fixed by the change as expected.
Uploading as Jammy SRU ...