On Sat, Dec 15, 2012 at 06:47:29PM -0600, W. Michael Petullo wrote:
> >> I have successfully installed Fedora 18 Beta as Dom0 on one computer,
> >> and am now trying to do the same on another. I am using all of the
> >> standard Fedora 18 packages, including xen-4.2.0-6.fc18.x86_64.
> >> 
> >> On the second computer, I ended up with an EFI grub2 install.
> >> 
> >> I used yum to install xen, and noted that the package installation did
> >> not update /etc/grub2-efi.cfg.
> >> 
> >> I ran grub2-mkconfig by hand, and this added Xen entries to
> >> /etc/grub2-efi.cfg. However, booting failed: grub2 complained that it
> >> did not know the multiboot keyword.
> >> 
> >> Does anyone have experience getting EFI grub2 to boot Xen/Fedora 18?
> >> Is my trouble expected?
> 
> > Did you try native UEFI boot? So booting the xen.efi binary directly from 
> > UEFI ? 
> > 
> > Also note that F18 kernel doesn't have proper UEFI support for dom0 (yet),
> > because it hasn't been upstreamed yet..
> 
> I eventually figured out how to install Fedora 18 using the MBR-style
> grub2.
> 
> My Fedora 18 install media was a thumbdrive; what I discovered was that
> if I did *not* instruct my motherboard firmware's UEFI menu to boot from
> this USB device, then it seemed to pick it up as an old-style MBR boot
> instead.  From that point on, Anaconda seemed to assume the computer
> had a BIOS, not UEFI.
> 
> It appears the Fedora 18 install image supports both BIOS/MBR and UEFI,
> and the motherboard's firmware picks up the MBR if not explicitly asked
> to boot the device as UEFI.
> 
> After picking through Anaconda and finding no option (i.e., a way to
> install using an MBR boot instead of a UEIF boot), I suspect I could
> achieve the same effect by manually creating an msdos partition table
> on the target hard drive instead of a GPT partition table.
> 

I think there's also "nogpt" boot/kernel cmdline option for the installer..

-- Pasi

--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen

Reply via email to