As James-san already answered, target to be controlled by the pvSCSI
is SCSI hardware device. The pvSCSI backend cannot and doesn't
recognize "volume" layer, for example fdisk or LVM, and "file system"
layer, for example a file on ext3.
On Thu, 29 May 2008 21:02:25 +1000
"James Harper" <james.harper@xxxxxxxxxxxxxxxx> wrote:
> > Hi Jun,
> > Could you please tell us if it will be possible to "export" a LVM
> > as a SCSI drive? Or maybe I shall ask, would it make sense? If not, is
> > your pvSCSI implementation only efficient when there's an actual
> > scsi device on the dom?
> It wouldn't make sense. I can't think of any advantage to turning a
> block device into a scsi device for that purpose. The windows xenvbd
> driver does this on the windows side, but only because it appears to be
> the best way to present a disk device to Windows.
> The pvSCSI is a passthrough mechanism for 'sg' devices (eg /dev/sgX) and
> allows the passing through of raw scsi commands. Great for CD burners,
> tape drives, scanners (do SCSI scanners still exist???) and other
> non-block-device devices, but not necessary for lvm backed or file
> backed block devices.
> Did you have a particular reason in mind? Maybe you thought of something
> I didn't :)
Xen-devel mailing list