qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Andrew Melnychenko <andrew@daynix.com>,
	Dmitry Fleytman <dmitry.fleytman@gmail.com>,
	Alexander Bulekov <alxndr@bu.edu>,
	Jason Wang <jasowang@redhat.com>,
	Leonid Bloch <leonid@daynix.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Yuri Benditovich <yuri.benditovich@daynix.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: Is QEMU's vmxnet3 still being used?
Date: Thu, 19 Aug 2021 09:53:08 +0100	[thread overview]
Message-ID: <YR4b9J7jlfrd84BK@redhat.com> (raw)
In-Reply-To: <7ec1626e-3c4b-c9e8-1a29-f576163712f5@redhat.com>

On Wed, Aug 18, 2021 at 03:42:23PM +0200, Thomas Huth wrote:
> 
>  Hi all,
> 
> I recently noticed that we have quite a bunch of tickets against the vmxnet3
> device in our bug trackers, which indicate that this device could be used to
> crash QEMU in various ways:
> 
>  https://gitlab.com/qemu-project/qemu/-/issues?state=opened&search=vmxnet3
> 
>  https://bugs.launchpad.net/qemu?field.searchtext=vmxnet3

IIUC, all except 3 of those bugs, are issues from the device fuzzer.

It is nice that we find those, but if we don't consider this a device
targetted at virtualization use cases, I don't think they're a reason
to remove the device.

> Having hardly any knowledge about this device and its usage at all, I wonder
> how much it is still used out there in the wild? If there are still many
> users of this device, is there anybody interested here in helping to get
> these crashes fixed in the near future? Otherwise, should we maybe rather
> mark this device as deprecated and remove it in a couple of releases? What
> do you think?

We've got countless NIC models in QEMU most of which have minimal users,
are possibly buggy, not actively maintained, but exist to support
non-virtualization use cases. We've especially not had "how many users
are there" as a criteria for acceptance or removal of a device.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  parent reply	other threads:[~2021-08-19  8:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18 13:42 Is QEMU's vmxnet3 still being used? Thomas Huth
2021-08-19  8:21 ` Jason Wang
2021-08-19  8:32   ` Yan Vugenfirer
2021-08-19  8:53 ` Daniel P. Berrangé [this message]
2021-08-19  9:37   ` Peter Maydell
2021-08-24  6:14     ` Markus Armbruster
2021-08-24  6:14   ` Markus Armbruster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YR4b9J7jlfrd84BK@redhat.com \
    --to=berrange@redhat.com \
    --cc=alxndr@bu.edu \
    --cc=andrew@daynix.com \
    --cc=dmitry.fleytman@gmail.com \
    --cc=jasowang@redhat.com \
    --cc=leonid@daynix.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=thuth@redhat.com \
    --cc=yuri.benditovich@daynix.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).