All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Mike Perez <thingee@gmail.com>, Stefan Hajnoczi <stefanha@redhat.com>
Cc: libvir-list@redhat.com, nab@daterainc.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Configure virtio-scsi options via libvirt
Date: Thu, 08 May 2014 10:44:16 +0200	[thread overview]
Message-ID: <536B43E0.4050208@redhat.com> (raw)
In-Reply-To: <20140508072422.GA10416@gmail.com>

Il 08/05/2014 09:24, Mike Perez ha scritto:
> On 10:08 Wed 07 May     , Stefan Hajnoczi wrote:
>> On Tue, May 06, 2014 at 04:13:50PM -0700, Mike Perez wrote:
>>> I would like be able to configure virtio-scsi options num_queues, max_sectors,
>>> and cmd_per_lun via libvirt. Are there any plans to have this support?
>>
>> Hi Mike,
>> I'm not sure about the status of libvirt support for virtio-scsi options
>> but in the meantime you can use <qemu:commandline> passthrough:
>>
>> http://blog.vmsplice.net/2011/04/how-to-pass-qemu-command-line-options.html
>>
>> Stefan
>
> Thanks Stefan,
>
> My plan is to write the support in OpenStack, which unfortunately does not
> accept patches doing qemu passthrough:
>
> http://lists.openstack.org/pipermail/openstack-dev/2013-November/018551.html

Why do you need such fine-grained control?  The higher you go in the 
stack, the simpler configuration should be in my opinion.

For openstack, I think all you need is a singlequeue vs. multiqueue knob 
(setting num_queues = # VCPUs for multiqueue).

Paolo

  reply	other threads:[~2014-05-08  8:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06 23:13 [Qemu-devel] Configure virtio-scsi options via libvirt Mike Perez
2014-05-07  8:08 ` Stefan Hajnoczi
2014-05-08  7:24   ` Mike Perez
2014-05-08  8:44     ` Paolo Bonzini [this message]
2014-05-07  8:24 ` [Qemu-devel] [libvirt] " Ján Tomko
2014-05-08  9:05   ` Daniel P. Berrange

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=536B43E0.4050208@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=libvir-list@redhat.com \
    --cc=nab@daterainc.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=thingee@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.