All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sven Köhler" <sven.koehler@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Re: xl vs. xm, possible bug in xl
Date: Fri, 09 Sep 2011 00:53:03 +0200	[thread overview]
Message-ID: <j4bgsc$ka$1@dough.gmane.org> (raw)
In-Reply-To: <20110908170755.GB16730@dumpdata.com>



Am 08.09.2011 19:07, schrieb Konrad Rzeszutek Wilk:
> On Thu, Sep 08, 2011 at 06:42:12PM +0200, Sven Köhler wrote:
>> Hi,
>>
>> xl is supposed to superseed xm, is this correct? How mature is xl,
>> actually? I'm asking, because the maintainers of the gentoo's xen
>> packages are migrating the init.d-scripts from xm to xl, but xl is
>> causing a lot of trouble.
>>
>> Well, xl basically fails to start domains on my system.
>>> # xl create /etc/xen/xen-sk1
>>> Parsing config file /etc/xen/xen-sk1
>>> libxl: error: libxl.c:2145:libxl_set_memory_target new target 0 for dom0 is below the minimum threshold
>>> libxl: error: libxl.c:2145:libxl_set_memory_target new target 0 for dom0 is below the minimum threshold
>>> libxl: error: libxl.c:2145:libxl_set_memory_target new target 0 for dom0 is below the minimum threshold
>>> failed to free memory for the domain
>>
>> Consider, that autobaloon=1 in xl.conf.
>> With the autobaloon=0 the errors change to
>>
>>> # xl create /etc/xen/xen-sk1
>>> Parsing config file /etc/xen/xen-sk1
>>> libxl: error: libxl_device.c:476:libxl__wait_for_device_model Device Model not ready
>>> xl: fatal error: libxl_create.c:535, rc=-1: libxl__confirm_device_model_startup
>>
>>
>> Note, that I use dom0_mem=512M in grub.conf. Also, xm top states, that
>> there are 2139432k free memory. Considering the first issue, it seems
>> like xl is trying to baloon memory away from dom0, which fails - which
>> seems obvious wrong considering that I use dom0_mem. CONFIG_XEN_BALLOON
>> is enabled for dom0
> 
> Yeah, there is a bug there (in Linux kernel) that just got integrated in 3.1-rc5.
> Will show up in 3.0.5.

A bug will show up in 3.0.5/3.1-rc5 or the fix for it?

Also, you seem to be replying to the first problem, the on about memory.

Any clue, that the second problem is about?
> # xl create /etc/xen/xen-sk1
> Parsing config file /etc/xen/xen-sk1
> libxl: error: libxl_device.c:476:libxl__wait_for_device_model Device Model not ready
> xl: fatal error: libxl_create.c:535, rc=-1: libxl__confirm_device_model_startup


>> dom0:
>> vanilla 3.0.0 with vga patch
> 
> You could upgrade to 3.0.4 and then you get the VGA patch for free
> (and some bug-fixes too).

Done. No improvement.

  parent reply	other threads:[~2011-09-08 22:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-08 16:42 xl vs. xm, possible bug in xl Sven Köhler
2011-09-08 17:07 ` Konrad Rzeszutek Wilk
2011-09-08 17:44   ` David Vrabel
2011-09-08 22:53   ` Sven Köhler [this message]
2011-09-09 11:27     ` Stefano Stabellini
2011-09-09 11:27       ` Sven Köhler
2011-09-09 12:05         ` Stefano Stabellini
2011-09-09 12:06           ` Stefano Stabellini
2011-09-09 12:43           ` Sven Köhler
2011-09-09 12:54             ` Stefano Stabellini
2011-09-09 14:16               ` Ian Campbell
2011-09-21 16:13                 ` Re: xl vs. xm, possible bug in xl (fwd) [and 1 more messages] Ian Jackson

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='j4bgsc$ka$1@dough.gmane.org' \
    --to=sven.koehler@gmail.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.