I just installed a CentOs 5 domU system on a CentOS 5 dom0 system following the instructions detailed here: http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU.
The installation went through successfully. After installation, however, pygrub can't find a kernel.
This is the xen cfg file I'm using:
bootloader="/usr/bin/pygrub" name = "testsrv" memory = "2048" disk = [ 'tap:aio:/root/testsrv.img,xvda,w', ] vif = [ 'bridge=xenbr0', ] vcpus=2 on_reboot = 'destroy' on_crash = 'destroy'
this is the error:
Traceback (most recent call last): File "/usr/bin/pygrub", line 499, in ? curses.wrapper(run_main) File "/usr/lib/python2.4/curses/wrapper.py", line 44, in wrapper return func(stdscr, *args, **kwds) File "/usr/bin/pygrub", line 455, in run_main sel = g.run() File "/usr/bin/pygrub", line 358, in run self.run_main(timeout) File "/usr/bin/pygrub", line 381, in run_main draw() File "/usr/bin/pygrub", line 366, in draw self.draw_main_windows() File "/usr/bin/pygrub", line 159, in draw_main_windows curses.use_default_colors() _curses.error: use_default_colors() returned ERR No handlers could be found for logger "xend" Error: Boot loader didn't return any data! Usage: xm create <ConfigFile> [options] [vars]
Create a domain based on <ConfigFile>.
Options:
Anything I'm missing? Thanks for any help.
On Mon, 2007-05-21 at 11:26 -0700, Fong Vang wrote:
I just installed a CentOs 5 domU system on a CentOS 5 dom0 system following the instructions detailed here: http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU.
The installation went through successfully. After installation, however, pygrub can't find a kernel.
No, this:
File "/usr/bin/pygrub", line 366, in draw self.draw_main_windows() File "/usr/bin/pygrub", line 159, in draw_main_windows curses.use_default_colors() _curses.error: use_default_colors() returned ERR No handlers could be found for logger "xend" Error: Boot loader didn't return any data! Usage: xm create <ConfigFile> [options] [vars]
is a curses error. How are you creating the domain? Do you happen to use "xm create -c" over SSH? If so, could you try to create the domain with "xm create" (without -c), and attach the console to the domain later with "xm console"?
-- Daniel
pygrub wasn't able to find the kernel so I mounted the image and copied out the kernel and ramdisk. It still didn't work with this kernel and ramdisk -- cannot find root device (I added a root= line). I had to recreate a new ramdisk using mkinitrd before I could boot this system. For now, this is good enough. I'll have to go back and dig deeper at a later time.
Thank you for the response, though.
On 5/21/07, Daniel de Kok danieldk@pobox.com wrote:
On Mon, 2007-05-21 at 11:26 -0700, Fong Vang wrote:
I just installed a CentOs 5 domU system on a CentOS 5 dom0 system following the instructions detailed here: http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU.
The installation went through successfully. After installation, however, pygrub can't find a kernel.
No, this:
File "/usr/bin/pygrub", line 366, in draw self.draw_main_windows() File "/usr/bin/pygrub", line 159, in draw_main_windows curses.use_default_colors() _curses.error: use_default_colors() returned ERR No handlers could be found for logger "xend" Error: Boot loader didn't return any data! Usage: xm create <ConfigFile> [options] [vars]
is a curses error. How are you creating the domain? Do you happen to use "xm create -c" over SSH? If so, could you try to create the domain with "xm create" (without -c), and attach the console to the domain later with "xm console"?
-- Daniel
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Mon, 2007-05-21 at 15:48 -0700, Fong Vang wrote:
pygrub wasn't able to find the kernel so I mounted the image and copied out the kernel and ramdisk. It still didn't work with this kernel and ramdisk -- cannot find root device (I added a root= line). I had to recreate a new ramdisk using mkinitrd before I could boot this system. For now, this is good enough. I'll have to go back and dig deeper at a later time.
As I said, the problem is not finding the kernel. This workaround works, because it does not display the GRUB menu, and that is where it fails with pygrub (it can't get the necessary terminal features to display the GRUB menu). It fails in code completely unrelated to getting the kernel/initrd images from the disk image.
-- Daniel
-
Daniel de Kok -
Fong Vang