Installation guide

Resolved Issues

• the crash utility could not analyze x86_64 vmcores from systems running kernel-xen because

the Red Hat Enterprise Linux hypervisor was relocatable and the relocated physical base address is

not passed in the vmcore file's ELF header. The new --xen_phys_start command line option for

the crash utility allows the user to pass crash the relocated base physical address.

• Not all mouse events were being captured and processed by the Paravirtual Frame Buffer

(PVFB). Consequently, the scroll wheel did not function when interacting with a paravirtualized

guest with the Virtual Machine Console. In this update, scroll wheel mouse events are now

handled correctly, which resolves this issue.

• Using Virtualization on a machine with a large number of CPUs may have caused the hypervisor to

crash during guest installation. In this update, this issue has been resolved.

• On Intel processors that return a CPUID family value of 6, only one performance counter register

was enabled in kernel-xen. Consequently, only counter 0 provided samples. In this update, this

issue has been resolved.

6.2.2. x86 Architectures

• On systems with newer CPU's, the CPU APIC ID differs from the CPU ID. Consequently, the

virtualized kernel was unable to initialize CPU frequency scaling. In this update, the virtualized

kernel now retrieves CPU APIC ID from the hypervisor, allowing CPU frequency scaling to be

initialized properly.

• When running an x86 paravirtualized guest, if a process accessed invalid memory, it would run in a

loop instead of getting a SEGV signal. This was caused a flaw in the way execshield checks were

done under the hypervisor. In this update, this issue has been resolved.

6.2.3. ia64 Architecture

• A xend bug that previously caused guest installation failures is now fixed.

• the evtchn event channel device lacked locks and memory barriers. This led to xenstore

becoming unresponsive. In this update, this issue has been resolved.

• Non-Uniform Memory Access (NUMA) information was not being displayed by the xm info

command. Consequently, node_to_cpu value for each node was being incorrectly returned as no

cpus. In this update, this issue has been resolved.

• Previously, creating a guest on a Hardware Virtual Machine (HVM) would fail on processors that

include the VT-i2 technology. In this update, this issue has been resolved.

6.2.4. x86_64 Architectures

• When the Dynamic IRQs available for guests virtual machines were exhausted, the dom0 kernel

would crash. In this update, the crash condition has been fixed, and the number of available IRQs

has been increased, which resolves this issue.

• On systems with newer CPU's, the CPU APIC ID differs from the CPU ID. Consequently, the

virtualized kernel was unable to initialize CPU frequency scaling. In this update, the virtualized

kernel now retrieves CPU APIC ID from the hypervisor, allowing CPU frequency scaling to be

initialized properly.