search for: vminfo

...wn as an anchored probe, and one that does not is known as unanchored." Here''s my question: By the above definition, "pid" and "fbt" or clearly anchored providers since their probes specify specific locations in a program. However, other providers, like "vminfo" or "proc", while they obviously fire at a specific location, are not really defined by that location, but rather by when a certain kind of event occurs. And then there''s "sysproc" which is probably closer to being more like "fbt", in the way the use...

Is there a trick to listing available providers? I can''t find it.

...tate = cidl_vm_state_not_defined; } return state; } virDomainInfo res_util; virDomainPtr dom = virDomainLookupByName(virt, private_names[vm_idx]); res = virDomainGetInfo(dom, &res_util); vminfo[vm_idx].vm_state = vm_libvirt_state_to_vmm_state(res_util.state); Regards Ritesh Sharma

I have a number of systems running solaris10 and i see the package and binary for dtrace installed however whenever we try to run anything we get this error dtrace: failed to initialize dtrace: DTrace device not available on system the only system in which i dont have this error is the development server that has the full solaris 10 install while others are minimized, do i need additional

...tate = cidl_vm_state_not_defined; } return state; } virDomainInfo res_util; virDomainPtr dom = virDomainLookupByName(virt, private_names[vm_idx]); res = virDomainGetInfo(dom, &res_util); vminfo[vm_idx].vm_state = vm_libvirt_state_to_vmm_state(res_util.state); Regards Ritesh Sharma

...ame(virt, > > private_names[vm_idx]); Are you sure you're passing the correct name here? That's the only possible source of the error here. > > res = virDomainGetInfo(dom, &res_util); > > vminfo[vm_idx].vm_state = > > vm_libvirt_state_to_vmm_state(res_util.state); > > Michal

...rt, > > > private_names[vm_idx]); Are you sure you're passing the correct name here? That's the only possible source of the error here. > > res = virDomainGetInfo(dom, &res_util); > > vminfo[vm_idx].vm_state = > > vm_libvirt_state_to_vmm_state(res_util.state); > > Michal

The series introduces auto-generation of the type definitions used in the libxl interface followed by auto-generation of a destructor function for each type. In the future it may be possible to use the related data structures for other purposes, for example auto-generation of the functions to marshal between C and language binding data types. tools/_libxl_types.h should be identical both before

Hello, Third version of the NUMA placement series Xen 4.2. All the comments received during v2''s review have been addressed (more details in single changelogs). The most notable changes are the following: - the libxl_cpumap --> libxl_bitmap renaming has been rebased on top of the recent patches that allows us to allocate bitmaps of different sizes; - the heuristics for deciding