Bug#594986: Re: Bug#594986: xen-linux-system-2.6.32-5-xen-686: Can't find hypervisor information in sysfs!

[Javier Barroso <Javier.Barroso@isotrol.com>]

On -10/01/37 20:59, Bastian Blank wrote:
> On Tue, Aug 31, 2010 at 10:45:22AM +0200, Javier Barroso wrote:
>    
> > "
> >      
> > > [    0.000000] Booting paravirtualized kernel on bare hardware
> > >        
> > The kernel does not run on Xen. Closing as user error.
> > "
> > This is the same message which appear in my machine in syslog (I'm attaching dmesg output).
> >      
> So you are not running on Xen.
>    
Sorry my dmesg was produced by a working xen.
>    
> > Maybe dropping a note in /usr/share/doc/xen*/README.Debian would be a good idea about how to solve this issue.
> >      
> Which problem? That you can't read what Grub wants to tell you?
>    
Grub should be configured to boot with the xen working configuration.

In my system:
### BEGIN /etc/grub.d/10_linux ### ##
# THIS ENTRY WILL NOT WORK ( "Booting paravirtualized kernel on bare 
hardware" message)
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-686' --class debian 
--class gnu-linux --class gnu --class os {
        insmod part_msdos
        insmod ext2
        set root='(hd0,msdos1)'
        search --no-floppy --fs-uuid --set 
65ff51e3-bf08-4565-b0de-7f168c0e7602
        echo    'Loading Linux 2.6.32-5-xen-686 ...'
        linux   /vmlinuz-2.6.32-5-xen-686 
root=/dev/mapper/isofuture-root ro
        echo    'Loading initial ramdisk ...'
        initrd  /initrd.img-2.6.32-5-xen-686
}
...

### BEGIN /etc/grub.d/20_linux_xen ###
# THIS ENTRY WILL WORK
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-686 and XEN 
4.0-i386' --class debian --class gnu-linux --class gnu --class os 
--class xen {
        insmod part_msdos
        insmod ext2
        set root='(hd0,msdos1)'
        search --no-floppy --fs-uuid --set 
65ff51e3-bf08-4565-b0de-7f168c0e7602
        echo    'Loading Linux 2.6.32-5-xen-686 ...'
        multiboot       /xen-4.0-i386.gz placeholder
        module  /vmlinuz-2.6.32-5-xen-686 placeholder 
root=/dev/mapper/isofuture-root ro
        echo    'Loading initial ramdisk ...'
        module  /initrd.img-2.6.32-5-xen-686
}

So, is this a grub bug ?

>    
> > First entry (default entry) will give me this message error. But if I boot with third entry (which talk about booting xen kernel and 4.0 xen flavour) then xm commands start working, but the same message (Booting paravirtualized kernel on bare hardware) is shown too in dmesg.
> >      
> No, it looks more like this in the correct case.
> | [    0.000000] Booting paravirtualized kernel on Xen
> | [    0.000000] Xen version: 4.0.1-rc3 (preserve-AD) (dom0)
>    
Sorry about reporting with not appropiate dmesg (I sent an older dmesg)