[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] grub2 problem while booting with xen-4.0.1


  • To: "Fajar A. Nugraha" <list@xxxxxxxxx>
  • From: Abhishek Dixit <abhidixit87@xxxxxxxxx>
  • Date: Thu, 3 Mar 2011 10:51:06 +0530
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 02 Mar 2011 21:22:30 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=v155/Pd2flowzVDPwebc4S1DlCQPGos0BmoBRisXvsotqy5k0gp201zeYqao2POyvf PnpUY9KX9O2iMuJWykLQi6LUC0JxbDFVSIFgXpd9dJskPwxoCoTaOy3sM16+uXliH3z3 o4W9TWSU4/Mr3QKaD4OG9nUhbtN0OkRmjlKTg=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On Thu, Mar 3, 2011 at 8:40 AM, Fajar A. Nugraha <list@xxxxxxxxx> wrote:
> On Thu, Mar 3, 2011 at 9:50 AM, Abhishek Dixit <abhidixit87@xxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.