On Mon, 11 Feb 2013, Dario Faggioli wrote:

On Wed, 2013-01-23 at 15:15 +0100, Roberto Fichera wrote:
I've the same exact problem. I had to manually run grub2-mkconfig in
all F17 boxes.

Happened again! Sorry I'm coming back to this thread so late, but I
couldn't access my Fedora test box for a while...

Ok, here's the thing. I booted the 'Fedora with Xen...' menu entry, so
I'm sure it was working.

I run `yum upgrade', and that involved installing a new version of the
Xen packages (at the end of the update, I have 4.2.1-7).

Now, here it is what I have in my /boot/grub2/grub.cfg:

menuentry 'Fedora, with Xen hypervisor' --class gnu-linux --class gnu --class 
os --class xen $menuentry_id_option 
'xen-gnulinux-simple-86a900c9-aa88-49f1-a007-0facdf17b732' {
       insmod part_msdos
       insmod ext2
       set root='hd0,msdos8'
       if [ x$feature_platform_search_hint = xy ]; then
         search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos8 
--hint-efi=hd0,msdos8 --hint-baremetal=ahci0,msdos8  
         search --no-floppy --fs-uuid --set=root 
       echo    'Loading Xen xen ...'
       multiboot       /xen.gz placeholder
       echo    'Loading Linux 3.7.6-201.fc18.x86_64 ...'
       module  /vmlinuz-3.7.6-201.fc18.x86_64 placeholder 
root=/dev/mapper/host-fedora_root ro

Did you update the kernel at the same time? That looks like what you might get with grubby which is run (which doesn't handle xen very well, which is why xen-hypervisor runs grub2-mkconfig).

        Michael Young
xen mailing list

Reply via email to