From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 780C3C4338F for ; Thu, 19 Aug 2021 08:33:52 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id BF382610FA for ; Thu, 19 Aug 2021 08:33:51 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org BF382610FA Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=nongnu.org Received: from localhost ([::1]:39374 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mGdUk-0006Wc-Mc for qemu-devel@archiver.kernel.org; Thu, 19 Aug 2021 04:33:50 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:37460) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mGdTv-0005r7-BF for qemu-devel@nongnu.org; Thu, 19 Aug 2021 04:32:59 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:32037) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mGdTt-0005Tm-I7 for qemu-devel@nongnu.org; Thu, 19 Aug 2021 04:32:59 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1629361975; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=sAr3cAp32u+B5DTGCL4SloiPKELrBlFwYsZPpbkB75k=; b=Ut5mBtuvLzhwc2VUBtB+2TJt88mnEkaklo9R0ekv1A8u5dOgaUnbzaZMaZ1FUSgKwKF0ya IYcmGS1PSzNxmUcU5jbVfiWb3qjbgGH3+Iq7e06svdehPakM+95o9XJXzZqXOVikPHDRg6 G54HGIxm9QIIDZBcIepqVRrTxrWBFjI= Received: from mail-lj1-f199.google.com (mail-lj1-f199.google.com [209.85.208.199]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-179-t9ZH0I3tMeaZNLn0C2UrXw-1; Thu, 19 Aug 2021 04:32:53 -0400 X-MC-Unique: t9ZH0I3tMeaZNLn0C2UrXw-1 Received: by mail-lj1-f199.google.com with SMTP id 7-20020a05651c12c7b029019545e8e9c2so1890513lje.4 for ; Thu, 19 Aug 2021 01:32:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=sAr3cAp32u+B5DTGCL4SloiPKELrBlFwYsZPpbkB75k=; b=B+88+cXerlXkEK0bky0SDstZNTytuVd1Kkr19NYUpTh6isMy3kGsa50WUh8jfYwnXn 2a/Pst9i8dPCDaC6TVrZHXbTt/uXGBvjlPgnsn3s9ykXNBjfJAa6nmkiBZ+8sacyz81x 0hX1Zb5wGLiUIll7ipyakppElVz3SrSddh6557G2IJ7TgalaUHKoFmf+XW01gZ41joJM mRjLuM6bihrJRXyYedM1MsyAARCNlNkmFeEQ9n7UT7TLCyQ4jlzVnzJ29TJ6JvqYVH2N 5ccVcDHOsTigebWfDx9Ilp2YKPTv0huPDxCkouI6oZCqLEflV6QAAfoQietHcAUXKjwt Re2w== X-Gm-Message-State: AOAM5307J+V5fjnfCYRr0T93dQHGlyVrqAfGSQPyEfLNyGqlzoNCyX45 4jgzZQIjluXslqlGnkyukQXiK5uUJWajgJLL5pz1GWJw3ArYWF1RFHSambTaD/KfPZ4aLkmC/Yd fxOk+AI/CPmLlLAtXUMy34l93Nw9GhIc= X-Received: by 2002:a05:6512:3b14:: with SMTP id f20mr5994585lfv.614.1629361971885; Thu, 19 Aug 2021 01:32:51 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz9f08olii+hcsasAgCP9iVnvgwo0SAEGq8A1qdjnw4mFNTgBj6lN33nTWC86FZEyqeH2aKFfwXpg/x1MvdXAE= X-Received: by 2002:a05:6512:3b14:: with SMTP id f20mr5994568lfv.614.1629361971645; Thu, 19 Aug 2021 01:32:51 -0700 (PDT) MIME-Version: 1.0 References: <7ec1626e-3c4b-c9e8-1a29-f576163712f5@redhat.com> In-Reply-To: From: Yan Vugenfirer Date: Thu, 19 Aug 2021 11:32:40 +0300 Message-ID: Subject: Re: Is QEMU's vmxnet3 still being used? To: Jason Wang Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=yvugenfi@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: multipart/alternative; boundary="00000000000087e3ef05c9e56509" Received-SPF: pass client-ip=216.205.24.124; envelope-from=yvugenfi@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -34 X-Spam_score: -3.5 X-Spam_bar: --- X-Spam_report: (-3.5 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.7, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Thomas Huth , Dmitry Fleytman , Yuri Benditovich , Leonid Bloch , Andrew Melnychenko , QEMU Developers , Alexander Bulekov , Stefan Hajnoczi Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" --00000000000087e3ef05c9e56509 Content-Type: text/plain; charset="UTF-8" Hi All, I know it is used to develop DPDK support on Windows right now. Previously it was used for different nested virtualization scenarios as well. Best regards, Yan. On Thu, Aug 19, 2021 at 11:22 AM Jason Wang wrote: > On Wed, Aug 18, 2021 at 9:42 PM 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 > > > > 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? > > I guess it might have been used for virt-v2v in the past. > > But I'm not sure what's the status now. > > Thanks > > > 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 > > > > > --00000000000087e3ef05c9e56509 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi All,

I know it is used to develop DP= DK support on Windows right now.=C2=A0
Previously it was used for= different nested virtualization scenarios as well.

Best regards,
Yan.

On Thu, Aug 19, 2021 at 11:22 AM Jason = Wang <jasowang@redhat.com>= wrote:
On Wed, Aug 18, 2021 at 9:42 PM Thomas Hu= th <thuth@redhat.c= om> wrote:
>
>
>=C2=A0 =C2=A0Hi all,
>
> I recently noticed that we have quite a bunch of tickets against the v= mxnet3
> device in our bug trackers, which indicate that this device could be u= sed to
> crash QEMU in various ways:
>
>=C2=A0 =C2=A0ht= tps://gitlab.com/qemu-project/qemu/-/issues?state=3Dopened&search=3Dvmx= net3
>
>=C2=A0 =C2=A0https://bugs.launchpad.ne= t/qemu?field.searchtext=3Dvmxnet3
>
> 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?

I guess it might have been used for virt-v2v in the past.

But I'm not sure what's the status now.

Thanks

> If there are still many
> users of this device, is there anybody interested here in helping to g= et
> these crashes fixed in the near future? Otherwise, should we maybe rat= her
> mark this device as deprecated and remove it in a couple of releases? = What
> do you think?
>
>=C2=A0 =C2=A0Thomas
>


--00000000000087e3ef05c9e56509--