Did you forget your init ramdisk? -Alex On Sat, Feb 14, 2009 at 9:49 PM, Mike Mildner <m.mildner@kleiderschrank51.de> wrote:> hi folks, > > a new error. i can''t make steps forward )-: ok, my opteron was to old for > xen, so we get today a brand new phenom 2 X3 and after the complete xen > rebuild i get this: > Error: (1, ''Internal error'', ''Could not open kernel image (2 = No such file > or directory)'') What Kernel image? Which file/directory? why can not make > xen clearly error messages? > so i check my system and can''t find the error: > ls /boot: > vmlinuz-2.6.18.8-xen > xen-3.3.1.gz > xen-3.3.gz -> xen-3.3.1.gz > xen-3.gz -> xen-3.3.1.gz > xen.gz -> xen-3.3.1.gz > xen-syms-3.3.1 > > cat /boot/grub/menu.lst > title Xen 3.3 / XenLinux 2.6 > kernel /boot/xen-3.gz vga=791 console=tty > module /boot/vmlinuz-2.6.18.8-xen root=/dev/md0 ro vga=791 console=tty0 > root (hd0,0) > > > the xen kernel booting fine. i don''t known any more... > also i can''t find a usable documentation. the readme in source tree is not a > big help. ...make world && make install and you are ready, haha! > do i need a kernel named ...-xen-dom0? i''m very frustrated about. since 5 > day i try to get a minimal sucsess, but... argh! can any one help me to > understand this game? > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
hi folks, a new error. i can''t make steps forward )-: ok, my opteron was to old for xen, so we get today a brand new phenom 2 X3 and after the complete xen rebuild i get this: Error: (1, ''Internal error'', ''Could not open kernel image (2 = No such file or directory)'') What Kernel image? Which file/directory? why can not make xen clearly error messages? so i check my system and can''t find the error: ls /boot: vmlinuz-2.6.18.8-xen xen-3.3.1.gz xen-3.3.gz -> xen-3.3.1.gz xen-3.gz -> xen-3.3.1.gz xen.gz -> xen-3.3.1.gz xen-syms-3.3.1 cat /boot/grub/menu.lst title Xen 3.3 / XenLinux 2.6 kernel /boot/xen-3.gz vga=791 console=tty module /boot/vmlinuz-2.6.18.8-xen root=/dev/md0 ro vga=791 console=tty0 root (hd0,0) the xen kernel booting fine. i don''t known any more... also i can''t find a usable documentation. the readme in source tree is not a big help. ...make world && make install and you are ready, haha! do i need a kernel named ...-xen-dom0? i''m very frustrated about. since 5 day i try to get a minimal sucsess, but... argh! can any one help me to understand this game? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Alexia Benington schrieb:> Did you forget your init ramdisk? > > -Alex > > On Sat, Feb 14, 2009 at 9:49 PM, Mike Mildner > <m.mildner@kleiderschrank51.de> wrote: > >> hi folks, >> >> a new error. i can''t make steps forward )-: ok, my opteron was to old for >> xen, so we get today a brand new phenom 2 X3 and after the complete xen >> rebuild i get this: >> Error: (1, ''Internal error'', ''Could not open kernel image (2 = No such file >> or directory)'') What Kernel image? Which file/directory? why can not make >> xen clearly error messages? >> so i check my system and can''t find the error: >> ls /boot: >> vmlinuz-2.6.18.8-xen >> xen-3.3.1.gz >> xen-3.3.gz -> xen-3.3.1.gz >> xen-3.gz -> xen-3.3.1.gz >> xen.gz -> xen-3.3.1.gz >> xen-syms-3.3.1 >> >> cat /boot/grub/menu.lst >> title Xen 3.3 / XenLinux 2.6 >> kernel /boot/xen-3.gz vga=791 console=tty >> module /boot/vmlinuz-2.6.18.8-xen root=/dev/md0 ro vga=791 console=tty0 >> root (hd0,0) >> >> >> the xen kernel booting fine. i don''t known any more... >> also i can''t find a usable documentation. the readme in source tree is not a >> big help. ...make world && make install and you are ready, haha! >> do i need a kernel named ...-xen-dom0? i''m very frustrated about. since 5 >> day i try to get a minimal sucsess, but... argh! can any one help me to >> understand this game? >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >no, i build a kernel with all ''build-in'' they necessary for booting _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Initrd seems to be missing. # cd /usr/src/ # tar -zxvf xen-3.3.1.tar.gz # cd xen-3.3.1 This Xen build from source will clone linux-2.6.18-xen.hg tree to your local box and compile xen kernel with no manual intervention . Make sure commands:- # which hg # which git return path to binaries, required by build. # make world # make install Determine the name of the Xen Linux kernel version that was installed. # ls /lib/modules There should be a directory for the Xen Linux kernel (e.g.2.6.18.8-xen) Generate the module dependency list and map files # /sbin/depmod 2.6.18.8-xen Create the Xen initial ramdisk image # /sbin/mkinitrd /boot/initrd-2.6.18.8-xen.img 2.6.18.8-xen Disable tls # mv /lib64/tls /lib64/tls.disabled Set xend service to start # /sbin/chkconfig –add xend # /sbin/chkconfig xend on Install bridge-utils:- # yum install bridge-utils ***************************************** Create new /boot/grub/menu.lst entry ***************************************** title Xen-3.3.1 CentOS 5.2 x86_64 (2.6.18.8-xen) (/dev/sdb12) root (hd1,11) kernel /xen-3.3.gz module /vmlinuz-2.6.18.8-xen ro root=/dev/VolGroup01/LogVol00 rhgb quiet module /initrd-2.6.18.8-xen.img --- On Sat, 2/14/09, Mike Mildner <m.mildner@kleiderschrank51.de> wrote: From: Mike Mildner <m.mildner@kleiderschrank51.de> Subject: Re: [Xen-users] strange error masseages in xen To: "Alexia Benington" <alexbenington@gmail.com>, Xen-users@lists.xensource.com Date: Saturday, February 14, 2009, 10:09 PM Alexia Benington schrieb:> Did you forget your init ramdisk? > > -Alex > > On Sat, Feb 14, 2009 at 9:49 PM, Mike Mildner > <m.mildner@kleiderschrank51.de> wrote: > >> hi folks, >> >> a new error. i can''t make steps forward )-: ok, my opteron was toold for>> xen, so we get today a brand new phenom 2 X3 and after the completexen>> rebuild i get this: >> Error: (1, ''Internal error'', ''Could not open kernel image(2 = No such file>> or directory)'') What Kernel image? Which file/directory? why cannot make>> xen clearly error messages? >> so i check my system and can''t find the error: >> ls /boot: >> vmlinuz-2.6.18.8-xen >> xen-3.3.1.gz >> xen-3.3.gz -> xen-3.3.1.gz >> xen-3.gz -> xen-3.3.1.gz >> xen.gz -> xen-3.3.1.gz >> xen-syms-3.3.1 >> >> cat /boot/grub/menu.lst >> title Xen 3.3 / XenLinux 2.6 >> kernel /boot/xen-3.gz vga=791 console=tty >> module /boot/vmlinuz-2.6.18.8-xen root=/dev/md0 ro vga=791console=tty0>> root (hd0,0) >> >> >> the xen kernel booting fine. i don''t known any more... >> also i can''t find a usable documentation. the readme in sourcetree is not a>> big help. ...make world && make install and you are ready,haha!>> do i need a kernel named ...-xen-dom0? i''m very frustrated about.since 5>> day i try to get a minimal sucsess, but... argh! can any one help meto>> understand this game? >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >no, i build a kernel with all ''build-in'' they necessary for booting _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sun, Feb 15, 2009 at 9:49 AM, Mike Mildner <m.mildner@kleiderschrank51.de> wrote:> Error: (1, ''Internal error'', ''Could not open kernel image (2 = No such file > or directory)'') What Kernel image? Which file/directory? why can not make > xen clearly error messages?What distro are you using? Is this error on booting the dom0, or is it on booting domU?> cat /boot/grub/menu.lst > title Xen 3.3 / XenLinux 2.6 > kernel /boot/xen-3.gz vga=791 console=tty > module /boot/vmlinuz-2.6.18.8-xen root=/dev/md0 ro vga=791 console=tty0 > root (hd0,0)Does your distro support booting without initrd? AFAIK, RHEL/Centos requires initrd because there are some setup (e.g. LVM, udev) that is done in initrd. This is true even if you''ve built every necessary module as built-in. Regards, Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha schrieb:> On Sun, Feb 15, 2009 at 9:49 AM, Mike Mildner > <m.mildner@kleiderschrank51.de> wrote: > >> Error: (1, ''Internal error'', ''Could not open kernel image (2 = No such file >> or directory)'') What Kernel image? Which file/directory? why can not make >> xen clearly error messages? >> > > What distro are you using? > Is this error on booting the dom0, or is it on booting domU? > > >> cat /boot/grub/menu.lst >> title Xen 3.3 / XenLinux 2.6 >> kernel /boot/xen-3.gz vga=791 console=tty >> module /boot/vmlinuz-2.6.18.8-xen root=/dev/md0 ro vga=791 console=tty0 >> root (hd0,0) >> > > Does your distro support booting without initrd? AFAIK, RHEL/Centos > requires initrd because there are some setup (e.g. LVM, udev) that is > done in initrd. This is true even if you''ve built every necessary > module as built-in. > > Regards, > > Fajar > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >it comes when i try to start domU. and yes, i build kernel without inird because all needed things (ide-devices, fs etc) for booting are as built-in. and the dom0 kernel booting fine from my /dev/md0. i try many different builds last night but always when i run ''xm create mydomU.cfg'' this error occurs. what does this mean "could not open kernel image"? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sun, Feb 15, 2009 at 10:23 PM, Mike Mildner <m.mildner@kleiderschrank51.de> wrote:>>> Error: (1, ''Internal error'', ''Could not open kernel image (2 = No such >>> file> > it comes when i try to start domUAh, 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@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Feb 16, 2009 at 1:00 AM, Mike Mildner <m.mildner@kleiderschrank51.de> wrote:> >> What is the contents of your domU config file > > hm, thats it. kernel = "/usr/lib/xen/boot/hvmloader" > and hvmloader was not there. dam! but why can''t xen say: "hvmloader not > found in /usr/lib/xen/boot..."? > so i delete the complete source tree and rebuild now from scratch. stay > tuned... ;-) >Just a guess, but I think it won''t work :) hvmloader is used to create HVM guests. e.g. Fully-virtualized guests, like for Windows domU. For that to work, you need some additional stuff, like specifying which qemu device model to use, etc. At this point you need to stop to think what you''re trying to do : (1) Create a new dom0 system. For this you (probably) need to recompile xen. But since you say you inherited this system, chances are you need to keep it running. Which is why I don''t think you need this. (2) Create a HVM linux domU In this case, the best way to proceed is to copy your working Windows domU config and start from there. If your original "working" system also has "kernel = /usr/lib/xen/boot/hvmloader" line, then it''s also a HVM domU. Note that this will also explain why the original system works even without modifying inittab : HVM domU does not have a serial console by default, you access it using vnc to domU''s tty1. In this case you won''t nee da -xen kernel, you only need a normal kernel. (3) Create a PV Linux domU Depending on what you''re trying to do, you might need to recompile a xen kernel for domU. But again, depending on what you''re trying to do, the module might not be available for a xenified kernel. Examples of such modules : VMWare or Virtualbox kernel module. In any case, good luck! Regards, Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users