Re: [Xen-ia64-devel] IA64 Intel further problems

[Radek Antoniuk <r.antoniuk@xxxxxxxxxxxx>]

Alex Williamson napisał(a):
> On Mon, 2007-05-28 at 18:13 +0200, Radek Antoniuk wrote:
>
> > image=/boot/vmlinuz-2.6.18-4-mckinley
> >          label=Linux
> >          root=/dev/sda2
> >          read-only
> >          initrd=/boot/initrd.img-2.6.18-4-mckinley
> >
> > image=/boot/vmlinuz-2.6.18-xen
> >          label=xen
> >          root=/dev/sda2
> >          vmm=/boot/xen.gz
> >          read-only
> >          initrd=/boot/initrd.img-2.6.18-xen
> >          append="com2=115200,8n1 console=com2 dom0_mem=1G -- nomca nosmp 
> > console=tty0 console=ttyS1,115200,8n1 rhgb root=/dev/sda2"
>    These shouldn't matter, but you've got a lot of unnecessary options
> here.  "com2=115200,8n1 console=com2" - these should be auto detected
> now.  "nomca nosmp" - no longer necessary.  "console=tty0
> console=ttyS1,115200,8n1" - this will split your kernel output between
> VGA and serial, but if you use autodection as mentioned above, I think
> ttyS1 becomes ttyS0.  You can also just remove these for only serial
> console and it should autodetect correctly.  "rhgb" - this is an option
> for Red Hat Graphical Boot, but based on your other elilo entry, I'd
> guess you're running Debian, so doesn't do anything.  So you could
> reduce this to something like:
>
> append="dom0_mem=1G -- root=/dev/sda2"
>
> > And for curiosity:
> > fdisk -l /dev/sda
>    fdisk doesn't understand GPT partition tables and shows the entire
> disk as a single partition.  This is a way of protecting the partition
> from old utilities.  Try 'parted /dev/sda print'.
>
> > Disk /dev/sda: 36.7 GB, 36701199872 bytes
> > 255 heads, 63 sectors/track, 4462 cylinders
> > Units = cylinders of 16065 * 512 = 8225280 bytes
> >
> >     Device Boot      Start         End      Blocks   Id  System
> > /dev/sda1               1        4463    35841015   ee  EFI GPT
> >
> >
> > Remark: the non-xen kernel works of course :)
> > Any ideas?
>    Posting your entire boot log may help see what's going on.  In
> response to your followup; 8,2 is correct for sda2:
>
> brw-rw---- 1 root disk 8, 2 2007-05-13 20:42 /dev/sda2
>
> If you're using Debian as your dom0 OS and have all your drivers
> builtin, why are you using an initrd?  That may be causing you problems.
> I usually test with Debian and don't require one.  Thanks,

Well. Not all drivers, but the needed for the FS mounting :)
Indeed parted showed the partitions:
Disk /dev/sda: 36.7GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system  Name  Flags
 1      17.4kB  130MB   130MB   fat16              boot
 2      130MB   9567MB  9437MB  ext3         /
 3      9567MB  13.8GB  4194MB  linux-swap

and my fstab:
proc            /proc           proc    defaults        0       0
/dev/sda2       /               ext3    defaults,errors=remount-ro 0       1
/dev/sda3       none            swap    sw              0       0
/dev/hda        /media/cdrom0   udf,iso9660 user,noauto     0       0


Hm, I have read somewhere about the necessity of using LABEL= in append 
line of elilo.conf.
Maybe that is the cause?
However i've tried now, following your suggestion:
        append="dom0_mem=1G -- root=/dev/sda2 LABEL=/"

And, surprise, no xen console output, and of course restart because of 
rootfs panic. So I guess the console lines still have to be there ;)
For the bootlog, it's quite a problem cause it doesn't get logged 
anywhere...

Radek

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel