On Sun, Aug 12, 2012 at 10:49:15PM -0500, Jerry Amundson wrote:
> On Thu, Jun 28, 2012 at 9:22 AM, Pasi Kärkkäinen <pa...@iki.fi> wrote:
> > On Wed, Jun 27, 2012 at 10:40:01PM -0500, Jerry Amundson wrote:
> >> On Sat, Jun 9, 2012 at 6:37 AM, Pasi Kärkkäinen <pa...@iki.fi> wrote:
> >> > On Fri, Jun 08, 2012 at 12:00:44AM -0700, sorabh hamirwasia wrote:
> >> >>    Hi,
> >> >>    I have installed "Xen" on Fedora16 host using "yum install xen" 
> >> >> command
> >> >>    and it has been installed properly. I can see the changes in
> >> >>    /etc/grub2.cfg file too. But when I reboot then the entry for Xen is 
> >> >> not
> >> >>    listed in the boot menu. On further analyzing I found that in
> >> >>    /etc/grub.conf there is no entry related to Xen. Do we need to modify
> >> >>    grub.conf manually ? If yes then how to do that. ?
> >> >>    Please help me with this.
> >> >
> >> > You can tweak the Xen hypervisor cmdline options in:
> >> > /etc/default/grub file, like this:
> >> >
> >> > GRUB_DEFAULT="Xen"
> >>
> >> The only thing I see in fc17 (also) is a
> >> set default="Xen"
> >> line in /boot/grub2/grub.cfg
> >>
> >> I've been waiting, hoping, and did a fresh install of Fedora 17, then
> >> "yum install xen", in anticipation (again) of Fedora/Xen/dom0 boot
> >> magic.
> >> Disappointment.
> >>
> >
> > And did you run "grub2-mkconfig -o /boot/grub2/grub.cfg" ?
> >
> > What's the problem?
> 
> FWIW, my original problem, being that the system in question is i686,
> was that kernel-PAE had not been installed before xen-hypervisor.
> However, even after that the
> set default="Xen"
> accomplishes nothing as "Xen" does not exactly match the entries put

Whoops. Did putting 'Xen 4.1.2" do it?

> in place by grub2-mkconfig.
> 
> So, getting further along, but still no Xen without manual assistance.
> 
> jerry
> --
> xen mailing list
> xen@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/xen
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen

Reply via email to