On 3/27/06, Winston Chang <winston@xxxxxxxxxx> wrote:
That sounds like a good possiblity since I'm at work and sshd to it, I'll try running it on the box and see what happens.
I had the same problem and I just figured out a workaround. The
issue is that the curses screen-drawing library isn't happy -- it
can't print the nice grub-like kernel selection menu. On my
computer, this is because I sshed in from a Mac Terminal window.
When I connected via an xterm, it worked fine.
Seems like a bug to me.
--Winston
That sounds like a good possiblity since I'm at work and sshd to it, I'll try running it on the box and see what happens.
On Mar 27, 2006, at 10:34 AM, Justin Conover wrote:
> I created a guest with the python script xenguest-install.py when I
> run
>
> # /usr/sbin/xm create -c webserver1
>
> I get the following error
>
>
> Traceback (most recent call last):
> File "/usr/bin/pygrub", line 258, 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 214, in run_main
> sel = main(cf)
> File "/usr/bin/pygrub", line 162, in main
> (stdscr, win) = draw_window()
> File "/usr/bin/pygrub", line 33, in draw_window
> curses.use_default_colors ()
> _curses.error: use_default_colors() returned ERR
> Error: Boot loader didn't return any data!
> #xm log (3-27-06)
>
> [2006-03-27 09:30:26 xend] ERROR (XendBootloader:84) Boot loader
> didn't return any data!
> [2006-03-27 09:32:18 xend] INFO (SrvDaemon:192) Xend stopped due to
> signal 15.
> [2006-03-27 09:32:18 xend] INFO (SrvDaemon:285) Xend Daemon started
> [2006-03-27 09:32:18 xend] INFO (SrvDaemon:289) Xend changeset:
> unavailable .
> [2006-03-27 09:32:18 xend.XendDomainInfo] DEBUG (XendDomainInfo:
> 199) XendDomainInfo.recreate({'paused': 0, 'cpu_time':
> 13021637090975L, 'ssidref': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0,
> 0, 0, 0, 0, 0, 0, 0, 0], 'shutdown_reason': 0, 'dying': 0, 'dom':
> 0, 'mem_kb': 762984, 'maxmem_kb': -4, 'max_vcpu_id': 1, 'crashed':
> 0, 'running': 1, 'shutdown': 0, 'online_vcpus': 2, 'blocked': 0})
> [2006-03-27 09:32:18 xend.XendDomainInfo] INFO (XendDomainInfo:211)
> Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000.
> [2006-03-27 09:32:18 xend] DEBUG (XendDomain:151) number of vcpus
> to use is 0
> [2006-03-27 09:32:19 xend] INFO (SrvServer:114) unix path=/var/lib/
> xend/xend-socket
> [2006-03-27 09:32:22 xend] ERROR (XendBootloader:84) Boot loader
> didn't return any data!
>
> This file compared to the examples seems to be missing info, but
> that might be because the create -c didn't start/finish what it does.
>
>
> # cat /etc/xen/webserver1
>
> # Automatically generated xen config file
> name = "webserver1"
> memory = "256"
> disk = [ 'file:/xen/webserver1,xvda,w' ]
> vif = [ 'mac=00:16:3e:14:83:a4' ]
> bootloader="/usr/bin/pygrub"
>
> on_reboot = 'restart'
> on_crash = 'restart'
>
>
> # xm list
> Name ID Mem(MiB) VCPUs State Time(s)
> Domain-0 0 745 2 r----- 13017.5
> --
>
> Fedora-xen@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/fedora-xen
