All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael David Crawford <mdc@prgmr.com>
To: xen-devel@lists.xensource.com
Subject: xm create can't find /proc/xen/balloon
Date: Mon, 11 May 2009 05:47:54 -0700	[thread overview]
Message-ID: <4A081E7A.50203@prgmr.com> (raw)

I have the latest git sources of xen, ioemu and linux.  I just now did a 
"git pull" in each just to be sure.

When I do an "xm create" I get:

    Error: [Errno 2] No such file or directory: '/proc/xen/balloon'

Searching the list archives told me that this is most commonly caused by 
not having enough memory available for the DomU, but I have fixed that.

I'm pretty sure the problem is that the paravirt_ops Linux kernel puts 
its balloon in sysfs and not procfs.  So I applied Jeremy's patch found 
here:

   http://lists.xensource.com/archives/html/xen-devel/2008-11/msg00358.html

... then rebuilt and rebooted.  But I still get the message.

However, that patch changes a file in xend's sources.

Does xm need a similar patch - or should xm be looking at that same 
python module in xend's directory?  I don't know the codebase well 
enough to figure it out yet, though I'll be investigating while I await 
your responses.

Thanks for your help,

Mike
-- 
Michael David Crawford
mdc@prgmr.com

    prgmr.com - We Don't Assume You Are Stupid.

       Xen-Powered Virtual Private Servers: http://prgmr.com/xen

             reply	other threads:[~2009-05-11 12:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-11 12:47 Michael David Crawford [this message]
2009-05-11 13:00 ` xm create can't find /proc/xen/balloon Dulloor
2009-05-11 13:45   ` Michael David Crawford
2009-05-12 21:44 ` Jeremy Fitzhardinge

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=4A081E7A.50203@prgmr.com \
    --to=mdc@prgmr.com \
    --cc=xen-devel@lists.xensource.com \
    /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.