https://bugzilla.novell.com/show_bug.cgi?id=811408 https://bugzilla.novell.com/show_bug.cgi?id=811408#c8 Marcus Schaefer <ms@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|ms@suse.com |puzel@suse.com --- Comment #8 from Marcus Schaefer <ms@suse.com> 2013-03-27 20:28:34 UTC --- I know that the UEFI spec doesn't allow an MBR to be embedded in the GPT and that there will be firmware which will refuse to boot such a thing in UEFI mode if an MBR is detected. The reason why I'd like to be able to create hybrid images is that SuSE Studio requested it. So there will be an option which allows the user to create EFI hybrid images also mentioning the risk. in kiwi speak there is the syncMBR="true|false" attribute available. With gptsync I was able to implement that. Thus kiwi supports: - legacy only - uefi only - legacy/uefi hybrid (risky) from what you wrote I don't understand the difference between gptsync and the suse parted extension. both are targeting the legacy BIOS and the ability to boot in that mode if GPT is not supported. I wasn't able to boot with a legacy bios (the one qemu or VMware provides) if I use sync_mbr label code from parted. The idea of a consistent mapping is fine but I don't think it makes the legacy bios implementations happy. I'm fine if you are saying that the intention of the sync_mbr label in parted is different from gptsync and that you don't consider this as a bug. In that case I will follow the gptsync way and will try to get a package into the suse distro. imho the parted label is also not upstream. so either way, it stays hacky Thoughts ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.