[Xen-devel] domU still not rebooting in 3.0.2

["Brian Hays" <brian.hays@xxxxxxxxx>]

After upgrading to 3.0.2 I tried rebooting a domU (a problem sometimes in 3.0.1 related to bug 514) it failed to come back up. This was in my xend.log. ("Refusing to restart to avoid loops." .... )

[2006-04-11 20:53:39 
xend.XendDomainInfo] DEBUG (__init__:988) Storing domain details: {'console/ring-ref': '223144', 'console/port': '2', 'name': 'vmtest1', 'console/limit': '1048576', 'vm': '/vm/c73d7a4b-4747-fe91-dbc4-0408183a9456', 'domid': '10', 'cpu/0/availability': 'online', 'memory/target': '98304', 'store/ring-ref': '223145', 'store/port': '1'}
[2006-04-11 20:53:39 xend.XendDomainInfo] DEBUG (__init__:988) XendDomainInfo.handleShutdownWatch
[2006-04-11 20:53:39 xend.XendDomainInfo] WARNING (__init__:988) Domain has crashed: name=vmtest1 id=10.
[2006-04-11 20:53:39 
xend.XendDomainInfo] ERROR (__init__:988) VM vmtest1 restarting too fast (1.396226 seconds since the last restart).  Refusing to restart to avoid loops.
[2006-04-11 20:53:39 xend.XendDomainInfo] DEBUG (__init__:988) XendDomainInfo.destroy
: domid=10
[2006-04-11 20:53:39 xend.XendDomainInfo] DEBUG (__init__:988) XendDomainInfo.destroyDomain(10)

Is there a way to adjust the parameter that tells Xen the domain is "restarting too fast"? Would adjusting that parameter fix this?

Thank you,
Brian
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel