question of DestinationSystem meaning in MigrateVirtualSystemToSystem method
by Guo Lian Yun
Hi,
I'm a little confusing of MigrateVirtualSystemToSystem method，who can
tell me what does "DestinationSystem" refer to? It different from
DestinationHost which can be passed by a simple ip address. As a reference,
the DestinationSystem's Name have to be parsed below. Then what on earth
does it mean?
if (cu_get_str_path(dsys, "Name", &dname) != CMPI_RC_OK) {
cu_statusf(_BROKER, &s,
CMPI_RC_ERR_FAILED,
"Missing key (Name) in DestinationSystem");
METHOD_RETURN(results, 1);
return s;
}
Thanks!
Best,
Regards
Daisy Guo Lian Yun
E-mail: yunguol(a)cn.ibm.com
IBM China Development Lab, Shanghai, China
TEL: (86)-21-61008057
16 years, 11 months
[PATCH 0 of 2] [RFC] ComputerSystemModifiedIndication
by Jay Gagnon
This is still pretty rough around the edges but it seems functional enough that it's worth showing, and I've got a few spots where I could use some input. Right now it does in fact notice a domain that changes and fires an indication. The "previous instance" embedded object has it's Name and UUID fields filled in; I couldn't find any other fields that seemed terribly relevant to fill in.
The places where I could use some advice:
In _lifecycle_indication, the get_typed_instance args are mostly hardcoded. This seems rather bad, but I'm not quite sure where I should get them. It's not like I have a reference being passed in to pull that out of.
The entire sys_name_from_xml feels like an abomination, but sscanf falls short and full xml parsing seems way overkill. Any suggestions on how to make it safer/more sane are welcome.
In async_ind, I once again use some hardcoded values because I'm not sure where to get them.
In lifecycle_thread, I use lv_connect because I don't think I have the requisite info for the preferred method, but AFAIK lv_connect usage is frowned upon now. I also am not sure what to do here when I get errors. Should I terminate the event loop? Where would I even return an error message to the client?
16 years, 11 months
Xen_ElementCapabilities qurey error list
by Guo Lian Yun
Hi,
Beside the former error report of query Xen_HostSystem from
Xen_VirtualSystemManagementCapabilities according to
Xen_ElementCapabilities association,
that is to say, with a non exist VirtualSystemManagementCapabilities, we
can still get excepted result as following.
wbemcli ain -ac Xen_ElementCapabilities
http://root:password@localhost/root/virt:Xen_VirtualSystemManagementCapab..."
wrong"
localhost:5988/root/virt:Xen_HostSystem.CreationClassName="Xen_HostSystem",Name="wks230838wss.cn.ibm.com"
Meanwhile, other associations have the same problems.
With a non exist ComputerSystem instance, we can still get expected
association.
wbemcli ain -ac Xen_ElementCapabilities
http://root:password@localhost/root/virt:Xen_ComputerSystem.CreationClass..."Xen_ComputerSystem",Name="
wrong"
localhost:5988/root/virt:Xen_EnabledLogicalElementCapabilities.InstanceID="wrong"
However, there is no error report when I do invalid reverse query of
Xen_EnabledLogicalElementCapabilities.
wbemcli ain -ac Xen_ElementCapabilities
http://root:password@localhost/root/virt:Xen_EnabledLogicalElementCapabil..."
wrong"
As we know, Xen_AllocationCapabilities associate with ResourcePool by
Xen_ElementCapabilities. There are still errors from two sides querying.
wbemcli ain -ac Xen_ElementCapabilities
http://root:password@localhost/root/virt:Xen_AllocationCapabilities.Insta..."ProcessorPool/0"
*
* wbemcli: Cim: (7) CIM_ERR_NOT_SUPPORTED: The requested operation is not
supported
*
wbemcli ain -ac Xen_ElementCapabilities
http://root:password@localhost/root/virt:Xen_MemoryPool.InstanceID="wrong"
localhost:5988/root/virt:Xen_AllocationCapabilities.InstanceID="wrong"
Please who can have a look into them? Thanks!
Best,
Regards
Daisy Guo Lian Yun
E-mail: yunguol(a)cn.ibm.com
IBM China Development Lab, Shanghai, China
TEL: (86)-21-61008057
16 years, 11 months
[PATCH] Add DECLARE_INST_LIST() macro
by Dan Smith
# HG changeset patch
# User Dan Smith <danms(a)us.ibm.com>
# Date 1200494010 28800
# Node ID ef0dd32ef7faf101f97acfa0f0268bf18c22dcac
# Parent 2948ecbed2674aee61a994b06468c2ce9c763bb3
Add DECLARE_INST_LIST() macro
to allow declarations of pre-initialized inst_list structures
Signed-off-by: Dan Smith <danms(a)us.ibm.com>
diff -r 2948ecbed267 -r ef0dd32ef7fa libcmpiutil.h
--- a/libcmpiutil.h Tue Jan 15 12:54:04 2008 +0100
+++ b/libcmpiutil.h Wed Jan 16 06:33:30 2008 -0800
@@ -366,6 +366,13 @@ void inst_list_free(struct inst_list *li
* @returns nonzero on success, zero on failure
*/
int inst_list_add(struct inst_list *list, CMPIInstance *inst);
+
+/**
+ * Define a pre-initialized inst_list
+ *
+ * @param x The variable name for the list.
+ */
+#define DECLARE_INST_LIST(x) struct inst_list x = {NULL, 0, 0};
/**
* Compare key values in a reference to properties in an instance,
16 years, 11 months
[PATCH] Fix include of internal headers
by Dan Smith
# HG changeset patch
# User Dan Smith <danms(a)us.ibm.com>
# Date 1200498221 28800
# Node ID fd28a485f90399d166eb62816c32e2d7727cced6
# Parent ef0dd32ef7faf101f97acfa0f0268bf18c22dcac
Fix include of internal headers
This was causing me problems when installing libcmpiutil into /usr/local
for testing. I think this is the right solution, and seems to work for me
in both cases.
Signed-off-by: Dan Smith <danms(a)us.ibm.com>
diff -r ef0dd32ef7fa -r fd28a485f903 std_indication.h
--- a/std_indication.h Wed Jan 16 06:33:30 2008 -0800
+++ b/std_indication.h Wed Jan 16 07:43:41 2008 -0800
@@ -25,8 +25,8 @@
#include <cmpift.h>
#include <cmpimacs.h>
-#include <libcmpiutil.h>
-#include <std_invokemethod.h>
+#include "libcmpiutil.h"
+#include "std_invokemethod.h"
CMPIStatus stdi_trigger_indication(const CMPIBroker *broker,
const CMPIContext *context,
16 years, 11 months
[PATCH 0 of 5] VSMS support for KVM/XenFV
by Dan Smith
This set adds the necessary bits to be able to minimally define KVM and
XenFV domains. It allows me to create valid KVM guests.
It sidesteps a couple of the issues we'll need to tackle at some point,
like how to convey the appropriate virtual network for a KVM interface, etc.
Comments welcome.
16 years, 11 months
[PATCH] [RFC] Update VSSD schemas for FullVirt
by Dan Smith
# HG changeset patch
# User Dan Smith <danms(a)us.ibm.com>
# Date 1200499991 28800
# Node ID 61dcb1a6e2097e8125db046d6aa53bda4bc18a20
# Parent 05fa2ceba145e9e93066bd66c74299680bd7d21d
[RFC] Update VSSD schemas for FullVirt
This adds a flag to the Xen VSSD to enable full-virt or not, as well as the
required boot device information. In the implementation, a "false" or
missing value for the flag will indicate paravirt-ness.
For KVM, I added the boot device as well, since that's something it will
always need. For both, a missing boot device will imply "hd".
Comments? Additions?
Signed-off-by: Dan Smith <danms(a)us.ibm.com>
diff -r 05fa2ceba145 -r 61dcb1a6e209 schema/VSSD.mof
--- a/schema/VSSD.mof Tue Jan 15 16:24:39 2008 -0800
+++ b/schema/VSSD.mof Wed Jan 16 08:13:11 2008 -0800
@@ -8,8 +8,17 @@ class Xen_VirtualSystemSettingData : CIM
class Xen_VirtualSystemSettingData : CIM_VirtualSystemSettingData
{
+ [Description ("Flag to determine whether this guest is fully-virtualized")]
+ boolean isFullVirt;
+
+ [Description ("The bootloader and arguments to use when in "
+ "para-virtualized mode")]
string Bootloader;
string BootloaderArgs;
+
+ [Description ("The device to boot from when in fully-virtualized mode."
+ "One of hd,fd,cdrom.")]
+ string BootDevice;
};
@@ -20,4 +29,8 @@ class Xen_VirtualSystemSettingData : CIM
]
class KVM_VirtualSystemSettingData : CIM_VirtualSystemSettingData
{
+
+ [Description ("The device to boot from. One of hd,fd,cdrom.")]
+ string BootDevice;
+
};
16 years, 11 months