[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Re: xl vs. xm, possible bug in xl
On Thu, 8 Sep 2011, Sven KÃhler wrote: > 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 That means that qemu failed to start. Could you please cat /var/log/xen/qemu-dm-domainname.log? _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |