On Wed, 8 Jul 2009, Giorgenes Gelatti wrote:
> Hi there,
>
> i've isntalled xen 3.4 from source on debian lenny and got the following
> error when running hvm + stubdomain (hvm only
> works fine):
>
> + /bin/sh -c 'xm create -c /etc/xen/stubdoms/xmexample.hvm-dm target=15
> memory=32 extra=" -d 15"'
> Using config file "/etc/xen/stubdoms/xmexample.hvm-dm".
> Started domain xmexample.hvm-dm (id=16)
> Using config file "/etc/xen/stubdoms/xmexample.hvm-dm".
> Unexpected error: <type 'exceptions.OSError'>
>
> Please report to xen-devel@xxxxxxxxxxxxxxxxxxx
> Traceback (most recent call last):
> File "/usr/sbin/xm", line 7, in <module>
> main.main(sys.argv)
> File "usr/lib/python2.5/site-packages/xen/xm/main.py", line 2979, in main
> _, rc = _run_cmd(cmd, cmd_name, args)
> File "usr/lib/python2.5/site-packages/xen/xm/main.py", line 3003, in
> _run_cmd
> return True, cmd(args)
> File "<string>", line 1, in <lambda>
> File "usr/lib/python2.5/site-packages/xen/xm/main.py", line 1360, in
> xm_importcommand
> cmd.main([command] + args)
> File "usr/lib/python2.5/site-packages/xen/xm/create.py", line 1371, in main
> do_console(sxp.child_value(config, 'name', -1))
> File "usr/lib/python2.5/site-packages/xen/xm/create.py", line 1398, in
> do_console
> (p, rv) = os.waitpid(cpid, os.WNOHANG)
> OSError: [Errno 10] No child processes
>
>
> This is the content of /etc/xen/stubdoms/xmexample.hvm-dm:
> #This file is autogenerated, edit xmexample.hvm instead!
> kernel = '/usr/lib/xen/boot/ioemu-stubdom.gz'
> vfb = ['sdl=0, opengl=1, xauthority=/root/.Xauthority, vnc=1, vncdisplay=0,
> vnclisten=0.0.0.0, vncunused=1']
> disk = [
> 'tap:aio:/home/ggelatti/disk.img,hda:disk,w','tap:aio:/home/ggelatti/debian-501-i386-CD-1.iso,hdc:cdrom,r'
> ]
> vif = [ 'mac=00:16:3e:50:a5:ad' ]
>
>
> It looks like something is wrong with the generated stub domain file.
>
> Any help?
> Thank you.
>
> PS: I've posted on xen-devel cse the log file told me so :P
>
Unfortunately the error message is just the generic error message you
get when the stubdom fails to start; also the generated config file
looks fine.
It is difficult to understand what the problem is with these
informations.
If you want to track down this bug you need to recompile xen and
stubdoms with "debug = y" in Config.mk, then try to start a stubdom
again and send me the output of "xm dmesg".
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home