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>
	<CABs9Ej=K7GGHHk43MJvekvffCVjQoVs5=+HursF2BmLRcU31ng@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============8495108855433470291=="
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <CABs9Ej=K7GGHHk43MJvekvffCVjQoVs5=+HursF2BmLRcU31ng@mail.gmail.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: "xen-devel@lists.xen.org" <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,<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.
>
> 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 <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
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    On 6/20/2012 10:07 PM, Rolu wrote:
    <blockquote
cite="mid:CABs9Ej=K7GGHHk43MJvekvffCVjQoVs5=+HursF2BmLRcU31ng@mail.gmail.com"
      type="cite">
      <pre wrap="">On Thu, Jun 21, 2012 at 2:34 AM,  <a class="moz-txt-link-rfc2396E" href="mailto:cyberhawk001@gmail.com">&lt;cyberhawk001@gmail.com&gt;</a> wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">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
&lt;domu_config_file&gt;", 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?

</pre>
      </blockquote>
      <pre wrap="">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 <a class="moz-txt-link-freetext" href="http://wiki.xen.org/wiki/Choice_of_Toolstacks">http://wiki.xen.org/wiki/Choice_of_Toolstacks</a> for more info.
</pre>
    </blockquote>
    <br>
    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.<br>
    <br>
    I was checking to make sure XEND was stopped by running "<b>sudo
      /etc/init.d/xend stop</b>" and i get an error message as below:<br>
    <br>
    <b>Traceback (most recent call last):<br>
      &nbsp; file "usr/sbin/xen", line 36, in &lt;module&gt;<br>
      &nbsp;&nbsp;&nbsp; from xen.xend.server import SrvDaemon<br>
      ImportError: No module named xen.xend.server</b> <br>
    <br>
    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.<br>
    <br>
    Once i run "<b>sudo update-rc.d xend stop</b>" than i am able to run
    "<b>sudo xl create</b>" without the FORCE option, but once i reboot
    the system, it comes back and have to run the "<b>sudo update-rc.d
      xend stop</b>" 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.<br>
    <br>
    <br>
    <br>
  </body>
</html>

--------------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==--