Red Hat ENTERPRISE 5.3 RELEASE NOTES Guia de Instalação descarregar pdf (Página 30)

6.2.4 . x86_64 Archit ectures

When the Dynamic IRQs available for guests virtual machines were exhausted, the dom 0 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.

6.3. Known Issues

6.3.1. All Architect ures

Diskette drive media will not be accessible when using the virtualized kernel. T o work around this,

use a USB-attached diskette drive instead.

Note that diskette drive media works well with other non-virtualized kernels.

In live migrations of paravirtualized guests, time-dependent guest processes may function improperly

if the corresponding hosts' (dom0) times are not synchronized. Use NT P to synchronize system

times for all corresponding hosts before migration.

Repeated live migration of paravirtualized guests between two hosts may cause one host to panic. If

a host is rebooted after migrating a guest out of the system and before migrating the same guest

back, the panic will not occur.

Formatting a disk when running Windows 2008 or Windows Vist a as a guest can crash when the

guest has been booted with multiple virtual CPUs. To work around this, boot the guest with a single

virtual CPU when formatting.

Fully virtualized guests created through virt-m anager may sometimes prevent the mouse from

moving freely throughout the screen. To work around this, use virt-manager to configure a USB

tablet device for the guest.

The maximum CPUs must be restricted to less than 128 when on a 128 or greater CPU system. The

maximum that is supported at this time is 126. Use the m axcpus=126 hypervisor argument to limit

the Hypervisor to 126

Fully virtualized guests cannot correct for time lost due to the domain being paused and unpaused.

Being able to correctly track the time across pause and unpause events is one of the advantages of

paravirtualized kernels. This issue is being addressed upstream with replaceable timers, so fully

virtualized guests will have paravirtualized timers. Currently, this code is under development

upstream and should be available in later versions of Red Hat Enterprise Linux.

Repeated migration of paravirtualized guests may result in bad mpa messages on the dom 0

console. In some cases, the hypervisor may also panic.

To prevent a hypervisor kernel panic, restart the migrated guests once the bad mpa messages

appear.

When setting up interface bonding on dom 0, the default network-bridge script may cause

bonded network interfaces to alternately switch between unavailable and available. This

occurrence is commonly known as flapping.

To prevent this, replace the standard network-script line in /etc/xen/xend-config.sxp with

the following line:

(network-script network-bridge-bonding netdev=bond0)

6. Virtualization

1 2 ... 25 26 27 28 29 30 31 32 33 34 35 ... 208 209

Comentários a estes Manuais

Sem comentários

Red Hat ENTERPRISE 5.3 RELEASE NOTES Guia de Instalação Página 30

Comentários a estes Manuais

Manuais e produtos relacionados com Telefones Red Hat ENTERPRISE 5.3 RELEASE NOTES