[kernel-xen] kernel-xen-3.8.10-1 & xen-4.2.2-3 released

[Gordan Bobic]

It would appear that as of this update, the shutdown sort-of hangs. It 
gets stuck while shutting down the VMs indefinitely printing dots, even 
though there are no VMs actually running to begin with (or perhaps there 
being no VMs to shut down might be the cause of it being stuck in the 
loop. Possibly related to parallel shutdowns?

Gordan

On 05/03/2013 07:57 AM, Steven Haigh wrote:
> Currently syncing to mirrors:
> Xen changes:
> * Fri May 03 2013 Steven Haigh <netwiz at crc.id.au> - 4.2.2-3
> - XSA-45 (CVE-2013-1918) - Several long latency operations are not
> preemptible
> - XSA-49 (CVE-2013-1952) - VT-d interrupt remapping source validation
> flaw for bridges
>
> * Sun Apr 28 2013 Steven Haigh <netwiz at crc.id.au> - 4.2.2-2 (Unreleased)
> - Updated xendomains initscript:
>      - Run DomU shutdowns in parallel to decrease time required for Dom0
> shutdown
>      - Correct usage of xm / xl based on if xend is being used. xend is
> still the default on
>        installation, but is now optional. To use xl, disable the xend
> service and reboot the Dom0
> - Updated xenstored initscript:
>      - Do the basics to allow xl to operate as required. Removes
> reliance on xencommons initscript.
>
> kernel-xen changes:
> * Sun Apr 28 2013 Steven Haigh <netwiz at crc.id.au> - 3.8.10-1
> - Update to kernel 3.8.10
> - Change CONFIG_NR_CPUS to 32
> - Change CONFIG_HOTPLUG_PCI_PCIE to m to address RH BZ#908023
>
> * Sat Apr 27 2013 Steven Haigh <netwiz at crc.id.au> - 3.8.8-2 (Unreleased)
> - Add patches to fix bug #3 where the Dom0 disables networking for
>    network errors from the DomU with entries in /var/log/messages like
>    Apr 25 12:09:25 hosting kernel: vif vif-4-0 vif.crc: Frag is bigger
> than frame.
>    Apr 25 12:09:25 hosting kernel: vif vif-4-0 vif.crc: fatal error;
> disabling device
>    Apr 25 12:09:25 hosting kernel: br0: port 5(vif.crc) entered disabled
> state
>
>
>