Memory reserved for the kdump kernel was incorrect, resulting in unusable crash dumps. In this
update, the memory reservation is now correct, allowing proper crash dumps to be generated.
Attaching a disk with a specific name (ie. /dev/xvdaa, /dev/xvdab, /dev/xvdbc etc.) to a
paravirtualized guest resulted in a corrupted /dev device inside the guest. T his update resolves the
issue so that attaching disks with these names to a paravirtualized guest creates the proper /dev
device inside the guest.
Previously, the number of loopback devices was limited to 4. Consequently, this limited the ability to
create bridges on systems with more than 4 network interfaces. In this update, the netloop driver
now creates additional loopback devices as required.
A race condition could occur when creating and destroying virtual network devices. In some
circumstances — especially high load situations — this would cause the virtual device to not
respond. In this update, the state of the virtual device is checked to prevent the race condition from
occurring.
a memory leak in virt-m anager would be encountered if the application was left running.
Consequently, the application would constantly consume more resources, which may have led to
memory starvation. In this update, the leak has been fixed, which resolves this issue.
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. T he 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. T his 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 Archit ecture
A xend bug that previously caused guest installation failures is now fixed.
the evtchn event channel device lacked locks and memory barriers. T his 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.
Comentarios a estos manuales