On Sun, Feb 15, 2009 at 10:23 PM, Mike Mildner
<m.mildner@xxxxxxxxxxxxxxxxxxx> wrote:
>>> Error: (1, 'Internal error', 'Could not open kernel image (2 = No such
>>> file
>
> it comes when i try to start domU
Ah, okay, now we're getting somewhere :)
If you're new to Xen, and you're using RHEL/CentOS, these documents should help
http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU
http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Virtualization_Guide/index.html
It's much easier to start with distro-bundled xen compared to
compiling your own.
Anyway, the contents of /boot/grub/menu.lst that you pasted earlier
was from dom0, right?
What you have on that file is not relevant for domU. To be exact, domU
can use kernel (and initrd) from two places :
- from "kernel" and "ramdisk" line on domU's config file (usually on
/etc/xen/... ), where the actual kernel is located on dom0's
filesystem, OR
- when domUs config has "bootloader=/usr/bin/pygrub", it will read
domU's boot/grub/menu.lst (which is different from dom0's) and load
kernel from domU's filesystem.
What is the contents of your domU config file?
If it has "kernel" and "ramdisk" line, then make sure those files exist on dom0.
If it has "bootlader" line, then your domU should have a
boot/grub/menu.lst that contaion something like this
title domU kernel
kernel /boot/vmlinuz-2.6.18.8-xen root=/dev/md0 ro vga=791 console=tty0
root (hd0,0)
Note the difference. On domU, xen-kernel is loaded as "kernel", while
on dom0 xen-kernel is loaded as "module".
Regards,
Fajar
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users