[Xen-bugs] [Bug 124] running reboot within a domU doesn't bring the domain back up after shutdown

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=124





------- Additional Comments From sean@xxxxxxxxx  2005-09-16 20:24 -------
There seems to be some disconnect in what Xend is seeing during the reboot
process.  After running reboot in the DomU the following appears in xend.log:

[2005-09-16 16:19:20 xend] DEBUG (XendDomain:240) XendDomain>reap> domain died
name=Suse9.2 id=11
[2005-09-16 16:19:20 xend] DEBUG (XendDomain:243) XendDomain>reap> shutdown
name=Suse9.2 id=11 reason=reboot
[2005-09-16 16:19:20 xend] DEBUG (XendDomain:472) domain_restart_schedule> 11
reboot 0
[2005-09-16 16:19:20 xend] INFO (XendDomain:479) Scheduling restart for domain:
name=Suse9.2 id=11
[2005-09-16 16:19:20 xend] INFO (XendDomain:514) Destroying domain: name=Suse9.2
[2005-09-16 16:19:20 xend] INFO (XendRoot:141) EVENT> xend.domain.exit
['Suse9.2', 11, 'reboot']
[2005-09-16 16:19:20 xend] INFO (XendRoot:141) EVENT> xend.domain.restart
['Suse9.2', 11, 'schedule']
[2005-09-16 16:19:20 xend] INFO (XendRoot:141) EVENT> xend.domain.destroy
['Suse9.2', 11]

Which all appears rather reasonable.  However the DomU has not rebooted yet.  If
you run xm list you get the following:

root@lrr:~/xen-unstable> xm list     
Name              Id  Mem(MB)  CPU VCPU(s)  State  Time(s)
Domain-0           0      123    0      1   r----    105.6
Fedora3            1      127    3      1   -b---     39.7
Fedora4            2      127    1      1   -b---     12.8
Mandrake10.2       4      127    1      1   -b---     17.3
Mandrake2006       3      127    3      1   -b---     12.6
Suse9.2           11        0    3      1   ---s-     11.4

Which shows the DomU is somewhat hung in shutdown state.  More interestingly the
following exception shows up in xend.log when you run xm list:

[2005-09-16 16:19:33 xend] ERROR (XendDomainInfo:128) domain_getinfo(11) failed,
ignoring
Traceback (most recent call last):
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 123, in dom_get
    domlist = xc.domain_getinfo(dom, 1)
error: (3, 'No such process')

Which means that xc no longer knows anything about the domain.


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs