[Bug 247098] Initscript Review
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=247098
Richard W.M. Jones <rjones(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |CLOSED
Version|9 |rawhide
Resolution| |RAWHIDE
--- Comment #4 from Richard W.M. Jones <rjones(a)redhat.com> 2008-09-09 09:26:33 EDT ---
xenconsoled - OK
xend - OK
xendomains - OK
xenstored - OK
All OK, so closing with RAWHIDE.
--
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.
15 years, 8 months
[Bug 207470] Need ability to handle duplicate VG names for Xen
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=207470
--- Comment #12 from Dave Wysochanski <dwysocha(a)redhat.com> 2008-09-08 14:23:18 EDT ---
Agreed - I've got a setup myself and have been playing with maintenance on my
own guest images so I feel the pain!
I'm looking into better solutions such as the code detecting duplicate names
and perhaps add something (part of the UUID?) to remove the ambiguity. Making
such an LV usable (for maintenance) would require modification of the device
mapper namespace but not the on-disk metadata, so this needs some thought and
maybe a special option.
--
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.
15 years, 8 months
[Bug 207470] Need ability to handle duplicate VG names for Xen
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=207470
--- Comment #11 from Stephen Tweedie <sct(a)redhat.com> 2008-09-08 09:41:43 EDT ---
That virtualisation-guide recipe is precisely what won't work with default
volume group naming conventions.
As for renaming volume groups, yes, that may provide one solution. But as
noted it does risk leaving an image unbootable; and as a general principle of
system diagnosis/recovery, users should not have to significantly reconfigure
their disks just in order to be able to perform maintenance on them.
--
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.
15 years, 8 months