Displaying 2 results from an estimated 2 matches for "xpathexpr".
Did you mean:
pathexpr
2017 Mar 23
2
[PATCH] p2v: Use lscpu instead of libvirt to get CPU information.
...ar **lscpu, struct cpu_config *cpu)
{
- virConnectPtr conn;
- CLEANUP_FREE char *capabilities_xml = NULL;
- CLEANUP_XMLFREEDOC xmlDocPtr doc = NULL;
- CLEANUP_XMLXPATHFREECONTEXT xmlXPathContextPtr xpathCtx = NULL;
- CLEANUP_XMLXPATHFREEOBJECT xmlXPathObjectPtr xpathObj = NULL;
- const char *xpathexpr;
- xmlNodeSetPtr nodes;
- size_t nr_nodes, i;
- xmlNodePtr node;
-
- /* Connect to libvirt and get the capabilities XML. */
- conn = virConnectOpenReadOnly (NULL);
- if (!conn) {
- libvirt_error (_("could not connect to libvirt"));
- return;
- }
+ const char *flags;
- /*...
2017 Mar 17
7
[PATCH v2 0/6] v2v: Pass CPU vendor, model and topology from source to target.
v1 -> v2:
- Support for passing topology through -o glance.
- Support for passing topology through -o rhv.
- Use bool for acpi/apic/pae struct fields in virt-p2v.
- Write the xpath expression in error messages instead of file/line.
- Fix more memory leaks in virt-p2v cpuid.c.
- Passes make check & check-valgrind.
There may be some other minor changes. I believe that everything