'make syntax-check' wants a newer gnulib for 2014 copyright.
Also, a couple of fixes for bootstrap issues reported on IRC:
- on some older glibc systems, ./configure could deadlock due to
a glibc malloc bug
- on FreeBSD systems, a broken autom4te coupled with gettext
0.18.3 prevents bootstrap; we
From: Richard W.M. Jones rjo...@redhat.com
I'm using gcc-4.8.2-7.fc21.aarch64 which does not appear to support
this option.
---
m4/virt-compile-warnings.m4 | 3 +++
1 file changed, 3 insertions(+)
diff --git a/m4/virt-compile-warnings.m4 b/m4/virt-compile-warnings.m4
index 1547e03..574fbc4
See http://honk.sigxcpu.org:8001/job/libvirt-syntax-check/1805/
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
On 01/01/2014 06:42 AM, Richard W.M. Jones wrote:
From: Richard W.M. Jones rjo...@redhat.com
I'm using gcc-4.8.2-7.fc21.aarch64 which does not appear to support
this option.
---
m4/virt-compile-warnings.m4 | 3 +++
1 file changed, 3 insertions(+)
diff --git
On Wed, Jan 01, 2014 at 06:52:09AM -0700, Eric Blake wrote:
On 01/01/2014 06:42 AM, Richard W.M. Jones wrote:
From: Richard W.M. Jones rjo...@redhat.com
I'm using gcc-4.8.2-7.fc21.aarch64 which does not appear to support
this option.
---
m4/virt-compile-warnings.m4 | 3 +++
1
Libvirt compiles fine on aarch64. You will need to configure with
--without-dtrace as systemtap tracepoints are pretty broken, giving
lots of strange compile-time errors/link failures in both libvirt and qemu.
The test suite fails, see attachment.
Note this is all running under qemu-arm64
On Wed, Jan 01, 2014 at 02:51:30PM +, Richard W.M. Jones wrote:
In particular, any aarch64 binary which the test suite runs is
actually run under the qemu-arm64 interpreter (using binfmt). I'm
guessing this explains the extra file descriptor in some tests.
More precisely, qemu opens a
On Wed, Jan 01, 2014 at 02:51:30PM +, Richard W.M. Jones wrote:
FAIL: sysinfotest
=
TEST: sysinfotest
1) aarch64 sysinfo ...
Offset 0
Expect [sysinfo type='smbios'
/sysinfo
]
Actual [sysinfo type='smbios'
From: Richard W.M. Jones rjo...@redhat.com
---
tests/sysinfotest.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/sysinfotest.c b/tests/sysinfotest.c
index 8357701..c8675f9 100644
--- a/tests/sysinfotest.c
+++ b/tests/sysinfotest.c
@@ -83,7 +83,7 @@ testSysinfo(const
From: Richard W.M. Jones rjo...@redhat.com
On AArch64 the kernel prints one processor (lower case 'p') line per
core. As this was missing from the test data, virSysinfo was not
parsing any processors at all.
Fix the test data so the test now passes.
---
tests/sysinfodata/aarch64cpuinfo.data
From: Richard W.M. Jones rjo...@redhat.com
---
tests/virnetsockettest.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/tests/virnetsockettest.c b/tests/virnetsockettest.c
index eda95bc..82c202e 100644
--- a/tests/virnetsockettest.c
+++ b/tests/virnetsockettest.c
@@ -60,8
On Wed, Jan 01, 2014 at 03:34:33PM +, Richard W.M. Jones wrote:
On Wed, Jan 01, 2014 at 02:51:30PM +, Richard W.M. Jones wrote:
FAIL: sysinfotest
=
In fact, since this test is entirely test-data-driven, why does the
test contain arch-specific sections at all?
Rich.
On 01/01/2014 08:49 AM, Richard W.M. Jones wrote:
From: Richard W.M. Jones rjo...@redhat.com
---
tests/virnetsockettest.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/tests/virnetsockettest.c b/tests/virnetsockettest.c
index eda95bc..82c202e 100644
---
On 01/01/2014 08:49 AM, Richard W.M. Jones wrote:
From: Richard W.M. Jones rjo...@redhat.com
---
tests/sysinfotest.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/sysinfotest.c b/tests/sysinfotest.c
index 8357701..c8675f9 100644
--- a/tests/sysinfotest.c
+++
On 01/01/2014 08:49 AM, Richard W.M. Jones wrote:
From: Richard W.M. Jones rjo...@redhat.com
On AArch64 the kernel prints one processor (lower case 'p') line per
core. As this was missing from the test data, virSysinfo was not
parsing any processors at all.
Fix the test data so the test
See http://honk.sigxcpu.org:8001/job/libvirt-syntax-check/1807/
--
Started by upstream project libvirt-build build number 2016
Building on master in workspace
http://honk.sigxcpu.org:8001/job/libvirt-syntax-check/ws/
[workspace] $ /bin/sh -xe
On 01/01/2014 09:24 AM, Eric Blake wrote:
On 01/01/2014 08:49 AM, Richard W.M. Jones wrote:
From: Richard W.M. Jones rjo...@redhat.com
---
tests/virnetsockettest.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/tests/virnetsockettest.c b/tests/virnetsockettest.c
Prior to this patch, every test:/// URI has its own event manager,
which means that registering for an event can only ever receive
events from the connection where it issued the API that triggered
the event. But the whole idea of events is to be able to learn
about something where an API call did
See http://honk.sigxcpu.org:8001/job/libvirt-syntax-check/1808/
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
Prior to this patch, every test:/// URI has its own event manager,
which means that registering for an event can only ever receive
events from the connection where it issued the API that triggered
the event. But the whole idea of events is to be able to learn
about something where an API call did
On 01/01/2014 09:54 AM, Eric Blake wrote:
Prior to this patch, every test:/// URI has its own event manager,
which means that registering for an event can only ever receive
events from the connection where it issued the API that triggered
the event. But the whole idea of events is to be able
Hi Umar,
please contact libvirt guys for python bindings. Python bindings for libvirt
are not handled by me, I handle just the PHP bindings and I'm not aware of the
function support in the Python bindings.
Happy New Year!
Thanks,
Michal
- Original Message -
From: Umar Draz
In my recent work on events, I'm running into something where I'm
stumped on timing behavior. I'm using
virEventRegisterDefaultImpl()/virEventRunDefaultImpl() as my event loop,
and trying to test that an event is firing correctly.
With the test:///default (or any other local URI), if I register
On 12/31/2013 08:21 AM, Eric Blake wrote:
Since libvirt 0.9.3, the entire virevent.c file has been a public
API, so improve the documentation in this file. Also, fix a
potential core dump - it could only be triggered by bogus use of
the API and would only affect the caller (not libvirtd), but
Dear All,
Happy new year to you.
I have a similar question which had been replied by Daniel in the following
post:
http://www.redhat.com/archives/libvir-list/2010-March/msg00296.html
I also want to assign a static IP to the container.
As Daniel said, I can successfully assign a static IP to
25 matches
Mail list logo
