From: "Stuart D. Gathman" <stuart@bmsi.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: giovanni_re <john_re@fastmail.us>
Subject: Re: [linux-lvm] Disk Partitioning tools, GUI preferably- best for LVM Logical Volume Management ; jor
Date: Mon, 26 Jul 2010 08:16:54 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.1007260805250.3000@bmsred.bmsi.com> (raw)
In-Reply-To: <4C4D4B47.8000201@redhat.com>
On Mon, 26 Jul 2010, Bryn M. Reeves wrote:
> On 07/24/2010 04:28 AM, giovanni_re wrote:
> > So, I've got that big LV 4th partition, with empty space (2TB drive),
> > and now I want to create some more linux partitions so I can install
> > some other distros.
>
> If you want VMs then partitioning an LV makes sense. You present the
> entire LV as a virtual disk to the guest and the emulated devices appear
> to that OS as a regular partitioned disk. This is a very common technique.
Using Xen modified OSes, you don't need to partition the LVs. The
xen storage driver presents each mapped block device as a virtual
partition.
> If you want to boot these directly on the hardware however you might
> want to reconsider your approach. Partitioned LVs are not supported
> out-of-the box by any distro that I know of. I think you would need to
> mess around with custom boot scripts to get the system to boot properly
> and you'll probably need to do some special tricks to get a standard
> distro installer to install onto these partitioned LVs. You would also
> need to figure out a way of sharing a /boot partition (on the physical
> disk) between all the installed distributions to avoid conflicts since
> PC BIOS boot support does not handle LVM devices.
Booting multiple LVM supporting OSes works fine with LVM. Have a LV for the
root filesystem of each Linux OS, and have them all on the Grub menu.
Make the /boot partition extra large. I do this with every laptop
and desktop as SOP. Make Fedora upgrades much less fearful.
If necessary, you can boot non LVM OSes installed in a DOS partition
via a chain menu entry in grub. (e.g. boot Windows)
> If this is your goal then you might find it easier to allocate a single
> LV to each new installation and use that directly. With a bit of fancy
> footwork in grub (and as long as each distro supports installation to an
> existing LVM2 volume group) I think this should work and would be easier
> and simpler to set up.
If every distro sticks to reasonable naming conventions in /boot (so
that they don't step on each others kernels), then it all works fine.
--
Stuart D. Gathman <stuart@bmsi.com>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
next prev parent reply other threads:[~2010-07-26 12:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-24 3:28 [linux-lvm] Disk Partitioning tools, GUI preferably- best for LVM Logical Volume Management ; jor giovanni_re
2010-07-24 4:39 ` Stuart D. Gathman
2010-07-24 16:54 ` Harald Heigl
2010-07-26 8:45 ` Bryn M. Reeves
2010-07-26 12:16 ` Stuart D. Gathman [this message]
2010-07-26 12:43 ` Bryn M. Reeves
2010-07-26 13:59 ` Stuart D. Gathman
2010-07-26 14:04 ` Bryn M. Reeves
2010-07-26 16:48 ` Stuart D. Gathman
2010-07-26 22:32 ` [linux-lvm] Disk Partitioning tools, - for having multi distros bootable - " giovanni_re
2010-07-28 18:10 ` Stuart D Gathman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.1007260805250.3000@bmsred.bmsi.com \
--to=stuart@bmsi.com \
--cc=john_re@fastmail.us \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).