All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: QEMU Developers <qemu-devel@nongnu.org>,
	Dmitry Fleytman <dmitry.fleytman@gmail.com>,
	Jason Wang <jasowang@redhat.com>
Cc: Yuri Benditovich <yuri.benditovich@daynix.com>,
	Andrew Melnychenko <andrew@daynix.com>,
	Leonid Bloch <leonid@daynix.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Alexander Bulekov <alxndr@bu.edu>
Subject: Is QEMU's vmxnet3 still being used?
Date: Wed, 18 Aug 2021 15:42:23 +0200	[thread overview]
Message-ID: <7ec1626e-3c4b-c9e8-1a29-f576163712f5@redhat.com> (raw)


  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

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?

  Thomas



             reply	other threads:[~2021-08-18 13:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18 13:42 Thomas Huth [this message]
2021-08-19  8:21 ` Is QEMU's vmxnet3 still being used? Jason Wang
2021-08-19  8:32   ` Yan Vugenfirer
2021-08-19  8:53 ` Daniel P. Berrangé
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=7ec1626e-3c4b-c9e8-1a29-f576163712f5@redhat.com \
    --to=thuth@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.