On Wed, Jul 21, 2010 at 02:14:05AM -0400, Adit Ranadive wrote:
> The nomodeset parameter didnt work either. One thing I didnt mention was
> that I could see the Xen bootup messages before and now but cannot see the
> linux boot up messages. Is there anything I need to enable in the linux
> config for the console to be visible?
> There maybe something funky with what the pvops kernel is doing versus the
> older pv kernel since I can see the messages for the older one.
>
grub.conf like this works for me:
title Xen 4.0, dom0 Linux kernel 2.6.32.12
root (hd0,0)
kernel /boot/xen-4.0.gz dom0_mem=512M
module /boot/vmlinuz-2.6.32.12 root=/dev/sda1 ro nomodeset
module /boot/initrd.img-2.6.32.12
That gives me VGA text console, and I can see both Xen and dom0 kernel boot
messages.
> Serial isnt an option since the machine is not physically accessible to
> me.
>
You could use SOL (Serial Over Lan), provided by the Dell iDRAC.
http://wiki.xensource.com/xenwiki/XenSerialConsole
-- Pasi
> Thanks,
> Adit
>
> On Tue, Jul 20, 2010 at 8:24 AM, Pasi Kärkkäinen <[1]pasik@xxxxxx> wrote:
>
> On Sun, Jul 18, 2010 at 08:43:40PM -0400, Adit Ranadive wrote:
> > I am currently using a Dell PowerEdge server R610 with Xen 4.0
> installed
> > and the 2.6.31.13 pvops kernel.
> > I am accessing the server console using the iDRAC KVM feature of
> the dell
> > management console.
> > Does anyone know how to configure the console option in the grub
> menu so
> > that all the boot messages can be seen on the
> > mgmt console?
> > Currently I can view only the Xen bootup messages if I dont specify
> the
> > console=xxx option on the kernel line. I cant see any of
> > the linux kernel boot up messages. Specifying console=xxx on the
> kernel
> > module line doesnt work either.
> > Has anyone worked with this sort of config before? Is there
> anything else
> > I can specify on the kernel/module line so that all
> > the bootup messages are visible?
> >
> > Below is my grub menu:
> > title Red Hat Enterprise Linux Server (2.6.18-164.6.1.el5)
> > root (hd0,0)
> > kernel /vmlinuz-2.6.18-164.6.1.el5 ro root=/dev/vg1/root
> > initrd /initrd-2.6.18-164.6.1.el5.img
> >
> > title Xen 4.0 - Linux 2.6.31.13 pvops
> > root (hd0,0)
> > kernel /xen.gz noreboot loglvl=all guest_loglvl=all iommu=1
> > module /vmlinuz-2.6.31.13 ro root=/dev/vg1/root loglevel=10
> swiotlb=force earlyprintk=xen console=hvc0
> > module /initrd-2.6.31.13.img
> >
>
> That should work. You could try adding "nomodeset" parameter, to disable
> the kernel modesetting (KMS) stuff.
> Maybe that messes up the console.
>
> You could also enable the SOL serial console:
> [2]http://wiki.xensource.com/xenwiki/XenSerialConsole
>
> -- Pasi
> > title Xen 4.0 - Linux 2.6.18.8
> > root (hd0,0)
> > kernel /xen.gz loglvl=all guest_loglvl=all
> > module /vmlinuz-2.6.18.8-xen0 ro root=/dev/vg1/root
> earlyprintk=xen
> > module /initrd-2.6.18.8-xen0.img
> >
> > P.S.: Ive tried using the 2.6.18.8 kernel and that seems to show
> > everything fine on the console.
> >
> > Thanks,
> > Adit
>
> > _______________________________________________
> > Xen-users mailing list
> > [3]Xen-users@xxxxxxxxxxxxxxxxxxx
> > [4]http://lists.xensource.com/xen-users
>
> References
>
> Visible links
> 1. mailto:pasik@xxxxxx
> 2. http://wiki.xensource.com/xenwiki/XenSerialConsole
> 3. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
> 4. http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home