Re: Access GPT partitions on LVM volumes (map entry doesn't fit media)

[Matthias Petermann <mp%petermann-it.de@localhost>]

Hello Brett,

Am 21.07.2020 um 08:24 schrieb Brett Lymn:
> On Sun, Jul 19, 2020 at 06:22:46PM +0200, Matthias Petermann wrote:
> > that sounded promising, but seems to only work with file-based volumes.
> >
> > 	jupiter# vndconfig vnd0 /dev/mapper/rvg0-builder9
> > 	vndconfig: /dev/rvnd0: VNDIOCSET: Operation not supported
> >
> > Thanks anyway - I should take a closer look at LVM - I'm probably scratching
> > the surface too much here. But it was worth a try.
>
> Well, if it is a device already you should be able to vgscan it to find
> the logical volumes.  You may need to tweak the the device filters in
> the lvm.conf to allow vgscan to look into /dev/mapper devices.  The
> trickiest bit is if your volume groups in the vm are the same names as
> the onese on the host but even that is not insurmountable.

thanks for the hint - my setup is even a little easier. I only use LVM 
on the host to provide each Xen VM with exactly one logical volume as a 
"hard disk". In the guest myself I only use GPT, no LVM. Therefore, 
vgscan unfortunately does not help me here - although it is interesting 
to know that this possibility exists.

Best wishes
Matthias