You, Yongkang
2006-Feb-28 03:28 UTC
RE: [Fedora-xen] Re: 2.6.15-1.1977_FC5hypervisor does not boot (bootingis interrupted by restart)
It seemed Xen0 couldn’t find root filesystem in your
root=/dev/VolGroup01/LogVol00
mount: could not find filesystem /dev/root
Setuproot: mouting /dev failed: No such file or directory
Setuproot: error mounting /proc: No such file or directory
Setuproot: error mounting /sys: No such file or directory
Best Regards,
Yongkang (Kangkang) 永康
________________________________
From: fedora-xen-bounces@redhat.com [mailto:fedora-xen-bounces@redhat.com] On
Behalf Of Jan Andrejkovic
Sent: 2006年2月28日 8:11
To: fedora-xen@redhat.com
Subject: [Fedora-xen] Re: 2.6.15-1.1977_FC5hypervisor does not boot (bootingis
interrupted by restart)
Hello,
I''m sending an update, based on some advices I have changed my
grub.conf:
title Fedora Core (2.6.15-1.1977_FC5hypervisor )
root (hd0,6)
kernel /boot/xen.gz-2.6.15-1.1977_FC5 com1=1200,8n1 console=com1,vga
sync_console noreboot
module /boot/vmlinuz-2.6.15-1.1977_FC5hypervisor ro
root=/dev/VolGroup01/LogVol00 init 3 com1=1200,8n1 console=com1,vga sync_console
noreboot
module /boot/initrd-2.6.15-1.1977_FC5hypervisor.img
So I have changed speed of display to synchronise with com port to 1200 bauds
and noreboot option so I can read last messages.
XEN has loaded fine, but domain0 was not able to mount some drives:
Here are some error messages:
<cut>
Red Hat nash version 5.0.28
Mounting proc filesystem
Mounting sysfs filesystem
Creating /dev
Creating initial device nodes
mknod: failed to create /dev/ram0 file exists ! first error message I have
noticed
mknod: failed to create /dev/ram1 file exists
<cut>
Creating block device node
Loading jbd.ko module
Loading ext3.ko module
Creating root device
Mounting root filesystem
mount: could not find filesystem /dev/root
Setuproot: mouting /dev failed: No such file or directory
Setuproot: error mounting /proc: No such file or directory
Setuproot: error mounting /sys: No such file or directory
<cut>
Do you have any idea where the problem is?
I can provide more detailed log if somebody is interested...
Do you think I should open bugzilla ticket?
Thank you very much for an advice,
Cheers,
Jan
On 2/26/06, Jan Andrejkovic <jandrejkovic@gmail.com> wrote:
Hello everybody,
This is my first e-mail into this mailing list. I have a problem to start
2.6.15-1.1977_FC5hypervisor kernel (domain0).
When I select this option in a grub I can see that xen hypervisor is loading but
after short time my laptop is restarted.
I cannot tell you last (error) message because pause or CTRL+S does not work and
laptop is restarted before drives are mounted so I have no logs.
Do you have any idea where is the problem and how can I pause booting so I can
see last (error) message?
Other details: I have Dell latitude D600 with Pentium M. I have upgraded FC4 to
FC5 test3 using DVD iso. I have updated all packages after that using yum
update.
Kernel 2.6.15-1.1977_FC5 works fine on my laptop. I was also able to start
domain0 in FC4 using kernel from Rik van Riel''s web page (
2.6.12-1.1454_FC4).
Some other problems I found:
When I upgraded from FC4 to FC5 test3 I did not see any option to install XEN
from DVD (I have selected upgrade not new install in anaconda).
Also entries for FC4 kernel were deleted from my grub.conf and original
grub.conf was not saved.
When I have installed kernel 1977_FC5 or 1977_FC5hypervisor my grub.conf was not
updated, so I had to update it manually (I have used yum install).
Part of my grub.conf configuration (manually added) - do you see any problem
here?
title Fedora Core ( 2.6.15-1.1977_FC5)
root (hd0,6)
kernel /boot/vmlinuz-2.6.15-1.1977_FC5 ro root=LABEL=/ rhgb quiet
initrd /boot/initrd-2.6.15-1.1977_FC5.img
title Fedora Core (2.6.15-1.1977_FC5hypervisor )
root (hd0,6)
kernel /boot/xen.gz-2.6.15-1.1977_FC5
module /boot/vmlinuz-2.6.15-1.1977_FC5hypervisor ro
root=/dev/VolGroup01/LogVol00 init 3
module /boot/initrd-2.6.15-1.1977_FC5hypervisor.img
List of files in /boot:
-rw-r--r-- 1 root root 63677 Feb 15 20:57 config-2.6.15-1.1955_FC5
-rw-r--r-- 1 root root 63666 Feb 23 20:05 config-2.6.15-1.1977_FC5
-rw-r--r-- 1 root root 58988 Feb 23 20:41 config-2.6.15-1.1977_FC5hypervisor
drwxr-xr-x 2 root root 1024 Feb 26 15:55 grub
-rw-r--r-- 1 root root 914868 Feb 25 05:01 initrd-2.6.15-1.1955_FC5.img
-rw-r--r-- 1 root root 918988 Feb 26 02:05
initrd-2.6.15-1.1977_FC5hypervisor.img
-rw-r--r-- 1 root root 916284 Feb 25 23:56 initrd-2.6.15-1.1977_FC5.img
-rw-r--r-- 1 root root 94600 Feb 8 15:39 memtest86+- 1.65
-rw-r--r-- 1 root root 812204 Feb 15 20:57 System.map-2.6.15-1.1955_FC5
-rw-r--r-- 1 root root 812648 Feb 23 20:05 System.map-2.6.15-1.1977_FC5
-rw-r--r-- 1 root root 812906 Feb 23 20:41
System.map-2.6.15-1.1977_FC5hypervisor
-rw-r--r-- 1 root root 1515418 Feb 15 20:57 vmlinuz-2.6.15-1.1955_FC5
-rw-r--r-- 1 root root 1515968 Feb 23 20:05 vmlinuz-2.6.15-1.1977_FC5
-rw-r--r-- 1 root root 1529433 Feb 23 20:41 vmlinuz-2.6.15-1.1977_FC5hypervisor
-rw-r--r-- 1 root root 257152 Feb 23 19:51 xen.gz-2.6.15-1.1977_FC5
-rwxr-xr-x 1 root root 710104 Feb 23 21:16 xen-syms-2.6.15-1.1977_FC5
Thank you for any advice in advance.
Kind regards,
Jan