From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: xl vs. xm, possible bug in xl Date: Thu, 8 Sep 2011 13:07:55 -0400 Message-ID: <20110908170755.GB16730@dumpdata.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Sven =?iso-8859-1?Q?K=F6hler?= , david.vrabel@citrix.com Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Thu, Sep 08, 2011 at 06:42:12PM +0200, Sven K=F6hler wrote: > Hi, >=20 > 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. >=20 > 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 d= om0 is below the minimum threshold > > libxl: error: libxl.c:2145:libxl_set_memory_target new target 0 for d= om0 is below the minimum threshold > > libxl: error: libxl.c:2145:libxl_set_memory_target new target 0 for d= om0 is below the minimum threshold > > failed to free memory for the domain >=20 > Consider, that autobaloon=3D1 in xl.conf. > With the autobaloon=3D0 the errors change to >=20 > > # 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=3D-1: libxl__confirm_device_m= odel_startup >=20 >=20 > Note, that I use dom0_mem=3D512M in grub.conf. Also, xm top states, tha= t > 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. Hm, but the migrating memory away from dom0 seems bizzare. Lets ping David who has been in the thick of this. I have a feeling it is the "delta" patches .. >=20 > The second issue sounds more severe, and I'm pretty clueless. >=20 > Is this a bug in xl? > Starting the very same domain with xm works without a hassle. >=20 >=20 > 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). > xen 4.1.1 >=20 > domU config: > kernel =3D "/usr/src/linux-domU/_domU/vmlinux" > memory =3D 2048 > vcpus =3D 8 >=20 > root =3D "/dev/xvda1" > extra =3D "ro" >=20 > disk =3D [ > "phy:/dev/md2,xvda1,w", > "phy:/dev/md5,xvda2,w", > ] > vif =3D [ > "bridge=3Dxenbr0,mac=3D00:16:3E:00:00:01", > "bridge=3Dxenbr1,mac=3D00:16:3E:00:01:01", > ] >=20 >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel