[Oraclevm-errata] OVMBA-2015-0146 Oracle VM 3.3 xen bug fix update
Errata Announcements for Oracle VM
oraclevm-errata at oss.oracle.com
Fri Nov 6 12:39:52 PST 2015
Oracle VM Bug Fix Advisory OVMBA-2015-0146
The following updated rpms for Oracle VM 3.3 have been uploaded to the
Unbreakable Linux Network:
x86_64:
xen-4.3.0-55.el6.47.62.x86_64.rpm
xen-tools-4.3.0-55.el6.47.62.x86_64.rpm
SRPMS:
http://oss.oracle.com/oraclevm/server/3.3/SRPMS-updates/xen-4.3.0-55.el6.47.62.src.rpm
Description of changes:
[4.3.0-55.el6.47.62]
- libxl: explicitly allocate BUFIOREQ event channel
There is an OVM-only change for domain creation that is only
implemented for xend. The change is to allocate the buffered IO
request server explicitly instead of doing it by default for VCPU 0.
Without this change qemu cannot initialize and thus failing the domain
creation with the following error in the device model:
bind interdomain ioctl error 22
qemu: hardware error: xen hardware virtual machine initialisation failed
Commit bebfe22 ("Xen: Fix pvhvm migration issue from ovm3.2.8 to
ovm3.4") introduces this change for xend and this patch introduces
it for libxl.
Signed-off-by: Joao Martins <joao.m.martins at oracle.com>
Acked-by: Konrad Rzeszutek Wilk <konrad.wilk at oracle.com>
Acked-by: Adnan Misherfi <adnan.misherfi at oracle.com>
Acked-by: Chuck Anderson <chuck.anderson at oracle.com> [bug 22157512]
[4.3.0-55.el6.47.61]
- Revert "Keep the maxmem and memory same in vm.cfg"
This commit saves original config mem and maxmem and use that in
the populate on demand check. This patch would be a partial fix to Bug
21673915 but memory is still being increased by 4M (with cirrus video)
over reboots and this was being caused by commit
"xend: Fix xm list bug reporting incorrect memory size". Since the
latter is reverted the original behaviour of memory/maxmem is
restored and
leaves this commit with no use.
Reviewed-by: Annie Li <annie.li at oracle.com>
Signed-off-by: Joao Martins <joao.m.martins at oracle.com>
Acked-by: Chuck Anderson <chuck.anderson at oracle.com> [bug 21648484]
[4.3.0-55.el6.47.60]
- xend: fix xm list introducing memory_actual R/O field
Introduces a field to sxp data structures named "memory_actual"
that xm will use to have up-to-date domain memory values from Xen.
This value is always up-to-date when xend refresh the list of domains,
though it's not used in domain management functions like
memory_dynamic_max
and memory_static_max to determine the memory the domain will have if
rebooted/balloned/saved/restored.
Signed-off-by: Joao Martins <joao.m.martins at oracle.com>
Acked-by: Konrad Rzeszutek Wilk <konrad.wilk at oracle.com>
Acked-by: Adnan Misherfi <adnan.misherfi at oracle.com>
Acked-by: Chuck Anderson <chuck.anderson at oracle.com> [bug 21648484]
[4.3.0-55.el6.47.59]
- Revert "xend: Fix xm list bug reporting incorrect memory size"
This patch reverts 6797b4c5 because it introduces a regression
when a guest reboots (on its own initiative) with a PCI passthrough.
By changing xcinfo domain memory with the most up-to-date values
from libxc we will cause a failed reboot (with PCI) and the creation
of a bigger guest and with balloning enabled.
xm creates a guest with X MBs plus 4 (default) megabytes in a HVM guest.
Plus, Xen/libxc won't allocate exactly that amount of memory (e.g. there
is a 128k VGA hole, 8 pages for console/xenstore/etc). This means
from the
view of the toolstack we will always see a gap between mem and maxmem
which
means that PoD gets enabled when guest is rebooted if these memory
values are up-to-date with libxc. Since PCI devices can't be attached
with
PoD enabled, it later causes the bug we observed.
The previous behaviour was to change this domain state only when explicit
for example on xm mem-set, pretty much as xl is doing right now. The next
patch will (re)fix the memory size listing issue which this commit we are
reverting intended to fix.
Signed-off-by: Joao Martins <joao.m.martins at oracle.com>
Acked-by: Konrad Rzeszutek Wilk <konrad.wilk at oracle.com>
Acked-by: Adnan Misherfi <adnan.misherfi at oracle.com>
Acked-by: Chuck Anderson <chuck.anderson at oracle.com> [bug 21648484]
More information about the Oraclevm-errata
mailing list