i added "noreboot" to read the err info:
Mounted /proc filesystem
Mounting sysfs
Creating /dev
Starting udev
Creating root device
Mounting root filesystem
mount: error 2 mounting ext3
mount: error 2 mounting none
Switching to new root
switchingroot:mounting failed: 22
umount /initrd/dev failed: 2
Kernel panic-not syncing: Attempted to kill init!
----The new menu.lst is:-------
kernel /xen.gz dom0_mem=131072 console=vga
module /vmlinuz-2.6.11.2-xen0 root=dev/hda1 ro console=tty0 noreboot
module /initrd-2.6.11.2-xen0
----the initrd-XXX-xen0 is made as:
mkinitrd initrd-2.6.11.2-xen0 2.6.11.2-xen0
"Petersson, Mats" <mats.petersson@xxxxxxx> 写道：
If you add "noreboot" to the end of kernel line, the machine shouldn't try to reboot on error, at least if the error is caused by something that causes XEN's machine_restart to be called. Obviously, if it's a triple-fault, then the machine will reboot regardless, in which case the more safe method to get the debug output is to use a serial console, such as "com1=115200,n81 console=vga, com1".
I hope this helps.
--
Mats
i change to:
kernel /xen.gz dom0_mem=131072 console=vga
initrd /initrd-2.6.11.2-xen0 root=dev/hda1 ro console=tty0
it said it is not a xen compitable img
so i change to:
kernel /xen.gz dom0_mem=131072 console=vga
module /vmlinuz-2.6.11.2-xen0 root=dev/hda1 ro console=tty0
module /initrd-2.6.11.2-xen0
and it after display info:starting ?ev?, too quick to read, and then the machine rebooted.
still can not boot
"Petersson, Mats" <mats.petersson@xxxxxxx> wrote：
You need to say "module /initrd-2.6.11.2-xen0" instead of initrd, as initrd requries (as it says) that the kernel loaded is linux. You're using a XEN kernel, which can handle taking a initrd as a module, but not as a initrd command (I don't know exactly what the difference is, but trust me, the module instead of initrd works).
--
Mats
Thanks Petersson,
I have not LVM, the Xen use xen.gz as a kernel and use vmlinuz-2.6.11.2-xen0 as a module, if i initrid vmlinuz-xxx-xen0, and add lines in grub/menu.lst:
kernel /xen.gz dom0_mem=131072 console=vga
module /vmlinuz-2.6.11.2-xen0 root=dev/hda1 ro console=tty0
initrd /initrd-2.6.11.2-xen0
it said:
Error19: Linux kernel must be loaded before initrd
how to set the initrd?
"Petersson, Mats" <mats.petersson@xxxxxxx> writon：
Most likely, you haven't got your initrd set up correctly, so your root file system isn't being detected. The final step in the kernel is to try NFS and Floppy file systems, if it can't find a root fs somewhere else.
You either need to make sure that your initrd contains the relevant modules for the disk(s) and file-systems that you use (including for instance LVM if you're using that on the disk). Another method is to disable modules, building a monolithic kernel. That way, you don't need an initrd to get things going. This was the way I got it working when I had the same problem.
--
Mats
xen3.0 booted and dom0 kernel loaded, it said:
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Insert root floppy and press ENTER
what should i do?
-----------info----------------------
xen: unstable, 3.0-devel
kernel 2.6.11.2-xen0
.coooom/xen-users
DO YOU YAHOO!?
__________________________________________________
赶快注册雅虎超大容量免费邮箱?
http://cn.mail.yahoo.com
__________________________________________________
赶快注册雅虎超大容量免费邮箱?
http://cn.mail.yahoo.com
