From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: errors from VHOST on shutdown. Date: Tue, 23 Oct 2018 08:56:58 -0700 Message-ID: <20181023085658.10aa5301@xeon-e3> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org To: Maxime Coquelin , Tiwei Bie Return-path: Received: from mail-pf1-f196.google.com (mail-pf1-f196.google.com [209.85.210.196]) by dpdk.org (Postfix) with ESMTP id 4B0941B1F3 for ; Tue, 23 Oct 2018 17:57:02 +0200 (CEST) Received: by mail-pf1-f196.google.com with SMTP id u12-v6so879007pfn.12 for ; Tue, 23 Oct 2018 08:57:02 -0700 (PDT) List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" I get errors on shutdown of application using virtio-user. For example, quitting testpmd: Detaching a port... vhost_kernel_set_backend(): VHOST_NET_SET_BACKEND fails, Operation not permitted vhost_kernel_set_backend(): VHOST_NET_SET_BACKEND fails, Operation not permitted vhost_kernel_ioctl(): VHOST_RESET_OWNER failed: Operation not permitted Everything works fine, but not good to have this kind of thing visible to user. These error messages should be fixed, or the error message removed. How do you want to handle it?