From: Stefan Hajnoczi <stefanha@gmail.com>
To: Paul Schlacter <wlfightup@gmail.com>
Cc: qemu-devel@nongnu.org, Daniel Berrange <berrange@redhat.com>
Subject: Re: [Qemu-devel] use qemu dataplane report '.x-data-plane' not found
Date: Fri, 20 Oct 2017 12:21:58 +0200 [thread overview]
Message-ID: <20171020102158.GH21393@stefanha-x1.localdomain> (raw)
In-Reply-To: <20171016122842.GB10968@redhat.com>
On Mon, Oct 16, 2017 at 01:28:42PM +0100, Daniel P. Berrange wrote:
> On Mon, Oct 16, 2017 at 08:19:36PM +0800, Paul Schlacter wrote:
> > qemu-kvm: -device
> > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1:
> > Property '.x-data-plane' not found
> >
> > What is wrong with this report? is Compiler qemu lost parameters?
>
> This option was deleted almost 2 years ago.
>
> It was only ever a temporary hack to let people do performance testing,
> while the proper long term solution was implemented. It is replaced by
> the 'iothread' concept - see docs/devel/multiple-iothreads.txt
>
> NB any property whose name starts with 'x-' is a temporary hack that is
> liable to be deleted at any time.
In addition to what Dan has posted, libvirt has added domain XML syntax
for IOThreads. That means it's no longer necessary to manually pass
QEMU command-line options if you use libvirt:
https://libvirt.org/formatdomain.html#elementsIOThreadsAllocation
Stefan
prev parent reply other threads:[~2017-10-20 10:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 12:19 [Qemu-devel] use qemu dataplane report '.x-data-plane' not found Paul Schlacter
2017-10-16 12:28 ` Daniel P. Berrange
2017-10-20 10:21 ` Stefan Hajnoczi [this message]
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=20171020102158.GH21393@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wlfightup@gmail.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).