https://bugzilla.novell.com/show_bug.cgi?id=811408 https://bugzilla.novell.com/show_bug.cgi?id=811408#c10 Marcus Schaefer <ms@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|agraf@suse.com |cschum@suse.com --- Comment #10 from Marcus Schaefer <ms@suse.com> 2013-03-28 14:54:28 UTC --- Thanks for the explanation. when I wrote that I did no understand the differences then I meant more why the "design" of the table layout differs between the tools although they are targeting the same goal. But you explained that as well my concern is that I can't make it boot with a legacy bios which is no problem when using gptsync. As I wrote a simple qemu smoke test outlined that it does not boot and I also provided the relevant information to you about this. The system try to boot from the disk but hangs at that point forever this means it is seen as a bootable disk but it can't boot from it for some reason. I think it would be easy for you to reproduce this with plain qemu
Perhaps Alex has some more ideas/comments...
Alex pointed me to you :) As you are saying you'd better don't touch it I'm more and more convinced it's easier to follow the gptsync way as it's an extra package which I also could remove again. It also fits better into the workflow as it's a single step and does not interact with the primary partition step. imho both solutions are hacky so it's up to the Studio people to speak up if we really need this @Cornelius: I hope this report provides enough information for you to get an impression. if not let's talk in person. if yes what's your opinion about hybrid EFI/legacy-BIOS images now ? Thanks -- 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.