On Mon, 17 Mar 2014 03:32:41 +0100 Cyril Brulebois <kibi@debian.org> wrote:
[...]
> I suspect the following happens:
> - when booting on non-virtio cdrom, udebs are detected on the cdrom
> and/or on the network, loaded, and the virtio-modules kernel udeb is
> then loaded, and non-cdrom resources work fine (nic, hard disk).
> - when booting with virtio cdrom, the relevant module hasn't been put
> in the initramfs, so cdrom isn't detected at all, and game over.
Richard just ran into this again.
> 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.
[...]
> I haven't played much with virtio myself, but I could probably provide
> you with an amd64 netinst image for test purposes. Do you want to
> perform some tests?
I can test this easily.
Ben.
--
Ben Hutchings
Time is nature's way of making sure that
everything doesn't happen at once.
Attachment:
signature.asc
Description: This is a digitally signed message part