[Qemu-devel] use qemu dataplane report '.x-data-plane' not found

[Qemu-devel] use qemu dataplane report '.x-data-plane' not found

[Paul Schlacter]

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?

Re: [Qemu-devel] use qemu dataplane report '.x-data-plane' not found

[Daniel P. Berrange]

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.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

Re: [Qemu-devel] use qemu dataplane report '.x-data-plane' not found

[Stefan Hajnoczi]

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