From mboxrd@z Thu Jan 1 00:00:00 1970 From: cyberhawk001@gmail.com Subject: [Xen-users] Why the need for "-f" with XL in Xen 4.2 rev-25467 Date: Wed, 20 Jun 2012 20:34:22 -0400 Message-ID: <4FE26C0E.9070104@gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0760382024588517640==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --===============0760382024588517640== Content-Type: multipart/alternative; boundary="------------060306010903060306020708" This is a multi-part message in MIME format. --------------060306010903060306020708 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Just out of annoyance more than curiosity, but ever since I started using Xen 4.2-unstable rev-25467, every time I try to run "sudo xl create ", or "sudo xl reboot", or "sudo xl destroy", it always gives me this message: "*xend is running, which prevents xl from working correctly. If you still want to force the execution of xl please use the -f option*" I am now forced to use the "-f" option anytime i am using the xl toolstack. It never used to be that way going back to Xen 4.2-unstable rev-25459. I was reading something about this a while ago on the Xen-devel list, but forget what. SOOO, any logical reason for the need to use the FORCE option every time you run the XL command? AND assuming it is not something on my setup that is causing it, will it always stay like this in future revisions? Thank you for any enlightening --------------060306010903060306020708 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Just out of annoyance more than curiosity, but ever since I started using Xen 4.2-unstable rev-25467, every time I try to run "sudo xl create <domu_config_file>", or "sudo xl reboot", or "sudo xl destroy", it always gives me this message:

"xend is running, which prevents xl from working correctly.
If you still want to force the execution of xl please use the -f option"

I am now forced to use the "-f" option anytime i am using the xl toolstack. It never used to be that way going back to Xen 4.2-unstable rev-25459. I was reading something about this a while ago on the Xen-devel list, but forget what.

SOOO, any logical reason for the need to use the FORCE option every time you run the XL command? AND assuming it is not something on my setup that is causing it, will it always stay like this in future revisions?

Thank you for any enlightening
--------------060306010903060306020708-- --===============0760382024588517640== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============0760382024588517640==--