From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: [PATCH 0/5] vhost-scsi: Add support for host virtualized target Date: Mon, 28 Jan 2013 15:11:33 +0200 Message-ID: <20130128131133.GA15108@redhat.com> References: <1347000499-28701-1-git-send-email-nab@linux-iscsi.org> <20130117164314.GA19458@redhat.com> <1358456841.18551.48.camel@haakon2.linux-iscsi.org> <20130121085034.GA31047@redhat.com> <510676B5.4070209@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <510676B5.4070209@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org To: Paolo Bonzini Cc: Stefan Hajnoczi , kvm-devel , Jan Kiszka , qemu-devel , Zhi Yong Wu , Anthony Liguori , target-devel , lf-virt , Christoph Hellwig List-Id: virtualization@lists.linuxfoundation.org On Mon, Jan 28, 2013 at 02:01:41PM +0100, Paolo Bonzini wrote: > Il 21/01/2013 09:50, Michael S. Tsirkin ha scritto: > >> Unfortunately, I've not been able to get back to the conversion > >> requested by Paolo for a standalone vhost-scsi PCI device. > > > > It doesn't have to be a standalone device. A vhost=on frontend > > option is also OK I think. Paolo, any objections? > > Sorry, I missed this message. > > I asked for a standalone device because the configuration mechanism > (configfs vs. command-line) and the feature set are completely > different. Unlike virtio-net, it's not possible to switch one to the > other at run time. > > Paolo Exactly the same applies to any other frontend option. For example if you have two qemu instances with different num_queues values you can not migrate one to the other. So in this sense it is not different from any other frontend option, right? -- MST