Displaying 6 results from an estimated 6 matches for "nenolod".
2008 Apr 11
3
Sucessful Upgrade from 3.0.4 to 3.2 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
2009 Jan 24
2
Bug#512900: xen-hypervisor-3.2-1-amd64: don't support core 2 duo processor
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:
2009 Mar 10
1
Bug#519149: xen-3: does not really load bzImage kernels.
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)
| *
2008 Feb 10
3
Bug#464969: xen-hypervisor-3.2-1-i386: Linux mmap()/vmsplice() exploit causes memory map corruption in hypervisor regardless of domain privilege
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]
2009 Jan 27
1
Bug#512900:
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
2008 Mar 20
7
Cacti-based monitoring
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