> For the install time, isn't it trivial to use regular ide/sata cdrom > drive or an usb flash instead of more exotic ways?
trivial? I don't know how to do that, and it does feel like a workaround. > Most of the time cdrom is only needed for the > installation, later on you can either > remove it entirely or switch it to virtio if needed. What about QA infrastructure that might want to do installs of various iso images, and do testing, or boot live CDs, for testing. Would scripts require extra special cases for every architecture? > we always use most common devices What does that mean? virtio is very much common. How is the user of qemu supposed to know which is the "most common device"? Are we going to maintain the proper flags for every architecture in the installation guide? It is an honest question. Please note that If one uses the most obvious way of supplying iso image, that is `-cdrom debian-testing-arm64-netinst.iso`, it also doesn't work: qemu-system-aarch64 -M virt -cpu max -smp 2 -m 8192 -device qemu-xhci,id=usb -usb -device usb-kbd -device usb-tablet -device virtio-gpu-pci -cdrom debian-testing-arm64-netinst.iso -bios /usr/share/qemu-efi-aarch64/QEMU_EFI.fd I don't find this exotic at all, and rather straightforward, and probably the first thing user will try. Thanks, Witold On Tue, 22 Dec 2020 at 04:31, Michael Tokarev <m...@tls.msk.ru> wrote: > > 22.01.2020 09:18, Witold Baryluk wrote: > > Package: debian-installer > > Followup-For: Bug #689528 > > > > Dear Maintainer, > > > > any progress on this, I still have this issue. > > Out of curiosity, _why_ this is necessary? > For the install time, isn't it trivial to use regular ide/sata cdrom > drive or an usb flash instead of more exotic ways? Most of the time > cdrom is only needed for the installation, later on you can either > remove it entirely or switch it to virtio if needed. > > We did lots of installations of various systems out there in qemu/kvm, > and we always use most common devices during this time. > > Thanks, > > /mjt
