in Incus 6.16 a new function to connect iso files was merged, see
lxc/incus#1835
and the commands to use it to connect disks to a vm
https://discuss.linuxcontainers.org/t/io-bus-usb-in-incus-6-16/24701/9
This somewhat dramatically simplifies the usage of iso files (especially for Windows VMs). It effectively skips the requirement to repack the iso with distrobuilder since it allows the user to connect multiple iso files to the same VM in a simple enough way. So you can connect one iso with the installer and the iso with the virtio drivers to be used during installation.
I think this should be the default way to handle ISOs from GUI. So you upload a iso file and it just ends up in the storage volume without any modification, either as a file or written to a block device (lvm volume or whatever, depending on what the storage is). Then the instance creation menu lets you attach attach iso files to a VM using this io.bus=usb feature to pass the raw file or block device as-is.
in Incus 6.16 a new function to connect iso files was merged, see
lxc/incus#1835
and the commands to use it to connect disks to a vm
https://discuss.linuxcontainers.org/t/io-bus-usb-in-incus-6-16/24701/9
This somewhat dramatically simplifies the usage of iso files (especially for Windows VMs). It effectively skips the requirement to repack the iso with distrobuilder since it allows the user to connect multiple iso files to the same VM in a simple enough way. So you can connect one iso with the installer and the iso with the virtio drivers to be used during installation.
I think this should be the default way to handle ISOs from GUI. So you upload a iso file and it just ends up in the storage volume without any modification, either as a file or written to a block device (lvm volume or whatever, depending on what the storage is). Then the instance creation menu lets you attach attach iso files to a VM using this io.bus=usb feature to pass the raw file or block device as-is.