On Sun, 2018-07-08 at 06:37 +0200, Cyril Brulebois wrote: [...] > Vincent Caron <vincent@zerodeux.net> (2018-07-06): [...] > > If this module makes it to netinst's initrd, one would use those kvm > > args: > > > > -chardev file,path=virtiocon0.log,id=virtiocon0 > > -device virtio-serial > > -device virtconsole,chardev=virtiocon0 > > > > ... and in the guest a /dev/hvc0 would appear. Anything the guest would > > write to /dev/hv0 would en up in the host's vitriocon0.log file. > > So it seems we're talking about kernel/drivers/char/virtio_console.ko > that could be added to either the serial-modules udeb or the > virtio-modules one. Kernel maintainers, what do you think? > > This might be worth backporting to stretch too. I can send patches when > you've selected the udeb we should be adding this module to. I would say virtio-modules. All the virtio class drivers depend on virtio and virtio_ring, which means that adding them to any other package would require that package to depend on virtio-modules. (The Xen-specific drivers don't have this issue only because xenbus unfortunately has to be built-in.) Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein
Attachment:
signature.asc
Description: This is a digitally signed message part