On Thu, Jul 23, 2020 at 02:15:07PM +0200, Cornelia Huck wrote:
> On Thu, 23 Jul 2020 13:57:08 +0200
> David Hildenbrand wrote:
>
> > On 23.07.20 08:33, Cornelia Huck wrote:
> > > On Mon, 20 Jul 2020 11:07:51 +0200
> > > David Hildenbrand wrote:
> > >
> > >> On 20.07.20 11:03, Michael S.
On Thu, 23 Jul 2020 13:57:08 +0200
David Hildenbrand wrote:
> On 23.07.20 08:33, Cornelia Huck wrote:
> > On Mon, 20 Jul 2020 11:07:51 +0200
> > David Hildenbrand wrote:
> >
> >> On 20.07.20 11:03, Michael S. Tsirkin wrote:
> >>> On Mon, Jul 20, 2020 at 10:09:57AM +0200, David Hildenbrand
On 23.07.20 08:33, Cornelia Huck wrote:
> On Mon, 20 Jul 2020 11:07:51 +0200
> David Hildenbrand wrote:
>
>> On 20.07.20 11:03, Michael S. Tsirkin wrote:
>>> On Mon, Jul 20, 2020 at 10:09:57AM +0200, David Hildenbrand wrote:
On 07.07.20 12:54, Cornelia Huck wrote:
> As discussed in
On Mon, 20 Jul 2020 11:54:06 +0200
Halil Pasic wrote:
> On Tue, 7 Jul 2020 12:54:44 +0200
> Cornelia Huck wrote:
>
> > As discussed in "virtio-fs: force virtio 1.x usage", it seems like
> > a good idea to make sure that any new virtio device (which does not
> > support legacy virtio) is
On Mon, 20 Jul 2020 11:07:51 +0200
David Hildenbrand wrote:
> On 20.07.20 11:03, Michael S. Tsirkin wrote:
> > On Mon, Jul 20, 2020 at 10:09:57AM +0200, David Hildenbrand wrote:
> >> On 07.07.20 12:54, Cornelia Huck wrote:
> >>> As discussed in "virtio-fs: force virtio 1.x usage", it seems
On Tue, 7 Jul 2020 12:54:44 +0200
Cornelia Huck wrote:
> As discussed in "virtio-fs: force virtio 1.x usage", it seems like
> a good idea to make sure that any new virtio device (which does not
> support legacy virtio) is indeed a non-transitional device, just to
> catch accidental
On 20.07.20 11:03, Michael S. Tsirkin wrote:
> On Mon, Jul 20, 2020 at 10:09:57AM +0200, David Hildenbrand wrote:
>> On 07.07.20 12:54, Cornelia Huck wrote:
>>> As discussed in "virtio-fs: force virtio 1.x usage", it seems like
>>> a good idea to make sure that any new virtio device (which does
On Mon, Jul 20, 2020 at 10:09:57AM +0200, David Hildenbrand wrote:
> On 07.07.20 12:54, Cornelia Huck wrote:
> > As discussed in "virtio-fs: force virtio 1.x usage", it seems like
> > a good idea to make sure that any new virtio device (which does not
> > support legacy virtio) is indeed a
On 07.07.20 12:54, Cornelia Huck wrote:
> As discussed in "virtio-fs: force virtio 1.x usage", it seems like
> a good idea to make sure that any new virtio device (which does not
> support legacy virtio) is indeed a non-transitional device, just to
> catch accidental misconfigurations. We can
On Tue, 7 Jul 2020 12:54:44 +0200
Cornelia Huck wrote:
> As discussed in "virtio-fs: force virtio 1.x usage", it seems like
> a good idea to make sure that any new virtio device (which does not
> support legacy virtio) is indeed a non-transitional device, just to
> catch accidental
As discussed in "virtio-fs: force virtio 1.x usage", it seems like
a good idea to make sure that any new virtio device (which does not
support legacy virtio) is indeed a non-transitional device, just to
catch accidental misconfigurations. We can easily compile a list
of virtio devices with legacy
11 matches
Mail list logo