On Tue, 2018-07-10 at 02:32 +0200, Cyril Brulebois wrote:
> Control: reassign -1 src:linux
> Control: tag -1 patch
>
> Ben Hutchings (2018-07-09):
> > I would say virtio-modules. All the virtio class drivers depend on
> > virtio and virtio_ring, which means that adding them to any other
> >
Control: reassign -1 src:linux
Control: tag -1 patch
Ben Hutchings (2018-07-09):
> 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
On Sun, 2018-07-08 at 06:37 +0200, Cyril Brulebois wrote:
[...]
> Vincent Caron (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
Hi Vincent,
Vincent Caron (2018-07-06):
> Package: debian-installer-9-netboot-amd64
> Severity: wishlist
> Tags: d-i
>
> Dear Maintainer,
>
> while automating Debian image creations thru netinst + KVM, I stumbled
> upon a limitation from the emulated UARTs (if one sends back from the
> guest
Package: debian-installer-9-netboot-amd64
Severity: wishlist
Tags: d-i
Dear Maintainer,
while automating Debian image creations thru netinst + KVM, I stumbled
upon a limitation from the emulated UARTs (if one sends back from the
guest to the host large logs, it might overrun the UART buffer
5 matches
Mail list logo
