[libvirt] RH EL5 test failure on interfaceshematest and xencapstest
I'm trying to build a new RPM for libvirt-0.8.5. Two tests are failing: interfaceschematest xencapstest Are these known errors? Any work-arounds? Thanks, Andy ./interfaceschematest 1) interfaceschemadata/bridge.xml ... FAILED xmllint --relaxng /usr/src/redhat/BUILD/libvirt-0.8.5/tests/../docs/schemas/interface.rng --noout /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge.xml /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge.xml:8: element interface: Relax-NG validity error : Element interface failed to validate attributes /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge.xml:9: element mac: Relax-NG validity error : Did not expect element mac there /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge.xml:11: element interface: Relax-NG validity error : Element interface failed to validate attributes /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge.xml:11: element interface: Relax-NG validity error : Expecting an element , got nothing /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge.xml:3: element mtu: Relax-NG validity error : Expecting element bridge, got mtu /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge.xml fails to validate 2) interfaceschemadata/vlan.xml ... OK 3) interfaceschemadata/ipv6-dhcp.xml ... OK 4) interfaceschemadata/bond-arp.xml ... OK 5) interfaceschemadata/ipv6-autoconf-dhcp.xml ... OK 6) interfaceschemadata/ethernet-static.xml ... OK 7) interfaceschemadata/ipv6-autoconf.xml ... OK 8) interfaceschemadata/bridge-vlan.xml ... FAILED xmllint --relaxng /usr/src/redhat/BUILD/libvirt-0.8.5/tests/../docs/schemas/interface.rng --noout /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-vlan.xml /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-vlan.xml:7: element interface: Relax-NG validity error : Element interface failed to validate attributes /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-vlan.xml:8: element vlan: Relax-NG validity error : Did not expect element vlan there /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-vlan.xml:1: element interface: Relax-NG validity error : Element interface failed to validate content /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-vlan.xml:3: element protocol: Relax-NG validity error : Expecting element bond, got protocol /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-vlan.xml:3: element protocol: Relax-NG validity error : Expecting element vlan, got protocol /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-vlan.xml fails to validate 9) interfaceschemadata/bridge-no-address.xml ... FAILED xmllint --relaxng /usr/src/redhat/BUILD/libvirt-0.8.5/tests/../docs/schemas/interface.rng --noout /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-no-address.xml /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-no-address.xml:5: element interface: Relax-NG validity error : Element interface failed to validate attributes /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-no-address.xml:6: element mac: Relax-NG validity error : Did not expect element mac there /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-no-address.xml:8: element interface: Relax-NG validity error : Element interface failed to validate attributes /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-no-address.xml:8: element interface: Relax-NG validity error : Expecting an element , got nothing /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-no-address.xml:1: element interface: Relax-NG validity error : Element interface failed to validate content /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-no-address.xml fails to validate 10) interfaceschemadata/ethernet-static-no-prefix.xml ... OK 11) interfaceschemadata/bridge42.xml ... FAILED xmllint --relaxng /usr/src/redhat/BUILD/libvirt-0.8.5/tests/../docs/schemas/interface.rng --noout /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge42.xml /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge42.xml:5: element interface: Relax-NG validity error : Element interface failed to validate attributes /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge42.xml:5: element interface: Relax-NG validity error : Expecting an element , got nothing /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge42.xml:1: element interface: Relax-NG validity error : Element interface failed to validate content /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge42.xml:1: element interface: Relax-NG validity error : Element interface failed to validate attributes /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge42.xml fails to validate 12) interfaceschemadata/bridge-empty.xml ... OK 13) interfaceschemadata/ipv6-local.xml ... OK 14) interfaceschemadata/ipv6-static-multi.xml ... OK 15) interfaceschemadata/ethernet-dhcp.xml ... OK 16) interfaceschemadata/bridge-bond.xml ... FAILED xmllint --relaxng /usr/src/redhat/BUILD/libvirt-0.8.5/tests/../docs/schemas/interface.rng --noout /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-bond.xml /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-bond.xml:1: element interface: Relax-NG validity error : Element interface failed to validate content /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-bond.xml:1: element interface: Relax-NG validity error : Element interface failed to validate attributes /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-bond.xml fails to validate 17) interfaceschemadata/bond.xml ... OK 18) interfaceschemadata/ipv6-static.xml ... OK ./xencapstest 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
Sorry to reply to my own post. I found more info regarding xencapstest. It seems that this is failing because the virConnectPtr is NULL in xencapstest.c, line 50: if (!(caps = xenHypervisorMakeCapabilitiesInternal(NULL, hostmachine, fp1, fp2))) This in turn calls src/xen/xend_internal.c xenDaemonNodeGetTopology() with the NULL virConnectPtr. I guess the test needs a mock virConnect. Regards, Andy On 11/06/2010 02:30 PM, Andy Howell wrote:
I'm trying to build a new RPM for libvirt-0.8.5. Two tests are failing:
interfaceschematest xencapstest
Are these known errors? Any work-arounds?
Thanks,
Andy
./interfaceschematest 1) interfaceschemadata/bridge.xml ... FAILED xmllint --relaxng /usr/src/redhat/BUILD/libvirt-0.8.5/tests/../docs/schemas/interface.rng --noout /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge.xml /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge.xml:8: element interface: Relax-NG validity error : Element interface failed to validate attributes /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge.xml:9: element mac: Relax-NG validity error : Did not expect element mac there /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge.xml:11: element interface: Relax-NG validity error : Element interface failed to validate attributes /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge.xml:11: element interface: Relax-NG validity error : Expecting an element , got nothing /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge.xml:3: element mtu: Relax-NG validity error : Expecting element bridge, got mtu /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge.xml fails to validate 2) interfaceschemadata/vlan.xml ... OK 3) interfaceschemadata/ipv6-dhcp.xml ... OK 4) interfaceschemadata/bond-arp.xml ... OK 5) interfaceschemadata/ipv6-autoconf-dhcp.xml ... OK 6) interfaceschemadata/ethernet-static.xml ... OK 7) interfaceschemadata/ipv6-autoconf.xml ... OK 8) interfaceschemadata/bridge-vlan.xml ... FAILED xmllint --relaxng /usr/src/redhat/BUILD/libvirt-0.8.5/tests/../docs/schemas/interface.rng --noout /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-vlan.xml /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-vlan.xml:7: element interface: Relax-NG validity error : Element interface failed to validate attributes /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-vlan.xml:8: element vlan: Relax-NG validity error : Did not expect element vlan there /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-vlan.xml:1: element interface: Relax-NG validity error : Element interface failed to validate content /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-vlan.xml:3: element protocol: Relax-NG validity error : Expecting element bond, got protocol /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-vlan.xml:3: element protocol: Relax-NG validity error : Expecting element vlan, got protocol /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-vlan.xml fails to validate 9) interfaceschemadata/bridge-no-address.xml ... FAILED xmllint --relaxng /usr/src/redhat/BUILD/libvirt-0.8.5/tests/../docs/schemas/interface.rng --noout /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-no-address.xml /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-no-address.xml:5: element interface: Relax-NG validity error : Element interface failed to validate attributes /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-no-address.xml:6: element mac: Relax-NG validity error : Did not expect element mac there /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-no-address.xml:8: element interface: Relax-NG validity error : Element interface failed to validate attributes /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-no-address.xml:8: element interface: Relax-NG validity error : Expecting an element , got nothing /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-no-address.xml:1: element interface: Relax-NG validity error : Element interface failed to validate content /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-no-address.xml fails to validate 10) interfaceschemadata/ethernet-static-no-prefix.xml ... OK 11) interfaceschemadata/bridge42.xml ... FAILED xmllint --relaxng /usr/src/redhat/BUILD/libvirt-0.8.5/tests/../docs/schemas/interface.rng --noout /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge42.xml /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge42.xml:5: element interface: Relax-NG validity error : Element interface failed to validate attributes /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge42.xml:5: element interface: Relax-NG validity error : Expecting an element , got nothing /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge42.xml:1: element interface: Relax-NG validity error : Element interface failed to validate content /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge42.xml:1: element interface: Relax-NG validity error : Element interface failed to validate attributes /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge42.xml fails to validate 12) interfaceschemadata/bridge-empty.xml ... OK 13) interfaceschemadata/ipv6-local.xml ... OK 14) interfaceschemadata/ipv6-static-multi.xml ... OK 15) interfaceschemadata/ethernet-dhcp.xml ... OK 16) interfaceschemadata/bridge-bond.xml ... FAILED xmllint --relaxng /usr/src/redhat/BUILD/libvirt-0.8.5/tests/../docs/schemas/interface.rng --noout /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-bond.xml /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-bond.xml:1: element interface: Relax-NG validity error : Element interface failed to validate content /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-bond.xml:1: element interface: Relax-NG validity error : Element interface failed to validate attributes /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge-bond.xml fails to validate 17) interfaceschemadata/bond.xml ... OK 18) interfaceschemadata/ipv6-static.xml ... OK
./xencapstest 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
-- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
On 11/06/2010 01:30 PM, Andy Howell wrote:
I'm trying to build a new RPM for libvirt-0.8.5. Two tests are failing:
interfaceschematest xencapstest
Are these known errors? Any work-arounds?
There were several reports of failures fixed by patches right after the 0.8.5 release, although I'm not sure if applying them will solve all the problems you are facing. For example, https://www.redhat.com/archives/libvir-list/2010-November/msg00085.html lists several commits needed for successful testing across multiple xen header versions. -- Eric Blake eblake@redhat.com +1-801-349-2682 Libvirt virtualization library http://libvirt.org
2010/11/8 Eric Blake <eblake@redhat.com>:
On 11/06/2010 01:30 PM, Andy Howell wrote:
I'm trying to build a new RPM for libvirt-0.8.5. Two tests are failing:
interfaceschematest xencapstest
Are these known errors? Any work-arounds?
There were several reports of failures fixed by patches right after the 0.8.5 release, although I'm not sure if applying them will solve all the problems you are facing.
For example, https://www.redhat.com/archives/libvir-list/2010-November/msg00085.html lists several commits needed for successful testing across multiple xen header versions.
No, the problem is different and not specific to libvirt 0.8.5 xenHypervisorInit is called from xenRegister and detects the sys_interface_version. As Andy figured out correctly, the xencapstest calls xenHypervisorMakeCapabilitiesInternal with conn == NULL. xenHypervisorMakeCapabilitiesInternal then calls xenDaemonNodeGetTopology with conn == NULL if sys_interface_version >= SYS_IFACE_MIN_VERS_NUMA holds. This is true when you have Xen installed, otherwise sys_interface_version is -1. Therefore this test will fail when ypu have recent Xen installed. I just remember this, because Jim mentioned it quite a while ago on IRC and I looked up the details in my logs. At that time I suggested to apply this patch/hack to avoid the problem, as xenDaemonNodeGetTopology want to talk to a real xend at that point and insists in conn != NULL for that. diff --git a/src/xen/xen_hypervisor.c b/src/xen/xen_hypervisor.c index c5cc880..95b3ca2 100644 --- a/src/xen/xen_hypervisor.c +++ b/src/xen/xen_hypervisor.c @@ -2244,8 +2244,7 @@ xenHypervisorBuildCapabilities(virConnectPtr conn, "xenmigr") < 0) goto no_memory; - - if (sys_interface_version >= SYS_IFACE_MIN_VERS_NUMA) { + if (sys_interface_version >= SYS_IFACE_MIN_VERS_NUMA && conn != NULL) { if (xenDaemonNodeGetTopology(conn, caps) != 0) { virCapabilitiesFree(caps); return NULL; I'm not sure why the interfaceschematest fails, as It works for me. Matthias
On 11/08/2010 02:31 PM, Matthias Bolte wrote:
xenHypervisorInit is called from xenRegister and detects the sys_interface_version. As Andy figured out correctly, the xencapstest calls xenHypervisorMakeCapabilitiesInternal with conn == NULL. xenHypervisorMakeCapabilitiesInternal then calls xenDaemonNodeGetTopology with conn == NULL if sys_interface_version >= SYS_IFACE_MIN_VERS_NUMA holds. This is true when you have Xen installed, otherwise sys_interface_version is -1. Therefore this test will fail when ypu have recent Xen installed.
diff --git a/src/xen/xen_hypervisor.c b/src/xen/xen_hypervisor.c index c5cc880..95b3ca2 100644 --- a/src/xen/xen_hypervisor.c +++ b/src/xen/xen_hypervisor.c @@ -2244,8 +2244,7 @@ xenHypervisorBuildCapabilities(virConnectPtr conn, "xenmigr") < 0) goto no_memory;
- - if (sys_interface_version >= SYS_IFACE_MIN_VERS_NUMA) { + if (sys_interface_version >= SYS_IFACE_MIN_VERS_NUMA && conn != NULL) { if (xenDaemonNodeGetTopology(conn, caps) != 0) { virCapabilitiesFree(caps); return NULL;
ACK if you'd like to turn that into a formal commit. -- Eric Blake eblake@redhat.com +1-801-349-2682 Libvirt virtualization library http://libvirt.org
2010/11/8 Eric Blake <eblake@redhat.com>:
On 11/08/2010 02:31 PM, Matthias Bolte wrote:
xenHypervisorInit is called from xenRegister and detects the sys_interface_version. As Andy figured out correctly, the xencapstest calls xenHypervisorMakeCapabilitiesInternal with conn == NULL. xenHypervisorMakeCapabilitiesInternal then calls xenDaemonNodeGetTopology with conn == NULL if sys_interface_version >= SYS_IFACE_MIN_VERS_NUMA holds. This is true when you have Xen installed, otherwise sys_interface_version is -1. Therefore this test will fail when ypu have recent Xen installed.
diff --git a/src/xen/xen_hypervisor.c b/src/xen/xen_hypervisor.c index c5cc880..95b3ca2 100644 --- a/src/xen/xen_hypervisor.c +++ b/src/xen/xen_hypervisor.c @@ -2244,8 +2244,7 @@ xenHypervisorBuildCapabilities(virConnectPtr conn, "xenmigr") < 0) goto no_memory;
- - if (sys_interface_version >= SYS_IFACE_MIN_VERS_NUMA) { + if (sys_interface_version >= SYS_IFACE_MIN_VERS_NUMA && conn != NULL) { if (xenDaemonNodeGetTopology(conn, caps) != 0) { virCapabilitiesFree(caps); return NULL;
ACK if you'd like to turn that into a formal commit.
Okay, I basically used the explaining text as a commit message and pushed the result. Matthias
On 11/08/2010 03:31 PM, Matthias Bolte wrote:
2010/11/8 Eric Blake <eblake@redhat.com>:
On 11/06/2010 01:30 PM, Andy Howell wrote:
I'm trying to build a new RPM for libvirt-0.8.5. Two tests are failing:
interfaceschematest xencapstest
Are these known errors? Any work-arounds?
There were several reports of failures fixed by patches right after the 0.8.5 release, although I'm not sure if applying them will solve all the problems you are facing.
For example, https://www.redhat.com/archives/libvir-list/2010-November/msg00085.html lists several commits needed for successful testing across multiple xen header versions.
No, the problem is different and not specific to libvirt 0.8.5
xenHypervisorInit is called from xenRegister and detects the sys_interface_version. As Andy figured out correctly, the xencapstest calls xenHypervisorMakeCapabilitiesInternal with conn == NULL. xenHypervisorMakeCapabilitiesInternal then calls xenDaemonNodeGetTopology with conn == NULL if sys_interface_version >= SYS_IFACE_MIN_VERS_NUMA holds. This is true when you have Xen installed, otherwise sys_interface_version is -1. Therefore this test will fail when ypu have recent Xen installed.
I just remember this, because Jim mentioned it quite a while ago on IRC and I looked up the details in my logs. At that time I suggested to apply this patch/hack to avoid the problem, as xenDaemonNodeGetTopology want to talk to a real xend at that point and insists in conn != NULL for that.
diff --git a/src/xen/xen_hypervisor.c b/src/xen/xen_hypervisor.c index c5cc880..95b3ca2 100644 --- a/src/xen/xen_hypervisor.c +++ b/src/xen/xen_hypervisor.c @@ -2244,8 +2244,7 @@ xenHypervisorBuildCapabilities(virConnectPtr conn, "xenmigr") < 0) goto no_memory;
- - if (sys_interface_version >= SYS_IFACE_MIN_VERS_NUMA) { + if (sys_interface_version >= SYS_IFACE_MIN_VERS_NUMA && conn != NULL) { if (xenDaemonNodeGetTopology(conn, caps) != 0) { virCapabilitiesFree(caps); return NULL;
I'm not sure why the interfaceschematest fails, as It works for me.
Matthias, Attached is what I'm seeing for the interfaceshematest Regards, Andy
On 11/09/2010 08:13 AM, Andy Howell wrote:
Attached is what I'm seeing for the interfaceshematest
Regards,
Andy
interfaceschematest.failures
1) interfaceschemadata/bridge.xml ... FAILED xmllint --relaxng /usr/src/redhat/BUILD/libvirt-0.8.5/tests/../docs/schemas/interface.rng --noout /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge.xml /usr/src/redhat/BUILD/libvirt-0.8.5/tests/interfaceschemadata/bridge.xml:8: element interface: Relax-NG validity error : Element interface failed to validate attributes
I seem to recall seeing the same failure back when I was testing my vcpu patches for RHEL 5. It may be that RHEL 5 has an older version of xmllint that doesn't grok our Relax-NG schema correctly. I'll try and look into this more in-depth, and double check if I can actually reproduce the failure (it's a reboot or two away to get back to my RHEL 5 environment...). Or it may be that there was a RHEL-5-specific patch that changed something in a way that broke this test in relation to what the test expects upstream; but perhaps something in the existing RHEL 5 spec file is skipping the test in a different manner than your attempts to create an 0.8.5 spec file. -- Eric Blake eblake@redhat.com +1-801-349-2682 Libvirt virtualization library http://libvirt.org
participants (4)
-
Andy Howell -
Andy Howell -
Eric Blake -
Matthias Bolte