Xen devel - Jun 2004 - ''ser_baud=xxx'' option gone away

The Xen boot option ''ser_baud=<baud>'' has been removed
from the
unstable tree. If you were still using this obsolete option then the
effect is that you will get no serial output when you boot Xen, which
may lead you to believe that there is a more serious problem.

To fix this you must move to the new boot option:
 ''com1=<baud>,8n1''

 -- Keir


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

Hi, thanks for answers. Grub can now find the files, but there are even 
a worse nut to solve now:

When booting I get this messages:

Warning: unable to open an initial console.
Kernel panic: no init found. Try passing init= option to kernel

This is a common failure message in bootup, but I am not sure what I do 
wrong now.

df -k gives:

/dev/hda2    38076936   4064044 etc..
/dev/hda1    124427 	......			/boot
none		..... 		.......		/dev/shm


grub conf :

title Xen

	root(hd0,0)
	kernel /xen.gz dom0_mem=131072 watchdog noreboot com1=115200 noht
	module	/xenolinux.gz root=/dev/hda1 ro console=tty0


Any ideas? I have trried to search for this problem but have not got 
any useful. I am useing the last
binary stable xen version.

Thank you!  :-)

Rune

Rune Johan Andresen wrote:
> Hi, thanks for answers. Grub can now find the files, but there are even 
> a worse nut to solve now:
> 
> When booting I get this messages:
> 
> Warning: unable to open an initial console.
> Kernel panic: no init found. Try passing init= option to kernel
> 
> This is a common failure message in bootup, but I am not sure what I do 
> wrong now.
> 
> df -k gives:
> 
> /dev/hda2 38076936 4064044 etc..
> /dev/hda1 124427 ...... /boot
> none ..... ....... /dev/shm
> 
> 
> grub conf :
> 
> title Xen
> 
> root(hd0,0)
> kernel /xen.gz dom0_mem=131072 watchdog noreboot com1=115200 noht
> module /xenolinux.gz root=/dev/hda1 ro console=tty0
Hi Rune,

I''ve only run 1.0 but I use grub and may have some ideas.  The kernel 
and module instructions may require a full path.  Also, df -k shows 
/dev/hda1 as /boot.  You need to specify where / lives.  I''m guessing 
it''s /dev/hda2.  If so, try this in your grub.conf file.

   root(hd0,0)
   kernel /boot/xen.gz dom0_mem=131072 watchdog noreboot com1=115200 noht
   module /boot/xenolinux.gz root=/dev/hda2 ro console=tty0

Hope that solves the problem.

Mike Wright
> 
> Any ideas? I have trried to search for this problem but have not got any 
> useful. I am useing the last
> binary stable xen version.
> 
> Thank you! :-)
> 
> Rune
> 
> 
> 
> 
> 


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel