[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#689528: please add virtio support for cdrom at install time



On Mon, Dec 10, 2018 at 11:38:33AM +0100, Stefan Sperling wrote:
>On Sat, Aug 11, 2018 at 01:20:53PM +0100, Ben Hutchings wrote:
>> On Mon, 17 Mar 2014 03:32:41 +0100 Cyril Brulebois <kibi@debian.org> wrote:
>> > I suspect all we need is to add virtio-modules-${kernel:Version} to
>> > pkg-lists/cdrom/<arch>.cfg files. Quoting for example the amd64 one:
>> 
>> I agree.  This should be done for at least amd64 and i386.  It is
>> probably sensible for all architectures where virtio-modules is built.
>
>This bug also prevents installation of Debian in OpenBSD's native
>vmm(4) hypervisor: https://man.openbsd.org/vmm
>
>The vmm hypervisor only provides virtio devices. Installation of Debian
>with a netinstall image fails in the same way as described above.
>
>OpenBSD users who want to use Debian in vmm currently have to install
>Debian in Qemu and then boot the installed system in vmm. This works
>around the problem but it is very inconvenient.

Looking to add these changes, as I've had similar requests from other
people too. But I'm struggling to get my qemu to actually boot such an
image! My command line is

$ qemu-system-x86_64 -enable-kvm -m 2048 \
  -drive file=efi-hard-disk.img,if=virtio,format=raw \
  -drive file=/scratch/mirror/debian-cd-test/debian-10.0-SBHACK-amd64-NETINST-1.iso,if=virtio,media=cdrom,boot=on

"""
Booting from DVD/CD...
Boot failed: Could not read from CDROM (code 0003)
Booting from Floppy...
Boot failed: could not read the boot disk

Booting from Hard Disk...
...

and then things hang. What am I missing? If I remove the "if=virtio"
from both drive stanzas, I at least get to the isolinux menu.

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
"I've only once written 'SQL is my bitch' in a comment. But that code 
 is in use on a military site..." -- Simon Booth


Reply to: