From: Stefan Hajnoczi <stefanha@gmail.com>
To: Bug 1558175 <1558175@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1558175] [NEW] virtio: vm killed (Guest moved used index)
Date: Thu, 17 Mar 2016 15:10:14 +0000 [thread overview]
Message-ID: <20160317151014.GR14062@stefanha-x1.localdomain> (raw)
In-Reply-To: <20160316172207.18045.92202.malonedeb@gac.canonical.com>
[-- Attachment #1: Type: text/plain, Size: 1688 bytes --]
On Wed, Mar 16, 2016 at 05:22:07PM -0000, Julien Meunier wrote:
> I ran a DPDK application with virtio ports. If I killed and relaunched it, VM is
> killed by qemu with the following message:
> > qemu-system-x86_64: Guest moved used index from 571 to 0
>
> If I ran the same application with e1000 ports, I haven't this issue.
>
> Network topology
> ================
>
> I used two VM machines with last qemu-2.5 with two virtio-net netdevs. Both
> netdevs are connected through a VDE switch.
>
> On testnode, I used a Debian 8 (3.16) and virtio-net linux drivers. On DUT, I
> used a Ubuntu 14.04 (3.13) with DPDK (next/16_04) with virtio pmd.
>
> (Topology in attachment, launchpad does not support ascii-art)
>
> Steps
> =====
>
> 1. Start a DPDK application using virtio ports
> 2. Send traffic over those ports (using ping flood ...)
> 3. Kill this DPDK application (sending SIGKILL, making it crash etc...)
> 4. Restart this DPDK application with the same configuration
> 5. During EAL initialization, if an incoming packet is received on a virtio
> port, qemu exits (error code 1) with the following message:
> > qemu-system-x86_64: Guest moved used index from 571 to 0
The DPDK application is not using the virtio-net device correctly. QEMU
will abort if the driver (application) is out of sync with the device.
The application probably needs to do an explicit virtio device reset in
order to reinitialize the vrings.
This ungraceful exit isn't pretty but it is shows there is a bug with
the driver. Please contact the application authors to fix the
application (it must reset the device explicitly to initialize it).
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-03-17 15:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 17:22 [Qemu-devel] [Bug 1558175] [NEW] virtio: vm killed (Guest moved used index) Julien Meunier
2016-03-16 17:24 ` [Qemu-devel] [Bug 1558175] " Julien Meunier
2016-03-17 15:10 ` Stefan Hajnoczi [this message]
2016-03-17 15:56 ` Laszlo Ersek (Red Hat)
2016-03-18 9:45 ` Stefan Hajnoczi
2016-03-18 11:30 ` Laszlo Ersek
2016-03-17 16:00 ` Laszlo Ersek (Red Hat)
2016-03-17 16:01 ` Laszlo Ersek (Red Hat)
2016-03-18 10:04 ` Julien Meunier
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=20160317151014.GR14062@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=1558175@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/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).