All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	Alex Fishman <alex.fishman@ravellosystems.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	yvugenfi@redhat.com, Izik Eidus <izik.eidus@ravellosystems.com>,
	qemu-devel@nongnu.org,
	Dmitry Fleytman <dmitry.fleytman@ravellosystems.com>,
	pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/5] VMWare PVSCSI paravirtual device implementation
Date: Thu, 15 Mar 2012 11:54:31 +0000	[thread overview]
Message-ID: <20120315115431.GH2388@redhat.com> (raw)
In-Reply-To: <CAJSP0QWGb+n3hmBp37N_Mahtopqw+wieKFi+6a3wsZ4bswZPLA@mail.gmail.com>

On Thu, Mar 15, 2012 at 11:47:29AM +0000, Stefan Hajnoczi wrote:
> On Thu, Mar 15, 2012 at 9:02 AM, Dmitry Fleytman
> <dmitry.fleytman@ravellosystems.com> wrote:
> > Below is the implementation of VMWare PVSCSI device and
> > command line parameters to configure vendor name and product name
> > for SCSI storage are implemented.
> > Latter is needed to make PVSCSI storage devices look exactly as
> > on VMWare hypervisors.
> >
> > With this and VMWARE3 patches V2V migration problem for VMWare
> > images should be solved relatively easy.
> 
> What is the V2V strategy?
> 
> Supporting these devices is fine if we have a way to convert guests to
> use virtio.  But if the plan is to keep the guests on VMware pv
> devices, then that will split the development effort on support and
> optimizing I/O devices.  All the performance work going into
> virtio-net (vhost-net), virtio-blk, and possibly virtio-scsi isn't
> easy to duplicate for VMware pv devices.  Also, we cannot extend
> VMware devices easily while retaining compatibility.
> 
> I'm for supporting these devices, but we really need another step to
> move migrated guests onto virtio - otherwise users will be
> disappointed with KVM's support/performance.  Can you explain a bit
> how you want these devices to be used?

FWIW, there is a v2v tool that is able to update guest images to
port them from VMware to KVM, which covers changing the drivers,
but also a bunch of other things

  http://libguestfs.org/virt-v2v/


I can still see value in natively supporting the VMWare PV devices
though, since it could facilitate people who just want to try out
pre-built appliance images which were designed only to use those
devices.

Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  reply	other threads:[~2012-03-15 11:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15  9:02 [Qemu-devel] [PATCH 0/5] VMWare PVSCSI paravirtual device implementation Dmitry Fleytman
2012-03-15  9:02 ` [Qemu-devel] [PATCH 1/5] Utility function strpadcpy() added Dmitry Fleytman
2012-03-15  9:53   ` Paolo Bonzini
2012-03-18  9:22     ` Dmitry Fleytman
2012-03-15  9:02 ` [Qemu-devel] [PATCH 2/5] Vendor name and product name parameters for SCSI devices Options "vendor_name" and "product_name" added for SCSI disks Dmitry Fleytman
2012-03-15  9:55   ` Paolo Bonzini
2012-03-18  9:24     ` Dmitry Fleytman
2012-03-15  9:02 ` [Qemu-devel] [PATCH 3/5] Header with various utility functions shared by VMWARE SCSI and network devices Dmitry Fleytman
2012-03-15  9:56   ` Paolo Bonzini
2012-03-18  9:23     ` Dmitry Fleytman
2012-03-15  9:02 ` [Qemu-devel] [PATCH 4/5] PVCSI paravirtualized device implementation Dmitry Fleytman
2012-03-15  9:02 ` [Qemu-devel] [PATCH 5/5] PVSCSI paravirtualized device integration Bus type "pvscsi" added Dmitry Fleytman
2012-03-15  9:46   ` Paolo Bonzini
2012-03-18  9:15     ` Dmitry Fleytman
2012-03-15 11:47 ` [Qemu-devel] [PATCH 0/5] VMWare PVSCSI paravirtual device implementation Stefan Hajnoczi
2012-03-15 11:54   ` Daniel P. Berrange [this message]
2012-03-15 11:54   ` Paolo Bonzini
2012-03-15 12:29   ` Avi Kivity
2012-03-18  8:31 ` Gerhard Wiesinger
2012-03-18  8:32 ` Gerhard Wiesinger
2012-03-18 12:33   ` Evgeny Budilovsky
  -- strict thread matches above, loose matches on Subject: below --
2012-03-15 21:29 Dmitry Fleytman

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=20120315115431.GH2388@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.fishman@ravellosystems.com \
    --cc=aliguori@us.ibm.com \
    --cc=dmitry.fleytman@ravellosystems.com \
    --cc=izik.eidus@ravellosystems.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=yvugenfi@redhat.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.