[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[Libvir] [PATCH] Fix virDomainGetMaxVcpus in remote case

There's a typo in the remote_internal.c driver which causes it to call the wrong back-end function for virDomainGetMaxVcpus. The simple fix is attached.


Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom.  Registered in
England and Wales under Company Registration No. 03798903
Index: src/remote_internal.c
RCS file: /data/cvs/libvirt/src/remote_internal.c,v
retrieving revision 1.4
diff -u -p -r1.4 remote_internal.c
--- src/remote_internal.c	22 Jun 2007 13:16:10 -0000	1.4
+++ src/remote_internal.c	22 Jun 2007 16:20:11 -0000
@@ -1522,7 +1525,7 @@ remoteDomainGetMaxVcpus (virDomainPtr do
     make_nonnull_domain (&args.dom, domain);
     memset (&ret, 0, sizeof ret);
-    if (call (domain->conn, priv, 0, REMOTE_PROC_GET_MAX_VCPUS,
+    if (call (domain->conn, priv, 0, REMOTE_PROC_DOMAIN_GET_MAX_VCPUS,
               (xdrproc_t) xdr_remote_domain_get_max_vcpus_args, (char *) &args,
               (xdrproc_t) xdr_remote_domain_get_max_vcpus_ret, (char *) &ret) == -1)
         return -1;

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]