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@lists.xensource.com
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
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
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@lists.xensource.com > 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@lists.xensource.com http://lists.xensource.com/xen-devel
I''ve recompiled and rerunned it with debug, the results are attached. For the sake of reference, the domain id in question was 5. Thanks in advance. []''s 2009/7/9 Stefano Stabellini <stefano.stabellini@eu.citrix.com>> 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@lists.xensource.com > > 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@lists.xensource.com http://lists.xensource.com/xen-devel
Ops, forgot the xm dmesg. attached. 2009/7/9 Giorgenes Gelatti <giorgenes@gmail.com>> I''ve recompiled and rerunned it with debug, the results are attached. > For the sake of reference, the domain id in question was 5. > > Thanks in advance. > > []''s > > 2009/7/9 Stefano Stabellini <stefano.stabellini@eu.citrix.com> > > 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@lists.xensource.com >> > 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@lists.xensource.com http://lists.xensource.com/xen-devel
On Thu, 9 Jul 2009, Giorgenes Gelatti wrote:> Ops, forgot the xm dmesg. attached. >It seems that the stubdom fails to start with a memory problem: (XEN) memory.c:128:d0 Could not allocate order=9 extent: id=1 memflags=0 (2 of 3) I have seen this message appearing on the console only recently and since then stubdoms fail to start. Do anyone know the reason for this? _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I''ve read something out there about stubdomains failing with non-PAE xen, could it have something to do with it? Where could I enable it in the sources? Thank you. 2009/7/10 Stefano Stabellini <stefano.stabellini@eu.citrix.com>> On Thu, 9 Jul 2009, Giorgenes Gelatti wrote: > > Ops, forgot the xm dmesg. attached. > > > > It seems that the stubdom fails to start with a memory problem: > > (XEN) memory.c:128:d0 Could not allocate order=9 extent: id=1 memflags=0 (2 > of 3) > > I have seen this message appearing on the console only recently and > since then stubdoms fail to start. > Do anyone know the reason for this? > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Fri, 10 Jul 2009, Giorgenes Gelatti wrote:> I''ve read something out there about stubdomains failing with non-PAE xen, could it have something to do with it? > Where could I enable it in the sources? > > Thank you. > > 2009/7/10 Stefano Stabellini <stefano.stabellini@eu.citrix.com> > On Thu, 9 Jul 2009, Giorgenes Gelatti wrote: > > Ops, forgot the xm dmesg. attached. > > > > It seems that the stubdom fails to start with a memory problem: > > (XEN) memory.c:128:d0 Could not allocate order=9 extent: id=1 memflags=0 (2 of 3) > > I have seen this message appearing on the console only recently and > since then stubdoms fail to start. > Do anyone know the reason for this? >The patch I just sent should fix the issue. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
To which version should I apply the patch? My version (3.4) doesn''t have the lines in the patch. I tryed adding the lines to the stubdom-dm but it didn''t work. Should I get the "unstable" version? Thank you. []''s 2009/7/10 Stefano Stabellini <stefano.stabellini@eu.citrix.com>> On Fri, 10 Jul 2009, Giorgenes Gelatti wrote: > > I''ve read something out there about stubdomains failing with non-PAE xen, > could it have something to do with it? > > Where could I enable it in the sources? > > > > Thank you. > > > > 2009/7/10 Stefano Stabellini <stefano.stabellini@eu.citrix.com> > > On Thu, 9 Jul 2009, Giorgenes Gelatti wrote: > > > Ops, forgot the xm dmesg. attached. > > > > > > > It seems that the stubdom fails to start with a memory problem: > > > > (XEN) memory.c:128:d0 Could not allocate order=9 extent: id=1 memflags=0 > (2 of 3) > > > > I have seen this message appearing on the console only recently and > > since then stubdoms fail to start. > > Do anyone know the reason for this? > > > > The patch I just sent should fix the issue. >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Fri, 10 Jul 2009, Giorgenes Gelatti wrote:> To which version should I apply the patch? > My version (3.4) doesn''t have the lines in the patch. > I tryed adding the lines to the stubdom-dm but it didn''t work.Uhm.. I couldn''t reproduce the issue on 3.4 testing. If you are using 3.4, which CS is the tip of you xen and qemu trees?> Should I get the "unstable" version?The "unstable" version works for me at the moment, you can give it a try. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
#xen-3.4.0> cat .hg_archival.txt repo: ab039beb22dc9d53f224a5ef2ef88d534b561898 node: d2a5c477c647dc7b3f51a761ab481ed80d5a1771 2009/7/10 Stefano Stabellini <stefano.stabellini@eu.citrix.com>> On Fri, 10 Jul 2009, Giorgenes Gelatti wrote: > > To which version should I apply the patch? > > My version (3.4) doesn''t have the lines in the patch. > > I tryed adding the lines to the stubdom-dm but it didn''t work. > > Uhm.. I couldn''t reproduce the issue on 3.4 testing. > If you are using 3.4, which CS is the tip of you xen and qemu trees? > > > Should I get the "unstable" version? > > The "unstable" version works for me at the moment, you can give it a > try. >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Well, I''ve just find out that I was missing a basic step: running fs-backend. I couldn''t run the stubdomain running it either. Now i''m trying with xen-unstable and I''m getting this error: # xm create xmexample.hvm-stubdom Using config file "./xmexample.hvm-stubdom". Error: Device 768 (vbd) could not be connected. File /home/ggelatti/disk.img is loopback-mounted through /dev/loop2, which is mounted in a guest domain, and so cannot be mounted now. Any thoughts on that? Tks again. 2009/7/13 Giorgenes Gelatti <giorgenes@gmail.com>> #xen-3.4.0> cat .hg_archival.txt > repo: ab039beb22dc9d53f224a5ef2ef88d534b561898 > node: d2a5c477c647dc7b3f51a761ab481ed80d5a1771 > > > 2009/7/10 Stefano Stabellini <stefano.stabellini@eu.citrix.com> > >> On Fri, 10 Jul 2009, Giorgenes Gelatti wrote: >> > To which version should I apply the patch? >> > My version (3.4) doesn''t have the lines in the patch. >> > I tryed adding the lines to the stubdom-dm but it didn''t work. >> >> Uhm.. I couldn''t reproduce the issue on 3.4 testing. >> If you are using 3.4, which CS is the tip of you xen and qemu trees? >> >> > Should I get the "unstable" version? >> >> The "unstable" version works for me at the moment, you can give it a >> try. >> > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Tue, 14 Jul 2009, Giorgenes Gelatti wrote:> Well, I''ve just find out that I was missing a basic step: running fs-backend. > I couldn''t run the stubdomain running it either. > Now i''m trying with xen-unstable and I''m getting this error: > > # xm create xmexample.hvm-stubdom > Using config file "./xmexample.hvm-stubdom". > Error: Device 768 (vbd) could not be connected. > File /home/ggelatti/disk.img is loopback-mounted through /dev/loop2, > which is mounted in a guest domain, > and so cannot be mounted now. > > Any thoughts on that? > Tks again. >Try unmouting /dev/loop2, it probably remained mounted from one of your previous failed attempts. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I think it isn''t the case. mount and losetup don''t show anything. I looks like it just happens the first time I run xm create. If I try it again it "works". Well, the first time it "worked" it freezed the whole system actually. After reboot, I issued xm create again, which caused the same error again. I rerunned it and this time it created the VM pair: the hvm and the stubdomain. Connecting to the VNC interface works, but only shows a black screen. Running xm list shows the stubdomain isn''t running at all: # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 252 2 r----- 204.0 debstubhvm 3 128 1 r----- 9356.5 debstubhvm-dm 4 32 1 -b---- 0.0 the stubdomain status started with "p", then I unpaused it manually and it went into "b" forever. Any clue? Thanks for your help. 2009/7/14 Stefano Stabellini <stefano.stabellini@eu.citrix.com>> On Tue, 14 Jul 2009, Giorgenes Gelatti wrote: > > Well, I''ve just find out that I was missing a basic step: running > fs-backend. > > I couldn''t run the stubdomain running it either. > > Now i''m trying with xen-unstable and I''m getting this error: > > > > # xm create xmexample.hvm-stubdom > > Using config file "./xmexample.hvm-stubdom". > > Error: Device 768 (vbd) could not be connected. > > File /home/ggelatti/disk.img is loopback-mounted through /dev/loop2, > > which is mounted in a guest domain, > > and so cannot be mounted now. > > > > Any thoughts on that? > > Tks again. > > > > Try unmouting /dev/loop2, it probably remained mounted from one of your > previous failed attempts. > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Tue, 14 Jul 2009, Giorgenes Gelatti wrote:> I think it isn''t the case. mount and losetup don''t show anything. > I looks like it just happens the first time I run xm create. > If I try it again it "works". > Well, the first time it "worked" it freezed the whole system actually. > After reboot, I issued xm create again, which caused the same error again. > I rerunned it and this time it created the VM pair: the hvm and the stubdomain. > Connecting to the VNC interface works, but only shows a black screen. > Running xm list shows the stubdomain isn''t running at all: > > # xm list > Name ID Mem VCPUs State Time(s) > Domain-0 0 252 2 r----- 204.0 > debstubhvm 3 128 1 r----- 9356.5 > debstubhvm-dm 4 32 1 -b---- 0.0 > > the stubdomain status started with "p", then I unpaused it manually and it went into "b" forever. > > Any clue?It is hard to say with these informations. What does the xm dmesg say? Could you also send the qemu and stubdom logs? _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Attached. tks again []''s 2009/7/15 Stefano Stabellini <stefano.stabellini@eu.citrix.com>> On Tue, 14 Jul 2009, Giorgenes Gelatti wrote: > > I think it isn''t the case. mount and losetup don''t show anything. > > I looks like it just happens the first time I run xm create. > > If I try it again it "works". > > Well, the first time it "worked" it freezed the whole system actually. > > After reboot, I issued xm create again, which caused the same error > again. > > I rerunned it and this time it created the VM pair: the hvm and the > stubdomain. > > Connecting to the VNC interface works, but only shows a black screen. > > Running xm list shows the stubdomain isn''t running at all: > > > > # xm list > > Name ID Mem VCPUs State > Time(s) > > Domain-0 0 252 2 r----- > 204.0 > > debstubhvm 3 128 1 r----- > 9356.5 > > debstubhvm-dm 4 32 1 > -b---- 0.0 > > > > the stubdomain status started with "p", then I unpaused it manually and > it went into "b" forever. > > > > Any clue? > > It is hard to say with these informations. > What does the xm dmesg say? > Could you also send the qemu and stubdom logs?_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Wed, 15 Jul 2009, Giorgenes Gelatti wrote:> Attached. > > tks again >Unfortunately there is nothing on the logs: did you compile xen and stubdom with debug = y? _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Xen is crashing on boot with debug = y :( It gives a "FATAL PAGE FAULT" and kernel panics. 2009/7/15 Stefano Stabellini <stefano.stabellini@eu.citrix.com>> On Wed, 15 Jul 2009, Giorgenes Gelatti wrote: > > Attached. > > > > tks again > > > > Unfortunately there is nothing on the logs: did you compile xen and > stubdom with debug = y? > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Hi, Tks for all the help. It''s seems like i''ve being failing miserably to use the kernels that comes with the xen source. I''ve tryed different versions: 3.4.0 stable, 3.5-unstable, and 3.4.1-rc7. All kernels gave me different errors, some crashed with the debug options on. But the setup that ended up working for me was xen 3.5.1-rc7 with kernel 3.6.26-2 from the debian packages. The one released with the xen source didn''t work for me. Now I''ve successfully ran an hvm with a stubdomain. tks. 2009/7/16 Giorgenes Gelatti <giorgenes@gmail.com>> Xen is crashing on boot with debug = y :( > It gives a "FATAL PAGE FAULT" and kernel panics. > > > 2009/7/15 Stefano Stabellini <stefano.stabellini@eu.citrix.com> > >> On Wed, 15 Jul 2009, Giorgenes Gelatti wrote: >> >> > Attached. >> > >> > tks again >> > >> >> Unfortunately there is nothing on the logs: did you compile xen and >> stubdom with debug = y? >> >> >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel