Xen project Mailing List

Thanks George,

xe-toolstack-restart wont help as the host crashed and rebooted itself without any scope to login and fire up.

Any other ideas around INTERNAL_ERROR: [ Xc.Error("getinfo failed: domain -1: hypercall 36 fail: 11: Resource temporarily unavailable (ret -1)") ]

Documents on google and citrix tell that hypercall fail has something to do with xen heap memory.

As per the logs I thought that only XAPI would have killed but it took down full host reboot which is annoying.

There were around 20 VMs on the host.

Regards,

Rushikesh

On Wed, Dec 19, 2012 at 3:20 PM, George Shuklin <george.shuklin@xxxxxxxxx> wrote:

I don't know about real crash reason, but all 'INTERNAL_ERROR' is very simple. Something broke around libxc, and xapi continue to attempt to do some operation with domain.

Next time (hope not happens) just try to xe-toolstack-restart if this will helps.

19.12.2012 01:46, Rushikesh Jadhav ÐÐÑÐÑ:
Hi everyone,

We faced a dom0 crash on XCP1.1 and Xen 3.4.2.

I've attached the log file for reference. On dom0 we could find only "Xc.Error" and then reboot of host. There is no information in /var/crash/ or other log files.

Interestingly the "INTERNAL_ERROR" variable keeps growing until a length and then host reboots. Possible memory overlap ? Could someone please help me diagnose this and sort out a way to avoid it in future ?

Thank you for reading.

Regards,
Rushikesh
_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

Re: [Xen-API] XCP 1.1 host crash due to VM console connection