[opensuse-virtual] "duplicate name" VolumeGroup conflicts between DomUs? same as Fedora bug?
in creating multiple DomU's, i create a 'template' DomU, popluate & configure it as desired, then 'dd' it to new DomUs. the 'template' is autoyast configured, with partitioning, /dev/xvda mount=/boot label="BOOT" fs=ext3 vg0 lv_swap mount=swap label="SWAP" fs=swap lv_root mount=/ label="ROOT" fs=ext3 after boot, @ DomU, df -H Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg0-lv_root 3.6G 1.9G 1.5G 57% / udev 275M 82k 275M 1% /dev /dev/xvda1 104M 20M 79M 20% /boot vgs VG #PV #LV #SN Attr VSize VFree vg0 1 2 0 wz--n- 3.88G 64.00M lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert lv_root vg0 -wi-ao 3.31G lv_swap vg0 -wi-ao 512.00M after dd-ing this 'template'to multiple DomUs, @ Dom0, i get vgs WARNING: Duplicate VG name vg0: VKj8x5-ZKxX-9Nyv-TOAj-LT00-aNiT-t08maO (created here) takes precedence over zGm1oc-7Xu9-3A5i-jY7V-o8We-TJu6-z6RiMx WARNING: Duplicate VG name vg0: VKj8x5-ZKxX-9Nyv-TOAj-LT00-aNiT-t08maO (created here) takes precedence over zGm1oc-7Xu9-3A5i-jY7V-o8We-TJu6-z6RiMx WARNING: Duplicate VG name vg0: Existing VKj8x5-ZKxX-9Nyv-TOAj-LT00-aNiT-t08maO (created here) takes precedence over zGm1oc-7Xu9-3A5i-jY7V-o8We-TJu6-z6RiMx Couldn't find device with uuid 'z9TpKD-MQwQ-l5aB-wInc-DnMb-E4Lc-yMfd8s'. Couldn't find all physical volumes for volume group vg0. Couldn't find device with uuid 'z9TpKD-MQwQ-l5aB-wInc-DnMb-E4Lc-yMfd8s'. Couldn't find all physical volumes for volume group vg0. Volume group "vg0" not found WARNING: Duplicate VG name vg0: VKj8x5-ZKxX-9Nyv-TOAj-LT00-aNiT-t08maO (created here) takes precedence over zGm1oc-7Xu9-3A5i-jY7V-o8We-TJu6-z6RiMx Couldn't find device with uuid 'XvoxVH-Hnmj-PtIW-qgDK-C0sI-6aN0-7qL3eQ'. Couldn't find all physical volumes for volume group vg0. Couldn't find device with uuid 'XvoxVH-Hnmj-PtIW-qgDK-C0sI-6aN0-7qL3eQ'. Couldn't find all physical volumes for volume group vg0. Volume group "vg0" not found WARNING: Duplicate VG name vg0: VKj8x5-ZKxX-9Nyv-TOAj-LT00-aNiT-t08maO (created here) takes precedence over zGm1oc-7Xu9-3A5i-jY7V-o8We-TJu6-z6RiMx VG #PV #LV #SN Attr VSize VFree VG_Dom0 1 1 0 wz--n- 11.97G 0 VG_DomU 1 8 0 wz--n- 220.22G 163.22G VG_Swap 1 1 0 wz--n- 480.00M 0 it looks like UUID conflicts between DomUs' VGs -- namely, multiple instances of the VG=vg0, one in each DomU. i thought that DomUs' partitioning etc would be isolated from one another; apparently not, in that Dom0 seems to (need to?) be aware of the DomU VGs' name/UUID. what do i need to do to prevent these VG name/UUID conflicts? there's a Fedora bug that seems related, "Bug 207470 - Need ability to handle duplicate VG names for Xen" https://bugzilla.redhat.com/show_bug.cgi?id=207470 is this the same problem? -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
On Mon, 09 Feb 2009, 18:36:31 +0100, PGNet wrote:
in creating multiple DomU's, i create a 'template' DomU, popluate & configure it as desired, then 'dd' it to new DomUs.
the 'template' is autoyast configured, with partitioning,
/dev/xvda mount=/boot label="BOOT" fs=ext3 vg0 lv_swap mount=swap label="SWAP" fs=swap lv_root mount=/ label="ROOT" fs=ext3
after boot, @ DomU,
df -H Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg0-lv_root 3.6G 1.9G 1.5G 57% / udev 275M 82k 275M 1% /dev /dev/xvda1 104M 20M 79M 20% /boot
vgs VG #PV #LV #SN Attr VSize VFree vg0 1 2 0 wz--n- 3.88G 64.00M
lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert lv_root vg0 -wi-ao 3.31G lv_swap vg0 -wi-ao 512.00M
after dd-ing this 'template'to multiple DomUs, @ Dom0, i get
You need to exclude the device(s), where the 'template' and the domUs are stored on, from the list of devices which will be scanned by LVM in dom0. The list is actually defined in /etc/lvm/lvm.conf, further details can be found at its manual page lvm.conf(5). HTH, cheers. l8er manfred -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
On Mon, Feb 9, 2009 at 10:00 AM, Manfred Hollstein <manfred@die-hollsteins.de> wrote:
You need to exclude the device(s), where the 'template' and the domUs are stored on, from the list of devices which will be scanned by LVM in dom0. The list is actually defined in /etc/lvm/lvm.conf, further details can be found at its manual page lvm.conf(5).
aha. hadn't seen that yet. looks like the filter = [ ... ] in /etc/lvm/lvm.conf is what needs to be tweaked. that seems a proper workaround. thanks. i'm a bit confused as to why/how Dom0's lvm is even 'seeing' the VG='vg0' defined in an unmounted/unstarted DomU. i thought Dom0 was only supposed to be aware "of" its DomUs -- not their contents (e.g., their partitioning, VGs, etc etc) just trying to be sure to understand the "separation" between Dom0/DomU ... -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
On Mon, 09 Feb 2009, 19:09:01 +0100, PGNet wrote:
On Mon, Feb 9, 2009 at 10:00 AM, Manfred Hollstein <manfred@die-hollsteins.de> wrote:
You need to exclude the device(s), where the 'template' and the domUs are stored on, from the list of devices which will be scanned by LVM in dom0. The list is actually defined in /etc/lvm/lvm.conf, further details can be found at its manual page lvm.conf(5).
aha. hadn't seen that yet. looks like the
filter = [ ... ]
in /etc/lvm/lvm.conf is what needs to be tweaked. that seems a proper workaround. thanks.
No, it's _not_ a workaround, it's the proper solution!
i'm a bit confused as to why/how Dom0's lvm is even 'seeing' the VG='vg0' defined in an unmounted/unstarted DomU.
The dom0 doesn't even know about a domU's resources, but if these resources are under control of the dom0, hmmm... In your case the files containing the LVM signatures (which are scanned for when /etc/init.d/boot.lvm runs) *will* be found unless you exclude them from this process.
i thought Dom0 was only supposed to be aware "of" its DomUs -- not their contents (e.g., their partitioning, VGs, etc etc)
Again, the storage used for your domUs is just plain visible for LVMs scanning routine...
just trying to be sure to understand the "separation" between Dom0/DomU ...
HTH, cheers. l8er manfred -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
On Mon, Feb 9, 2009 at 11:22 AM, Manfred Hollstein <manfred@die-hollsteins.de> wrote:
No, it's _not_ a workaround, it's the proper solution!
got it. for my case, i've on /dev/md0 -> '/boot' /dev/md1 -> VG('VG_Swap'):LV('LV_SWAP'):'swap' /dev/md2 -> VG('VG_Dom0'):LV('LV_ROOT'):'/' /dev/md3 -> VG('VG_DomU'):LV('work'):'/home/work' :LV('xen'):'/home/xen' (fwiw, i keep my xen configs here) reading lvm.conf (& man), using the default lvm.conf's 'filter = [...]', @ rm /etc/lvm/.cache && vgs WARNING: Duplicate VG name vg0:... <------ WARNINGS etc ... VG_Dom0 ... VG_DomU ... VG_Swap ... changing to, filter =[ "a|/dev/md[12]|", "r|.*|" ] i.e., *excluding* /dev/md3 containing VG_DomU, @, rm /etc/lvm/.cache && vgs VG_Dom0 ... VG_Swap ... as expected. but, of course, since i create new xen DomU images in/on VG_DomU's remaining space, dd, lvcreate -n new_DomU -L 4G /dev/VG_DomU dd if=/dev/VG_DomU/domu_template of=/dev/VG_DomU/new_DomU @ 'dd', Volume group "VG_DomU" not found since the /dev/md3 block dev, on which VG_DomU resides, is not included iiuc, the 'filter=' specification filters on block-devices only, not VG/LV names (at least i've not figured out a regex that works, yet). yet, the UUID/name conflicts I'm seeing _are_ on names. _can_ i exclude the DomU images from scanning by LVM @ 'xm create' time if they share a block-dev with other VG's that are to be scanned? if yes, what regex would work here? given your comment,
In your case the files containing the LVM signatures (which are scanned for when /etc/init.d/boot.lvm runs) *will* be found unless you exclude them from this process.
it seems i can/might exclude individual files? -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
renaming all DomU LV's used as either phy: or file: in configs to have a common name prefix, e.g. "xenvm_", then filtering on "r|/dev/.*xenvm_.*|" and "r|/dev/.*dm-.*|" did the trick. the latter was not immediately obvious; apparently, there are symlinks from the DomUs' LV-names to these /dev/dm-* paths. if not specifically, excluded they, too, are scanned. no more reported conflicts @ 'lvm' scans. now, to see if anything else broke ... and whether there are additional problems when multiple VMs are built/launched. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
participants (2)
-
Manfred Hollstein -
PGNet