Normally our policy is to avoid any major version rebases of libvirt in released Fedora products, and only cherry-pick patches. The exception to this policy is when we have security updates which are not practical to backport. This is such a time. Thus we are updating the libvirt in in Fedora 12 from 0.7.1 to 0.8.2 and Fedora 13 from 0.7.7 to 0.8.2, both matching rawhide. In general we expect the quality of 0.8.2 to be fairly high, since 0.8.2 was primarily accumulated bug fixes resulting from RHEL6 testing of the 0.8.1 release.
None the less, if you are able to, please take time to test these two updates and report any regressions[1]:
https://admin.fedoraproject.org/updates/libvirt-0.8.2-1.fc12 https://admin.fedoraproject.org/updates/libvirt-0.8.2-1.fc13
Regards, Daniel
[1] There is an expected regression with certain uses of qcow2 disks as per the update notes.
On 07/12/2010 12:43 PM, Daniel P. Berrange wrote:
https://admin.fedoraproject.org/updates/libvirt-0.8.2-1.fc12 https://admin.fedoraproject.org/updates/libvirt-0.8.2-1.fc13
I pushed the java bindings for this as well.
-- bk
Attempt to build rpms via src.rpm at Xen 4.0.1-rc3 (2.6.32.16) Dom0 on top of F13 :-
PASS: xmconfigtest TEST: xencapstest !!!!!!!!!! 10 FAIL FAIL: xencapstest TEST: qemuxml2argvtest ........................................ 40 ........................................ 80 ......... 89 OK PASS: qemuxml2argvtest TEST: qemuxml2xmltest ........................................ 40 ........... 51 OK PASS: qemuxml2xmltest TEST: qemuargv2xmltest ........................................ 40 ................ 56 OK PASS: qemuargv2xmltest TEST: qemuhelptest ........ 8 OK PASS: qemuhelptest TEST: nwfilterxml2xmltest .............................. 30 OK PASS: nwfilterxml2xmltest TEST: esxutilstest .... 4 OK PASS: esxutilstest TEST: vmx2xmltest ....................................... 39 OK PASS: vmx2xmltest TEST: xml2vmxtest .................................. 34 OK PASS: xml2vmxtest PASS: seclabeltest TEST: eventtest ........... 11 OK PASS: eventtest TEST: networkxml2xmltest ..... 5 OK PASS: networkxml2xmltest TEST: storagevolxml2xmltest ...... 6 OK PASS: storagevolxml2xmltest TEST: storagepoolxml2xmltest ........... 11 OK PASS: storagepoolxml2xmltest TEST: nodedevxml2xmltest ............. 13 OK PASS: nodedevxml2xmltest TEST: interfacexml2xmltest ................... 19 OK PASS: interfacexml2xmltest ==================== 1 of 47 tests failed ==================== make[2]: *** [check-TESTS] Error 1 make[2]: Leaving directory `/root/rpmbuild/BUILD/libvirt-0.8.2/tests' make[1]: *** [check-am] Error 2 make[1]: Leaving directory `/root/rpmbuild/BUILD/libvirt-0.8.2/tests' make: *** [check-recursive] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.Dm4k8y (%check)
Boris.
--- On Mon, 7/12/10, Daniel P. Berrange berrange@redhat.com wrote:
From: Daniel P. Berrange berrange@redhat.com Subject: [fedora-virt] FYI: Major version rebase of libvirt in F12, F13 in updates-testing To: virt@lists.fedoraproject.org Date: Monday, July 12, 2010, 12:43 PM
Normally our policy is to avoid any major version rebases of libvirt in released Fedora products, and only cherry-pick patches. The exception to this policy is when we have security updates which are not practical to backport. This is such a time. Thus we are updating the libvirt in in Fedora 12 from 0.7.1 to 0.8.2 and Fedora 13 from 0.7.7 to 0.8.2, both matching rawhide. In general we expect the quality of 0.8.2 to be fairly high, since 0.8.2 was primarily accumulated bug fixes resulting from RHEL6 testing of the 0.8.1 release.
None the less, if you are able to, please take time to test these two updates and report any regressions[1]:
https://admin.fedoraproject.org/updates/libvirt-0.8.2-1.fc12 https://admin.fedoraproject.org/updates/libvirt-0.8.2-1.fc13
Regards, Daniel
[1] There is an expected regression with certain uses of qcow2 disks as per the update notes.
On Tue, Jul 13, 2010 at 05:45:18AM -0700, Boris Derzhavets wrote:
Attempt to build rpms via src.rpm at Xen 4.0.1-rc3 (2.6.32.16) Dom0 on top of F13 :-
PASS: xmconfigtest TEST: xencapstest !!!!!!!!!! 10 FAIL FAIL: xencapstest
Edit the libvirt.spec file and change
make check
to
VIR_TEST_DEBUG=1 make check
then it should show what failed.
Xen isn't a supported platform in Fedora anymore though, so we can't hold up the updates for this.
Regards, Daniel
On Tue, Jul 13, 2010 at 01:52:25PM +0100, Daniel P. Berrange wrote:
On Tue, Jul 13, 2010 at 05:45:18AM -0700, Boris Derzhavets wrote:
Attempt to build rpms via src.rpm at Xen 4.0.1-rc3 (2.6.32.16) Dom0 on top of F13 :-
PASS: xmconfigtest TEST: xencapstest !!!!!!!!!! 10 FAIL FAIL: xencapstest
Edit the libvirt.spec file and change
make check
to
VIR_TEST_DEBUG=1 make check
then it should show what failed.
I've now seen this failure aswell:
TEST: xencapstest 1) Capabilities for i686, no PAE, no HVM ... FAILED 2) Capabilities for i686, PAE, no HVM ... FAILED 3) Capabilities for i686, PAE, HVM ... FAILED 4) Capabilities for x86_64, no HVM ... FAILED 5) Capabilities for x86_64, HVM ... FAILED 6) Capabilities for ia64, no HVM, LE ... FAILED 7) Capabilities for ia64, HVM, LE ... FAILED 8) Capabilities for ia64, no HVM, BE ... FAILED 9) Capabilities for ia64, HVM, BE ... FAILED 10) Capabilities for ppc64 ... FAILED FAIL: xencapstest
So it sounds like there's something simple wrong that makes all of the tests to fail..
Any tips where to look at?
-- Pasi
On Mon, Sep 06, 2010 at 12:42:15PM +0300, Pasi Kärkkäinen wrote:
On Tue, Jul 13, 2010 at 01:52:25PM +0100, Daniel P. Berrange wrote:
On Tue, Jul 13, 2010 at 05:45:18AM -0700, Boris Derzhavets wrote:
Attempt to build rpms via src.rpm at Xen 4.0.1-rc3 (2.6.32.16) Dom0 on top of F13 :-
PASS: xmconfigtest TEST: xencapstest !!!!!!!!!! 10 FAIL FAIL: xencapstest
Edit the libvirt.spec file and change
make check
to
VIR_TEST_DEBUG=1 make check
then it should show what failed.
I've now seen this failure aswell:
TEST: xencapstest
- Capabilities for i686, no PAE, no HVM ... FAILED
- Capabilities for i686, PAE, no HVM ... FAILED
- Capabilities for i686, PAE, HVM ... FAILED
- Capabilities for x86_64, no HVM ... FAILED
- Capabilities for x86_64, HVM ... FAILED
- Capabilities for ia64, no HVM, LE ... FAILED
- Capabilities for ia64, HVM, LE ... FAILED
- Capabilities for ia64, no HVM, BE ... FAILED
- Capabilities for ia64, HVM, BE ... FAILED
- Capabilities for ppc64 ... FAILED
FAIL: xencapstest
So it sounds like there's something simple wrong that makes all of the tests to fail..
Try adding this patch to get more error diagnositics:
diff --git a/tests/testutils.c b/tests/testutils.c index 2f61aad..6c1933d 100644 --- a/tests/testutils.c +++ b/tests/testutils.c @@ -122,8 +122,12 @@ virtTestRun(const char *title, int nloops, int (*body)(const void *data), const
if (ts) GETTIMEOFDAY(&before); + virResetLastError(); if ((ret = body(data)) != 0) break; + virErrorPtr err = virGetLastError(); + if (err) + virDispatchError(NULL); if (ts) { GETTIMEOFDAY(&after); ts[i] = DIFF_MSEC(&after, &before);
Daniel
On Mon, Sep 06, 2010 at 11:28:31AM +0100, Daniel P. Berrange wrote:
On Mon, Sep 06, 2010 at 12:42:15PM +0300, Pasi Kärkkäinen wrote:
On Tue, Jul 13, 2010 at 01:52:25PM +0100, Daniel P. Berrange wrote:
On Tue, Jul 13, 2010 at 05:45:18AM -0700, Boris Derzhavets wrote:
Attempt to build rpms via src.rpm at Xen 4.0.1-rc3 (2.6.32.16) Dom0 on top of F13 :-
PASS: xmconfigtest TEST: xencapstest !!!!!!!!!! 10 FAIL FAIL: xencapstest
Edit the libvirt.spec file and change
make check
to
VIR_TEST_DEBUG=1 make check
then it should show what failed.
I've now seen this failure aswell:
TEST: xencapstest
- Capabilities for i686, no PAE, no HVM ... FAILED
- Capabilities for i686, PAE, no HVM ... FAILED
- Capabilities for i686, PAE, HVM ... FAILED
- Capabilities for x86_64, no HVM ... FAILED
- Capabilities for x86_64, HVM ... FAILED
- Capabilities for ia64, no HVM, LE ... FAILED
- Capabilities for ia64, HVM, LE ... FAILED
- Capabilities for ia64, no HVM, BE ... FAILED
- Capabilities for ia64, HVM, BE ... FAILED
- Capabilities for ppc64 ... FAILED
FAIL: xencapstest
So it sounds like there's something simple wrong that makes all of the tests to fail..
Try adding this patch to get more error diagnositics:
Thanks! I'll try it later today.
-- Pasi
diff --git a/tests/testutils.c b/tests/testutils.c index 2f61aad..6c1933d 100644 --- a/tests/testutils.c +++ b/tests/testutils.c @@ -122,8 +122,12 @@ virtTestRun(const char *title, int nloops, int (*body)(const void *data), const
if (ts) GETTIMEOFDAY(&before);
virResetLastError(); if ((ret = body(data)) != 0) break;virErrorPtr err = virGetLastError();if (err)virDispatchError(NULL); if (ts) { GETTIMEOFDAY(&after); ts[i] = DIFF_MSEC(&after, &before);Daniel
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
On Mon, Jul 12, 2010 at 05:43:34PM +0100, Daniel P. Berrange wrote:
Normally our policy is to avoid any major version rebases of libvirt in released Fedora products, and only cherry-pick patches. The exception to this policy is when we have security updates which are not practical to backport. This is such a time. Thus we are updating the libvirt in in Fedora 12 from 0.7.1 to 0.8.2 and Fedora 13 from 0.7.7 to 0.8.2, both matching rawhide. In general we expect the quality of 0.8.2 to be fairly high, since 0.8.2 was primarily accumulated bug fixes resulting from RHEL6 testing of the 0.8.1 release.
None the less, if you are able to, please take time to test these two updates and report any regressions[1]:
https://admin.fedoraproject.org/updates/libvirt-0.8.2-1.fc12 https://admin.fedoraproject.org/updates/libvirt-0.8.2-1.fc13
FYI no negative feedback so far, so I intend to push these to stable next Monday...
Daniel
-
Boris Derzhavets -
Bryan Kearney -
Daniel P. Berrange -
Pasi Kärkkäinen