search for: cpunum

Displaying 16 results from an estimated 16 matches for "cpunum".

Did you mean: cpu_num
2010 Apr 19
1
[PATCH matahari] Removes all code for the previous CPUWrapper class.
...;> t)) - throw invalid_argument("Conversion failure for " + str); - return t; -} - -ostream& operator<<(ostream& output, const CPUWrapper& cpu) -{ - output << "Processor" << endl; - output << "CPU #: " << cpu.cpunum << endl; - output << "Core #: " << cpu.corenum << endl; - output << "Num. Cores: " << cpu.numcores << endl; - output << "Model: " << cpu.model << endl; - output << "Family: " <&l...
2008 Nov 22
5
xvm start xend won''t work
...t;/usr/lib/python2.4/site-packages/xen/xend/XendNode.py", line 635, in instance File "/usr/lib/python2.4/site-packages/xen/xend/XendNode.py", line 92, in __init__ File "/usr/lib/python2.4/vendor-packages/xen/xend/osdep.py", line 140, in _solaris_get_cpuinfo (module, cpunum, combo, namevalue) = kstatline.split (":") ValueError: need more than 3 values to unpack [2008-11-22 10:59:00 579] INFO (SrvDaemon:334) Xend Daemon started [2008-11-22 10:59:00 579] INFO (SrvDaemon:338) Xend changeset: Mon Oct 13 22:14:51 2008 -0700 15904:94bd0a643efe. [2008-11-22 10:59:0...
2009 Jul 29
3
yum update broke ovirt
I did a yum update on my management server and now the ovirt gui is no longer accessable. Is it supposed to just work or do I need to do something after the yum update? Justin.
2012 Jul 10
1
Issue with getCPUStats and getMemoryStats
...ALL_CPUS' >>> print con.getCPUStats(2, None, 0, 0) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib64/python2.6/site-packages/libvirt.py", line 2173, in getCPUStats ret = libvirtmod.virNodeGetCPUStats(self._o, cpuNum, params, nparams, flags) *AttributeError: 'module' object has no attribute 'virNodeGetCPUStats'* >>> print con.getMemoryStats(2, None, 0, 0) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib64/python2.6/sit...
2010 Mar 15
0
[PATCH] Updated the list of ignored files and fixed whitespace issues.
...; return t; -} +} -ostream& operator<<(ostream& output, const CPUWrapper& cpu) +ostream& operator<<(ostream& output, const CPUWrapper& cpu) { output << "Processor" << endl; output << "CPU #: " << cpu.cpunum << endl; @@ -61,7 +61,7 @@ void CPUWrapper::setupQMFObject(ManagementAgent *agent, Manageable *parent) { mgmt_object = new _qmf::CPU(agent, this, parent); agent->addObject(mgmt_object); - syncQMFObject(); + syncQMFObject(); } void CPUWrapper::cleanupQMFObject(void)...
2009 Jul 10
2
[PATCH: server 0/3] Add host-register.rb (replaces host-browser.rb in part)
Removes node identification functionality from host-browser.rb and adds a new script, host-register.rb, that takes over that functionality. The chief difference is that host-browser used a simple TCP server setup to get data from the node, while host-register uses the qpid bus to do so. Specifically, it communicates with the matahari qmf agent added to the node in two related patchsets to node
2010 Nov 12
3
Updating oVirt Server to the latest Matahari 0.4.0 schema
...key Next, old Matahari has 1:N relationship between host and cpu objects, ovirt-server uses it by retrieving a list of cpus for each host: cpu_info = @qmfc.objects(:package => 'com.redhat.matahari', :class => 'cpu', 'host' => host.object_id) cpu properties used: cpunum corenum numcores vendor model family cpuid_lvl speed cache flags[0..251] New Matahari changed the model, here are CPU-related properties from 0.4.0 Host object, there isn't separate cpu class anymore: processors uint8 ReadOnly The number of physical...
2009 Jul 08
1
[PATCH: host-browser replacement 0/3] replacement of host-browser on ovirt-server
The purpose of this patch is to replace the identify function in host-browser.rb with a new script, host-register.rb. host-register.rb is a qmf ruby console that interfaces with the newly added matahari qmf agent on the ovirt node. While it stores node data in the database with the same behavior as the original host-browser implementation, it acquires the data using the amqp protocol (and
2007 Apr 18
1
[PATCH] Add smp_ops interface
...p_call_function_mask(cpumask_t mask, + void (*func) (void *info), void *info, + int wait) +{ + return smp_ops.smp_call_function_mask(mask, func, info, wait); +} + +void native_smp_prepare_boot_cpu(void); +void native_smp_prepare_cpus(unsigned int max_cpus); +int native_cpu_up(unsigned int cpunum); +void native_smp_cpus_done(unsigned int max_cpus); #ifndef CONFIG_PARAVIRT #define startup_ipi_hook(phys_apicid, start_eip, start_esp) \
2007 Apr 18
1
[PATCH] Add smp_ops interface
...p_call_function_mask(cpumask_t mask, + void (*func) (void *info), void *info, + int wait) +{ + return smp_ops.smp_call_function_mask(mask, func, info, wait); +} + +void native_smp_prepare_boot_cpu(void); +void native_smp_prepare_cpus(unsigned int max_cpus); +int native_cpu_up(unsigned int cpunum); +void native_smp_cpus_done(unsigned int max_cpus); #ifndef CONFIG_PARAVIRT #define startup_ipi_hook(phys_apicid, start_eip, start_esp) \
2009 Nov 04
4
[PATCH server] Update daemons to use new QMF.
...ogger.info "Saving new CPU records for host #{host_qmf.hostname}" - cpu_info.each do |cpu| - flags = (cpu.flags.length > 255) ? "#{cpu.flags[0..251]}..." : cpu.flags - detail = Cpu.new( - 'cpu_number' => cpu.cpunum, - 'core_number' => cpu.corenum, - 'number_of_cores' => cpu.numcores, - 'vendor' => cpu.vendor, - 'model' => cpu.model.to_s, -...
2007 Oct 31
3
[PATCH 0/7] (Re-)introducing pvops for x86_64 - Consolidation part
Hi folks, Here is the result of the latest work on the pvops front, after the x86 arch merge. From the functionality point of view, almost nothing was changed, except for proper vsmp support - which was discussed, but not implemented before - and the introduction of smp_ops in x86_64, which eased the merging of the smp header. Speaking of the merge, a significant part (although not majority) of
2007 Oct 31
3
[PATCH 0/7] (Re-)introducing pvops for x86_64 - Consolidation part
Hi folks, Here is the result of the latest work on the pvops front, after the x86 arch merge. From the functionality point of view, almost nothing was changed, except for proper vsmp support - which was discussed, but not implemented before - and the introduction of smp_ops in x86_64, which eased the merging of the smp header. Speaking of the merge, a significant part (although not majority) of
2007 Apr 18
34
[patch 00/34] Xen-pv_ops: Xen guest implementation for paravirt_ops interface
Hi Andi, This patch series implements the Linux Xen guest as a paravirt_ops backend. The features in implemented this patch series are: * domU only * UP and SMP guest support (NEW!) * dynamic ticks (NEW!) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes (non-PAE may be broken at the moment) * xen hvc console
2007 Apr 18
34
[patch 00/34] Xen-pv_ops: Xen guest implementation for paravirt_ops interface
Hi Andi, This patch series implements the Linux Xen guest as a paravirt_ops backend. The features in implemented this patch series are: * domU only * UP and SMP guest support (NEW!) * dynamic ticks (NEW!) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes (non-PAE may be broken at the moment) * xen hvc console
2007 Apr 18
34
[patch 00/34] Xen-pv_ops: Xen guest implementation for paravirt_ops interface
Hi Andi, This patch series implements the Linux Xen guest as a paravirt_ops backend. The features in implemented this patch series are: * domU only * UP and SMP guest support (NEW!) * dynamic ticks (NEW!) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes (non-PAE may be broken at the moment) * xen hvc console