That’s the funniest err I’ve seen so far in XenServer. But here’s how to fix it.
When you try to start vm you get this:
user@computer:$ sudo xe vm-start name-label=vm1
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")
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")
Restarting Xen tool stack should fix this problem
user@computer:$ sudo xe-toolstack-restart
Stopping xapi: .. [ OK ]
Stopping the v6 licensing daemon: [ OK ]
Stopping the memory ballooning daemon: [FAILED]
Stopping perfmon: [FAILED]
Stopping the fork/exec daemon: [ OK ]
Stopping the multipath alerting daemon: [ OK ]
Starting the multipath alerting daemon: [ OK ]
Starting the fork/exec daemon: [ OK ]
Starting perfmon: [ OK ]
Starting the memory ballooning daemon: [ OK ]
Starting the v6 licensing daemon: [ OK ]
Starting xapi: ......start-of-day complete. [ OK ]
done.
Stopping xapi: .. [ OK ]
Stopping the v6 licensing daemon: [ OK ]
Stopping the memory ballooning daemon: [FAILED]
Stopping perfmon: [FAILED]
Stopping the fork/exec daemon: [ OK ]
Stopping the multipath alerting daemon: [ OK ]
Starting the multipath alerting daemon: [ OK ]
Starting the fork/exec daemon: [ OK ]
Starting perfmon: [ OK ]
Starting the memory ballooning daemon: [ OK ]
Starting the v6 licensing daemon: [ OK ]
Starting xapi: ......start-of-day complete. [ OK ]
done.
Start vm:
user@computer:$ sudo xe vm-start name-label=vm1
user@computer:$ sudo xe vm-list name-label=vm1
uuid ( RO) : fde2f917-7612-8d09-9845-019bd409d744
name-label ( RW): vm1
power-state ( RO): running
uuid ( RO) : fde2f917-7612-8d09-9845-019bd409d744
name-label ( RW): vm1
power-state ( RO): running