search for: nowatchdog

...ero|server_init D:1691a70e8b4a|startup] task [Setting up domain 0 xenstore keys] exception: Xs.Failed_to_connect Oct 9 16:45:57 xenhost-1 xapi: [error|xenhost-1|0 thread_zero||xapi] Caught exception at toplevel: 'Xs.Failed_to_connect' Oct 9 16:45:57 xenhost-1 xcp-fe: 2567 (/usr/sbin/xapi -nowatchdog -writereadyfile /var/run/xapi_startup.cookie -writ...) exitted with code 2 Oct 9 16:45:57 xenhost-1 xapi: [ info|xenhost-1|0 thread_zero||watchdog] received exit code 2 Oct 9 16:45:57 xenhost-1 xapi: [ info|xenhost-1|0 thread_zero||watchdog] Received bad exit, retrying Oct 9 16:45:57 xenhost-1 x...

...the initial install. Thank you for the help!! ** paste ** Nov 29 18:10:37 xenserver-nordlund xsconsole: Displaying ''xapi is not running'' dialogue-bash: Nov: command not found [root@xenserver-nordlund log]# Nov 29 18:02:53 xenserver-nordlund fe: 8650 (/opt/xensource/bin/xapi -nowatchdog -writereadyfile /var/run/xapi_startup.coo...) exitted with code 2 -bash: syntax error near unexpected token `('' [root@xenserver-nordlund log]# Nov 29 18:02:54 xenserver-nordlund fe: 8698 (/opt/xensource/bin/xapi -nowatchdog -writereadyfile /var/run/xapi_startup.coo...) exitted with cod...

Package: xcp-squeezed Version: 1.3.2-9 Severity: important When trying to start a guest I get: # xe vm-start name-label=squeeze-2 The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: Failure("The ballooning daemon is not running") If I then manually run "/etc/init.d/xcp-squeezed

This issue I am encountering seems to only happen on multi-socket machines. It also does not help that the only multi-socket box I have is an Romley-EP (so two socket SandyBridge CPUs). The other SandyBridge boxes I''ve (one socket) are not showing this. Granted they are also a different model (42). The problem is that when I run ''perf top'' within an SMP PVHVM guest,