[libvirt-users] enabling virtio-scsi-data-plane in libvirt
Can somebody knows how to enable virtio-scsi-data-plane in libvirt for specific domain? I know that i need to replace "-device virtio-scsi-pci" with "-object iothread,id=io1 -device virtio-scsi-pci,iothread=io1" in qemu, but how can i do this in libvirt? -- Vasiliy Tolstov, e-mail: v.tolstov@selfip.ru
On 11/18/2015 05:44 AM, Vasiliy Tolstov wrote:
Can somebody knows how to enable virtio-scsi-data-plane in libvirt for specific domain?
I know that i need to replace "-device virtio-scsi-pci" with "-object iothread,id=io1 -device virtio-scsi-pci,iothread=io1" in qemu, but how can i do this in libvirt?
Check out virsh iothread{info|pin|add|del} and of course the corresponding virDomain{Add|Pin|Del}IOThread and virDomainGetIOThreadInfo. John
2015-11-19 16:09 GMT+03:00 John Ferlan <jferlan@redhat.com>:
Check out virsh iothread{info|pin|add|del} and of course the corresponding virDomain{Add|Pin|Del}IOThread and virDomainGetIOThreadInfo.
Yes, thanks! Does in near feature libvirt devs integrate this ability to domain format? As i understand all qemu stable features supported by libvirt. And data plane for virtio-blk is stable for some time.... -- Vasiliy Tolstov, e-mail: v.tolstov@selfip.ru
On 11/30/2015 02:58 AM, Vasiliy Tolstov wrote:
2015-11-19 16:09 GMT+03:00 John Ferlan <jferlan@redhat.com>:
Check out virsh iothread{info|pin|add|del} and of course the corresponding virDomain{Add|Pin|Del}IOThread and virDomainGetIOThreadInfo.
Yes, thanks! Does in near feature libvirt devs integrate this ability to domain format? As i understand all qemu stable features supported by libvirt. And data plane for virtio-blk is stable for some time....
Such as? http://libvirt.org/formatdomain.html#elementsIOThreadsAllocation and usage within <cputune> as <iothreadpin> or <iothreadsched> John
2015-11-30 14:17 GMT+03:00 John Ferlan <jferlan@redhat.com>:
Such as?
http://libvirt.org/formatdomain.html#elementsIOThreadsAllocation
and usage within <cputune> as <iothreadpin> or <iothreadsched>
So you mean that if i define iothread in domain xml and create virtio-scsi it automatic enables virtio-scsi-data-plane? -- Vasiliy Tolstov, e-mail: v.tolstov@selfip.ru
On 11/30/2015 06:23 AM, Vasiliy Tolstov wrote:
2015-11-30 14:17 GMT+03:00 John Ferlan <jferlan@redhat.com>:
Such as?
http://libvirt.org/formatdomain.html#elementsIOThreadsAllocation
and usage within <cputune> as <iothreadpin> or <iothreadsched>
So you mean that if i define iothread in domain xml and create virtio-scsi it automatic enables virtio-scsi-data-plane?
As long as the qemu you're using supports the "-object iothread", then this works. I forget the exact version it went into qemu. John
2015-11-30 14:32 GMT+03:00 John Ferlan <jferlan@redhat.com>:
As long as the qemu you're using supports the "-object iothread", then this works. I forget the exact version it went into qemu.
Nice! Thanks! (i'm use latest qemu) how can i check that data-plane used by virtio-scsi ? -- Vasiliy Tolstov, e-mail: v.tolstov@selfip.ru
On 11/30/2015 07:06 AM, Vasiliy Tolstov wrote:
2015-11-30 14:32 GMT+03:00 John Ferlan <jferlan@redhat.com>:
As long as the qemu you're using supports the "-object iothread", then this works. I forget the exact version it went into qemu.
Nice! Thanks! (i'm use latest qemu) how can i check that data-plane used by virtio-scsi ?
oh - um... Hold that thought... *scsi* not yet supported (I think changes only recent went into qemu, but it hasn't been on my list of things to follow closely. *pci* is supported Gotta read more closely sometimes... John
participants (2)
-
John Ferlan -
Vasiliy Tolstov