On 10/25/2013 07:04 PM, Adam Williamson wrote:
On Wed, 2013-10-23 at 15:07 -0600, Chris Murphy wrote:
On Oct 23, 2013, at 2:44 PM, Gene Czarcinski <gene@xxxxxxxxx> wrote:
On 10/21/2013 11:00 AM, Chris Murphy wrote:
Sometimes using UUID is not a good idea. This problem has been bugzill'ed. I was hoping the "swap-fix" would help with that but I believe it will not.
So then the question is, if the disk is GPT, can/should systemd use UniquePartitionGUID in the GPT for swap partitions rather than the swap volume format UUID? The UniquePartitionGUID is more stable.
Is there some underground movement to switch to GPT disks? Doing a little googling, I found this:
https://fedoraproject.org/wiki/Features/GUID_Partition_Table
which says the targeted release was Fedora 14 and thus it went nowhere.
I am not sure that anaconda is prepared to handle this?
Mmm, it was put in for F14 or F15 and then rolled back out for BIOS
computers because there were too many instances of BIOS firmware doing
a face plant without its beloved MBR. Many such instances are worked
around with the pmbr_boot flag (parted terminology) which is setting
the active flag on the 0xEE entry in the MBR, which is what you get if
you use the gpt flag when booting install media. Otherwise MBR is used
for BIOS computers.
Went in in F16, came out in F17. gpt is still the default for UEFI
installs and used when formatting a disk over 2TB in size. You can force
a BIOS install to use gpt by passing the 'gpt' kernel parameter.
I was not previously aware of that. Since we are all going to be
honored with EUFI "real soon now", I thought I would give gpt a try
now. I cracked up one of my "standard" simple KVM kickstart test
installs for F19 but specified gpt on the boot line (this was a fresh
install wiping the virtual disk). Looked good until the end when
grub2-install failed because it could not install into the gparted disk.
Then, I rebooted and again specified gpt on the boot line but did a
regular install with auto partitioning ... that worked and got this
special, small "grub_bios" partition.
OK, another try but lets do custom partitioning ... it would not let me
proceed until I allocated a 1 MB "bootbios" partition (I specified that
as the mountpoint). OK, now I wanted to look at anaconda-ks.cfg to see
want anaconda used to specify this special partition ... nothing!
OK, do I write this up as a bug or an RFE. Yes, I know that I can go in
and preallocate the partition manually but the whole idea of kickstart
is to do all of this stuff automagically. I assume we will be needing
this stuff for UEFI and we will be doing UEFI under KVM as well.
Comments?
Gene
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
