[Bug 207470] Need ability to handle duplicate VG names for Xen

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Need ability to handle duplicate VG names for Xen


https://bugzilla.redhat.com/show_bug.cgi?id=207470





------- Additional Comments From sct at redhat.com  2008-06-06 12:24 EST -------
> The bug in comment #1 has been fixed for at least RHEL 5.1 and 5.2; vgchange now
> accepts a UUID to specify the target volume group.  So, to get at the volumes of
> a virtual host, you can use kpartx/vgscan/vgchange/vgrename in sequence.

That works in dire emergency, but has the disadvantage of rendering the guest
unbootable in the process --- if you change the guest vgname, the initrd won't
be able to find the root filesystem.

> if anaconda detects that it is
> occurring within a paravirtualized install, or if the hardware it detects in the
> system looks suspiciously like the hardware Xen would present to an HVM guest,
> use a different automatic LVM volume naming scheme than "VolGroup00" (e.g.,
> "VVolGroup00".)  Or consider using /dev/urandom to generate a portion of the
> suggested volume group names randomly.

That would be ideal, but I think it came up before and was rejected by the
installer folks.  It's also too late for existing installs, of course; and we
still need to be able to support installs of old OS versions that don't do this.



-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.