* 'ser_baud=xxx' option gone away
@ 2004-06-23 16:56 Keir Fraser
2004-06-23 18:16 ` more bootupproblems with xen Rune Johan Andresen
0 siblings, 1 reply; 4+ messages in thread
From: Keir Fraser @ 2004-06-23 16:56 UTC (permalink / raw)
To: xen-devel
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* more bootupproblems with xen
2004-06-23 16:56 'ser_baud=xxx' option gone away Keir Fraser
@ 2004-06-23 18:16 ` Rune Johan Andresen
2004-06-23 20:01 ` xen user
0 siblings, 1 reply; 4+ messages in thread
From: Rune Johan Andresen @ 2004-06-23 18:16 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1: Type: text/plain, Size: 767 bytes --]
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
[-- Attachment #2: Type: text/enriched, Size: 816 bytes --]
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<x-tad-bigger>= 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
</x-tad-bigger>
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: more bootupproblems with xen
@ 2004-06-23 18:54 Neugebauer, Rolf
0 siblings, 0 replies; 4+ messages in thread
From: Neugebauer, Rolf @ 2004-06-23 18:54 UTC (permalink / raw)
To: Rune Johan Andresen, xen-devel; +Cc: Neugebauer, Rolf
> -----Original Message-----
> From: xen-devel-admin@lists.sourceforge.net [mailto:xen-devel-
> admin@lists.sourceforge.net] On Behalf Of Rune Johan Andresen
> Sent: 23 June 2004 19:17
> To: xen-devel@lists.sourceforge.net
> Subject: [Xen-devel] more bootupproblems with xen
>
> 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
Are you using xen-1.2? Then try: ser_baud=115200 instead of the com
option.
The com1 option was introduced in unstable tree some time ago.
> 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
Lot's of things have changed since the 1.2 release so suggestions made
on the mailing-list will not apply to all versions of Xen.
We try to keep the documentation in README and README.CD up-to-date, at
least after major changes have stabilized.
Rolf
> 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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: more bootupproblems with xen
2004-06-23 18:16 ` more bootupproblems with xen Rune Johan Andresen
@ 2004-06-23 20:01 ` xen user
0 siblings, 0 replies; 4+ messages in thread
From: xen user @ 2004-06-23 20:01 UTC (permalink / raw)
To: xen-devel
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2004-06-23 20:01 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-06-23 16:56 'ser_baud=xxx' option gone away Keir Fraser
2004-06-23 18:16 ` more bootupproblems with xen Rune Johan Andresen
2004-06-23 20:01 ` xen user
-- strict thread matches above, loose matches on Subject: below --
2004-06-23 18:54 Neugebauer, Rolf
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.