hi,
i'm fiddling around with LVM backed KVM raw disks, that i want to use
_directly_ in oVirt virtualization (as "Direct LUN"). i would like to
avoid "importing", dd, etc. if possible. in the KVM origin system exists
a mapping of one iSCSI whole device (no partitions) to one PV to one VG
to o
Dne 13.7.2017 v 15:25 Matthias Leopold napsal(a):
hi,
i'm fiddling around with LVM backed KVM raw disks, that i want to use
_directly_ in oVirt virtualization (as "Direct LUN"). i would like to avoid
"importing", dd, etc. if possible. in the KVM origin system exists a mapping
of one iSCSI who
On Thu, 13 Jul 2017, Zdenek Kabelac wrote:
PV has 'header' so the real 'data' are shifted by PV header+lvm2 metadata.
and also LV does not need to be sequential.
However if you have been having a single 'segment' LV and and you calculate
proper skipping offset (typically 1MB) you can try to us
Am 2017-07-13 17:25, schrieb Zdenek Kabelac:
Dne 13.7.2017 v 15:25 Matthias Leopold napsal(a):
hi,
i'm fiddling around with LVM backed KVM raw disks, that i want to use
_directly_ in oVirt virtualization (as "Direct LUN"). i would like to
avoid "importing", dd, etc. if possible. in the KVM or
Hello Zdenek,
Thursday, July 13, 2017, 17:25:10, you wrote:
> However if you have been having a single 'segment' LV and and you calculate
> proper skipping offset (typically 1MB) you can try to use such device directly
> without lvm2 with a loop device mapping - see losetup --offset option - but
On 07/13/2017 09:25 AM, Matthias Leopold wrote:
> i'm fiddling around with LVM backed KVM raw disks, that i want to use
> _directly_ in oVirt virtualization (as "Direct LUN"). i would like to
> avoid "importing", dd, etc. if possible. in the KVM origin system
> exists a mapping of one iSCSI whole d
