All of lore.kernel.org
 help / color / mirror / Atom feed
From: cyberhawk001@gmail.com
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
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	[thread overview]
Message-ID: <4FE26C0E.9070104@gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 864 bytes --]

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

[-- Attachment #1.2: Type: text/html, Size: 1157 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

             reply	other threads:[~2012-06-21  0:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21  0:34 cyberhawk001 [this message]
2012-06-21  2:07 ` [Xen-users] Why the need for "-f" with XL in Xen 4.2 rev-25467 Rolu
2012-06-21  2:52   ` cyberhawk001
2012-06-21  5:20     ` Ian Campbell
2012-06-21 11:40       ` George Dunlap
2012-06-21 11:43         ` Ian Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FE26C0E.9070104@gmail.com \
    --to=cyberhawk001@gmail.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.