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==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rolu Subject: Re: [Xen-users] Why the need for "-f" with XL in Xen 4.2 rev-25467 Date: Thu, 21 Jun 2012 04:07:36 +0200 Message-ID: References: <4FE26C0E.9070104@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4FE26C0E.9070104@gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: cyberhawk001@gmail.com Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On Thu, Jun 21, 2012 at 2:34 AM, wrote: > 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? > Xend and xl are part of different toolstacks and should not be used together. You should investigate why you have xend running, most likely it shouldn't be. Xen 4.2 and newer have the xl toolstack as default. Xen 4.1 and older have the xend/xm toolstack as default. See http://wiki.xen.org/wiki/Choice_of_Toolstacks for more info. From mboxrd@z Thu Jan 1 00:00:00 1970 From: cyberhawk001@gmail.com Subject: Re: [Xen-users] Why the need for "-f" with XL in Xen 4.2 rev-25467 Date: Wed, 20 Jun 2012 22:52:23 -0400 Message-ID: <4FE28C67.30000@gmail.com> References: <4FE26C0E.9070104@gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8495108855433470291==" Return-path: In-Reply-To: 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. --===============8495108855433470291== Content-Type: multipart/alternative; boundary="------------090901050102060909010405" This is a multi-part message in MIME format. --------------090901050102060909010405 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 6/20/2012 10:07 PM, Rolu wrote: > On Thu, Jun 21, 2012 at 2:34 AM, wrote: >> 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? >> > Xend and xl are part of different toolstacks and should not be used > together. You should investigate why you have xend running, most > likely it shouldn't be. > > Xen 4.2 and newer have the xl toolstack as default. > Xen 4.1 and older have the xend/xm toolstack as default. > > Seehttp://wiki.xen.org/wiki/Choice_of_Toolstacks for more info. Yes i know the difference between XL and XM toolstacks and have been using Xen 4.2-unstable with XL since the beginning of my Xen journey. As i mentioned before, i never had this issue with a previous Xen 4.2 person as i mentioned it, HOWEVER i have messed around with XCP and different version of Xen on this Debian before, SO very likely i forgot to remove or uninstall something between changes, just trying to figure out how to make it stop asking me to force anything. I was checking to make sure XEND was stopped by running "*sudo /etc/init.d/xend stop*" and i get an error message as below: *Traceback (most recent call last): file "usr/sbin/xen", line 36, in from xen.xend.server import SrvDaemon ImportError: No module named xen.xend.server* WHICH also happens to be the exact same message i have been getting every time i shut down Dom0 for quite a while now and been meaning to ask about that. Once i run "*sudo update-rc.d xend stop*" than i am able to run "*sudo xl create*" without the FORCE option, but once i reboot the system, it comes back and have to run the "*sudo update-rc.d xend stop*" all over again. SO wondering how to disable xend from loading at boot time? Or just get rid of whatever remnants floating around that is interfering with things. --------------090901050102060909010405 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 6/20/2012 10:07 PM, Rolu wrote: 
On Thu, Jun 21, 2012 at 2:34 AM,  <cyberhawk001@gmail.com> wrote:

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?


Xend and xl are part of different toolstacks and should not be used
together. You should investigate why you have xend running, most
likely it shouldn't be.

Xen 4.2 and newer have the xl toolstack as default.
Xen 4.1 and older have the xend/xm toolstack as default.

See http://wiki.xen.org/wiki/Choice_of_Toolstacks for more info.

Yes i know the difference between XL and XM toolstacks and have been using Xen 4.2-unstable with XL since the beginning of my Xen journey. As i mentioned before, i never had this issue with a previous Xen 4.2 person as i mentioned it, HOWEVER i have messed around with XCP and different version of Xen on this Debian before, SO very likely i forgot to remove or uninstall something between changes, just trying to figure out how to make it stop asking me to force anything.

I was checking to make sure XEND was stopped by running "sudo /etc/init.d/xend stop" and i get an error message as below:

Traceback (most recent call last):
  file "usr/sbin/xen", line 36, in <module>
    from xen.xend.server import SrvDaemon
ImportError: No module named xen.xend.server

WHICH also happens to be the exact same message i have been getting every time i shut down Dom0 for quite a while now and been meaning to ask about that.

Once i run "sudo update-rc.d xend stop" than i am able to run "sudo xl create" without the FORCE option, but once i reboot the system, it comes back and have to run the "sudo update-rc.d xend stop" all over again. SO wondering how to disable xend from loading at boot time? Or just get rid of whatever remnants floating around that is interfering with things.



--------------090901050102060909010405-- --===============8495108855433470291== 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 --===============8495108855433470291==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [Xen-users] Why the need for "-f" with XL in Xen 4.2 rev-25467 Date: Thu, 21 Jun 2012 06:20:36 +0100 Message-ID: <1340256036.4998.6.camel@dagon.hellion.org.uk> References: <4FE26C0E.9070104@gmail.com> <4FE28C67.30000@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4FE28C67.30000@gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "cyberhawk001@gmail.com" Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On Thu, 2012-06-21 at 03:52 +0100, cyberhawk001@gmail.com wrote: > Once i run "sudo update-rc.d xend stop" than i am able to run "sudo xl > create" without the FORCE option, but once i reboot the system, it > comes back and have to run the "sudo update-rc.d xend stop" all over > again. SO wondering how to disable xend from loading at boot time? Or > just get rid of whatever remnants floating around that is interfering > with things. You need to remove the initscript which is starting xend on boot. Try "update-rc.d xend disable". The reason for this check to prevent xl from running while xend is active is that using xl while xend is running can lead to subtle and confusing bugs. Ian. From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: [Xen-users] Why the need for "-f" with XL in Xen 4.2 rev-25467 Date: Thu, 21 Jun 2012 12:40:48 +0100 Message-ID: References: <4FE26C0E.9070104@gmail.com> <4FE28C67.30000@gmail.com> <1340256036.4998.6.camel@dagon.hellion.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1340256036.4998.6.camel@dagon.hellion.org.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On Thu, Jun 21, 2012 at 6:20 AM, Ian Campbell wrote: > The reason for this check to prevent xl from running while xend is > active is that using xl while xend is running can lead to subtle and > confusing bugs. Just to emphasize the point: about a month ago I spent 3 full days trying to track down what I thought was an ugly reference-counting error on domain destruction, but turned out just to be xend running in the background and messing with things behind xl's back. That's what prompted us to put in the check. :-) Perhaps the warning should explicitly mentioning disabling xend as the best solution? -George From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [Xen-users] Why the need for "-f" with XL in Xen 4.2 rev-25467 Date: Thu, 21 Jun 2012 12:43:44 +0100 Message-ID: <1340279024.21872.115.camel@zakaz.uk.xensource.com> References: <4FE26C0E.9070104@gmail.com> <4FE28C67.30000@gmail.com> <1340256036.4998.6.camel@dagon.hellion.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: George Dunlap Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On Thu, 2012-06-21 at 12:40 +0100, George Dunlap wrote: > On Thu, Jun 21, 2012 at 6:20 AM, Ian Campbell wrote: > > The reason for this check to prevent xl from running while xend is > > active is that using xl while xend is running can lead to subtle and > > confusing bugs. > > Just to emphasize the point: about a month ago I spent 3 full days > trying to track down what I thought was an ugly reference-counting > error on domain destruction, but turned out just to be xend running in > the background and messing with things behind xl's back. That's what > prompted us to put in the check. :-) > > Perhaps the warning should explicitly mentioning disabling xend as the > best solution? Yes, I think that would be a good idea. > > -George