Displaying 10 results from an estimated 10 matches for "libxlu_cfg_i".
Did you mean:
libxlu_cfg_y
2012 Sep 11
4
[PATCH] libxl: Tolerate xl config files missing trailing newline
I wrote:
> Also I wrote:
> > However, xl fails on config files which are missing the final
> > newline. This should be fixed for 4.2.
>
> My patch for this didn''t make it into 4.2 RC4.
Should this go into 4.2.0 or be held for 4.2.1 (or is it not 4.2.x
material at all) ?
Ian.
From: Ian Jackson <ian.jackson@eu.citrix.com>
Subject: [PATCH] libxl: Tolerate xl
2012 Aug 14
12
[TESTDAY] xl cpupool-create segfaults if given invalid configuration
# xl cpupool-create ''name="pool2" sched="credit2"''
command line:2: config parsing error near `sched'': syntax error,
unexpected IDENT, expecting NEWLINE or '';''
Failed to parse config file: Invalid argument
*** glibc detected *** xl: free(): invalid pointer: 0x0000000001a79a10 ***
Segmentation fault (core dumped)
Looking at the code
2013 Aug 20
1
xen 4.4 code bug
So i am getting this
cc1: warning: -Wformat-nonliteral ignored without -Wformat
[-Wformat-nonliteral]
libxlu_cfg_y.c: In function ''xlu__cfg_yyparse'':
libxlu_cfg_y.c:1292:41: error: ''scanner'' undeclared (first use in this
function)
yychar = yylex (&yylval, &yylloc, scanner);
^
libxlu_cfg_y.c:1292:41: note:
2010 Aug 03
1
[PATCH] libxl: free values in XLU_ConfigSetting
# HG changeset patch
# User Ian Campbell <ian.campbell@citrix.com>
# Date 1280829528 -3600
# Node ID b2ed7cc08554cba162f93cb95e84c2130d76b314
# Parent 8cd4de118ca4d0124011bff1611ddc2e04bd6566
libxl: free values in XLU_ConfigSetting.
Fixes these valgrind reported leaks, found with "valgrind xl create -n ..."
==21170== 8 bytes in 3 blocks are definitely lost in loss record 1 of 3
2012 May 30
10
[xen-unstable test] 12988: regressions - FAIL
flight 12988 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/12988/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-oldkern 4 xen-build fail REGR. vs. 12979
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-qemuu-win7-amd64 12
2012 Apr 12
6
fatal error if Flex and Bison is not configured
Hi all,
I try to build xen 4.2( revision number: 25161) on Ubuntu 11.10_amd64, Mac
pro. After running ./configure and make. I got the following fatal error:
*libxlu_cfg_y.y:22:26: fatal error: libxlu_cfg_l.h: No such file or
directory compilation terminated.*
So the original libxlu_cfg_l.h is deleted when making, and should be
regenerated but it is not. I find the path of flex and bison is not
2012 Dec 04
1
libxl: stable-4.2 git tree dirty after a build
It appears that something about the 4.2.1-rc1 tree is leaving around
generated files in a modified state after a build:
# Changes not staged for commit:
# (use "git add <file>..." to update what will be committed)
# (use "git checkout -- <file>..." to discard changes in working
directory)
#
# modified: tools/libxl/libxlu_cfg_y.c
# modified:
2012 Aug 24
0
[xen-unstable test] 13627: regressions - FAIL
flight 13627 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/13627/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-win-vcpus1 12 guest-localmigrate/x10 fail REGR. vs. 13625
test-amd64-amd64-win 5 xen-boot fail REGR. vs. 13625
test-i386-i386-xl-win 5 xen-boot
2010 Aug 18
16
[PATCH 00 of 16] libxl: autogenerate type definitions and destructor functions
The series introduces auto-generation of the type definitions used in
the libxl interface followed by auto-generation of a destructor
function for each type. In the future it may be possible to use the
related data structures for other purposes, for example auto-generation
of the functions to marshal between C and language binding data types.
tools/_libxl_types.h should be identical both before
2011 Jun 02
48
[PATCH 0/9] libxl: disk configuration handling
This is v3 of my disk series. What were previously patches 01-06 have
been applied. These are the tested and updated remainder, addressing
the previous comments.
1 Preparatory work.
2-4 The new parser and its documentation.
5-6 Replace old parsers with calls to the new one.
7-8 Two features, one of them essential.
9 Basic test suite for disk string parsing, as adhoc script.