Below is the output of xm info and where I think we can mine the properties in the provider code.
Note *1: Xen_VirtualSystemManagementService.version string is 3.0.3. I can get 3.0 from xen_major and minor, but I cannot get the last .3. Any suggestions>
Note *2: Xen_VirtualSystemManagementCapabilities.VirtualSystemTypesSupported only displays the first type (xen-3.0-x86_64) through the test suite. I have set up the test to accept that, but it's not exactly correct.
xm info:
host : 1089 Xen_VirtualSystemManagementService.SystemName
release : 2.6.18-xen
version : #1 SMP Tue May 22 ...
machine : x86_64
nr_cpus : 4 ProcessorPool.Capacity
nr_nodes : 1
sockets_per_node : 2
cores_per_socket : 1
threads_per_core : 2
cpu_mhz : 2793
hw_caps : bfebfbff:2...
total_memory : 2047 MemoryPool.Capacity = total_memory x 1GB
free_memory : 125
xen_major : 3 Xen_VirtualSystemManagementService.version (*1)
xen_minor : 0 Xen_VirtualSystemManagementService.version (*1)
xen_extra : -unstable
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p Xen_VirtualSystemManagementCapabilities (*2).VirtualSystemTypesSupported
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : Thu May 17 11:42:46 2007 +0100 15080:089696e0c603
cc_compiler : gcc version 4.1.2 20070115 (prerelease) (SUSE Linux)
cc_compile_by : root
cc_compile_domain :
cc_compile_date : Tue May 22 11:46:25 EDT 2007
xend_config_format : 4
Am I missing anything? If no then I should have a patch ready to add soon.
Luke
_______________________________________________
Xen-cim mailing list
Xen-cim@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-cim
|