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

["Fajar A. Nugraha" <list@xxxxxxxxx>]

On Thu, Mar 3, 2011 at 12:21 PM, Abhishek Dixit <abhidixit87@xxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users