search for: pitcock

Hi, I maintain several dom0 hosts, and I would like to monitor the following with Cacti: * the overall hypervisor CPU usage * available hypervisor memory (e.g. memory that can be allocated to new domUs) and maybe: * domU CPU usage But the latter is not as important to me right now. Anyone have any pointers on how I might do this? My knowledge of Cacti is very basic. Basically: has anyone

Hi, Has anyone actually successfully completed an upgrade from 3.0.4 to 3.2 using tar balls? Ive tried various ways but everytime the compile is complete the system just constantly reboots. Ive managed to upgrade fine from other version like 3.0.1 etc but 3.1 and 3.2 are just a nightmare. Ive spent hours on this and am getting nowhere fast. If anyone has any tips they would be

Package: xen-hypervisor-3.2-1-i386 Version: 3.2-1 Severity: critical Tags: security Justification: DoS of entire system regardless of privilege When running the exploit listed in bug 464953 [1], Xen's memory state becomes corrupted and the hypervisor eventually crashes, taking all of the domU's with it. As such, this breaks operational behaviour, so I have marked this as critical. [1]

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: grave Current xen hypervisor don't support Intel Core 2 Duo T9400 processor. Processor supports Intel (R) Virtualization Technology. -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.28.1 (SMP w/2 CPU cores; PREEMPT) Locale:

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: serious After noting that this version supposedly loads bzImage kernels: | xen-3 (3.2.1-2) unstable; urgency=low | | * Use e2fslibs based ext2 support for pygrub. (closes: #476366) | * Fix missing checks in pvfb code. | See CVE-2008-1952. (closes: #487095) | * Add support for loading bzImage files. (closes: #474509) | *

Hello,   I can say that I have searched the entire ''world wide web'' and still haven''t found ''complete  and clear answers'' to the often asked question of: Given a Xen (release) build (say 3.2.0), which by default tries to get and build and assume Linux kernel-xen 2.6.18 from the mercurial repository, HOW TO override the build and make it work with a

Hi everyone, I am very excited to see that dom0 pvops is finally coming close to working, so I wanted to give it a try. >From the description it was not clear to me which kernel to chose as base for the patches.hg, so I took the latest (that was ~ 2 weeks ago) kernel on git.kernel.org I could find (post-2.6.28 git tip at that point). I managed to more or less apply all of the patches in the

severity 512900 important thanks I'm capable of using Xen on this processor, so I am downgrading this bug, as it is definitely not a RC bug. William