Xen users - Mar 2011 - grub2 problem while booting with xen-4.0.1

Hi,
It is very surprising for me.
I am not able to get to xen 4.0.1

i.e. following grub2 entry does not work

menuentry ''Ubuntu, with Xen and  Linux 2.6.32.27''  {
        set root=''(hd0,1)''
        multiboot (hd0,1)/boot/xen.gz dummy=dummy
        module  (hd0,1)/boot/vmlinuz-2.6.32.27-pv-ops dummy=dummy
nopat root=/dev/hda1 ro console=tty0
        module  (hd0,1)/boot/initrd.img-2.6.32.27-pv-ops
}

but if I boot with following grub entry

menuentry ''Ubuntu, with Linux 2.6.32.27-pv-ops'' --class ubuntu
--class
gnu-linux --class gnu --class os {
        recordfail
        insmod ext2
        set root=''(hd0,1)''
        search --no-floppy --fs-uuid --set ef6fb0a3-17d8-46b8-944b-4d84fbd3c236
        linux   /boot/vmlinuz-2.6.32.27-pv-ops
root=UUID=ef6fb0a3-17d8-46b8-944b-4d84fbd3c236 ro   quiet splash
        initrd  /boot/initrd.img-2.6.32.27-pv-ops
}

the only concern being the hypervisor not started in case of 2nd type
of grub entry.
Can any one tell me what should I look as with first type of grub
entry I see computer simply starts booting and then suddenly a black
screen comes and every thing restarts.
I do not get any time to see any error messages.
I compiled every thing from scratch.

-- 
Regards
Abhi

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Thu, Mar 3, 2011 at 9:50 AM, Abhishek Dixit <abhidixit87@gmail.com>
wrote:
> i.e. following grub2 entry does not work
>
> menuentry ''Ubuntu, with Xen and  Linux 2.6.32.27''  {
>        set root=''(hd0,1)''
>        multiboot (hd0,1)/boot/xen.gz dummy=dummy
>        module  (hd0,1)/boot/vmlinuz-2.6.32.27-pv-ops dummy=dummy
> nopat root=/dev/hda1 ro console=tty0
>        module  (hd0,1)/boot/initrd.img-2.6.32.27-pv-ops
> }
>
> but if I boot with following grub entry
>
> menuentry ''Ubuntu, with Linux 2.6.32.27-pv-ops'' --class
ubuntu --class
> gnu-linux --class gnu --class os {
>        recordfail
>        insmod ext2
>        set root=''(hd0,1)''
>        search --no-floppy --fs-uuid --set
ef6fb0a3-17d8-46b8-944b-4d84fbd3c236
>        linux   /boot/vmlinuz-2.6.32.27-pv-ops
> root=UUID=ef6fb0a3-17d8-46b8-944b-4d84fbd3c236 ro   quiet splash
>        initrd  /boot/initrd.img-2.6.32.27-pv-ops
> }
>
> the only concern being the hypervisor not started in case of 2nd type
> of grub entry.
> Can any one tell me what should I look as with first type of grub
> entry
For starters, kernel parameters should mostly be the same whether or
not you''re loading the hypervisor. So start with "root"
parameter,
which is different in both entries (for example, by default there
should be no more disk recognized as /dev/hda in kernel 2.6.32)

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Thu, Mar 3, 2011 at 8:40 AM, Fajar A. Nugraha <list@fajar.net>
wrote:
> On Thu, Mar 3, 2011 at 9:50 AM, Abhishek Dixit
<abhidixit87@gmail.com> wrote:
>> i.e. following grub2 entry does not work
>
>>
>> menuentry ''Ubuntu, with Xen and  Linux 2.6.32.27''  {
>>        set root=''(hd0,1)''
>>        multiboot (hd0,1)/boot/xen.gz dummy=dummy
>>        module  (hd0,1)/boot/vmlinuz-2.6.32.27-pv-ops dummy=dummy
>> nopat root=/dev/hda1 ro console=tty0
>>        module  (hd0,1)/boot/initrd.img-2.6.32.27-pv-ops
>> }
>>
>> but if I boot with following grub entry
>>
>> menuentry ''Ubuntu, with Linux 2.6.32.27-pv-ops''
--class ubuntu --class
>> gnu-linux --class gnu --class os {
>>        recordfail
>>        insmod ext2
>>        set root=''(hd0,1)''
>>        search --no-floppy --fs-uuid --set
ef6fb0a3-17d8-46b8-944b-4d84fbd3c236
>>        linux   /boot/vmlinuz-2.6.32.27-pv-ops
>> root=UUID=ef6fb0a3-17d8-46b8-944b-4d84fbd3c236 ro   quiet splash
>>        initrd  /boot/initrd.img-2.6.32.27-pv-ops
>> }
>>
>> the only concern being the hypervisor not started in case of 2nd type
>> of grub entry.
>> Can any one tell me what should I look as with first type of grub
>> entry
>
> For starters, kernel parameters should mostly be the same whether or
> not you''re loading the hypervisor. So start with "root"
parameter,
> which is different in both entries (for example, by default there
> should be no more disk recognized as /dev/hda in kernel 2.6.32)
Sorry I mistyped the question.
The first type of grub entries which include hypervisor note the line
/xen.gz do not boot.
But in case of second grub entry where I booted without xen only
pv-ops dom0 kernel works.
So I infer that kernel was compiled cleanly and there is no problem if
I am trying to boot the pv-ops Dom0 kernel without hypervisor.

The first one does not work where I am trying to boot xen.gz with
pv-ops Dom0 kernel.

I am not clear do you mean to say my first  grub entry (where I am
trying to load the xen)

should look like
module   /boot/vmlinuz-2.6.32.27-pv-ops  root=/dev/hda1 ro console=tty0
or
module  /boot/vmlinuz-2.6.32.27-pv-ops  root=UUID=#@Q##@$ ro console=tty0

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Thu, Mar 3, 2011 at 12:21 PM, Abhishek Dixit <abhidixit87@gmail.com>
wrote:
> Sorry I mistyped the question.
> The first type of grub entries which include hypervisor note the line
> /xen.gz do not boot.
> But in case of second grub entry where I booted without xen only
> pv-ops dom0 kernel works.
> So I infer that kernel was compiled cleanly and there is no problem if
> I am trying to boot the pv-ops Dom0 kernel without hypervisor.
>
> The first one does not work where I am trying to boot xen.gz with
> pv-ops Dom0 kernel.
>
> I am not clear do you mean to say my first  grub entry (where I am
> trying to load the xen)
>
> should look like
> module   /boot/vmlinuz-2.6.32.27-pv-ops  root=/dev/hda1 ro console=tty0
> or
> module  /boot/vmlinuz-2.6.32.27-pv-ops  root=UUID=#@Q##@$ ro console=tty0
>
Two things.

First, even vanilla kernel.org supports pv_ops (enough to be booted as
domU). But you can''t use it for a fully functional dom0 kernel. So to
be able to boot it under hypervisor, you need to have proper dom0
patches (I assume you use JF''s git tree), and you need to enable
dom0-related kernel options.

Second, you need proper kernel parameters to boot. If your normal
kernel needs "root=UUID*" to boot, then the same is true when you boot
it under the hypervisor.

In any case, what''s wrong (whether you don''t have dom0-related
options
enabled, or you have incorrent "root" parameters), it should be
obvious from kernel boot message (as long as you do NOT have "rhgb"
and "quiet"). Simply saying "suddenly a black screen comes and
every
thing restarts" doesn''t help.

So start with modifying your kernel parameter, then if it still
doesn''t work you need to capture (or remember) what the last boot
message before reboot was. Otherwise there''s not much others can do to
help.

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Thu, Mar 3, 2011 at 11:19 AM, Fajar A. Nugraha <list@fajar.net>
wrote:
> On Thu, Mar 3, 2011 at 12:21 PM, Abhishek Dixit
<abhidixit87@gmail.com> wrote:
>> Sorry I mistyped the question.
>> The first type of grub entries which include hypervisor note the line
>> /xen.gz do not boot.
>> But in case of second grub entry where I booted without xen only
>> pv-ops dom0 kernel works.
>> So I infer that kernel was compiled cleanly and there is no problem if
>> I am trying to boot the pv-ops Dom0 kernel without hypervisor.
>>
>> The first one does not work where I am trying to boot xen.gz with
>> pv-ops Dom0 kernel.
>>
>> I am not clear do you mean to say my first  grub entry (where I am
>> trying to load the xen)
>>
>> should look like
>> module   /boot/vmlinuz-2.6.32.27-pv-ops  root=/dev/hda1 ro console=tty0
>> or
>> module  /boot/vmlinuz-2.6.32.27-pv-ops  root=UUID=#@Q##@$ ro
console=tty0
>>
>
> Two things.
>
> First, even vanilla kernel.org supports pv_ops (enough to be booted as
> domU). But you can''t use it for a fully functional dom0 kernel. So
to
> be able to boot it under hypervisor, you need to have proper dom0
> patches (I assume you use JF''s git tree), and you need to enable
> dom0-related kernel options.
Correct I used JF''s git tree.
I enabled all the Xen options.
.config attached with this mail.
> Second, you need proper kernel parameters to boot.
Exactly I am not clear with this part.
>If your normal
> kernel needs "root=UUID*" to boot, then the same is true when you
boot
> it under the hypervisor.
Ok.
> In any case, what''s wrong (whether you don''t have
dom0-related options
> enabled, or you have incorrent "root" parameters), it should be
> obvious from kernel boot message (as long as you do NOT have
"rhgb"
> and "quiet"). Simply saying "suddenly a black screen comes
and every
> thing restarts" doesn''t help.
>
> So start with modifying your kernel parameter, then if it still
> doesn''t work you need to capture (or remember) what the last boot
> message before reboot was. Otherwise there''s not much others can
do to
> help.
Ok.I will update.
-- 
Regards
Abhi


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users