mbox

[bug#39225,0/2] QEMU updates

Message ID cover.1579632845.git.leo@famulari.name
Headers show

Message

Leo Famulari Jan. 21, 2020, 6:55 p.m. UTC 
The security updates work with our current QEMU package of 4.1.1 as well
as 4.2.0.

I tested both 4.2.0 and the patched 4.1.1 by creating a vm-image and
running it with the "full" QEMU package, and the SLIRP networking works
fine in both cases.

Leo Famulari (2):
  gnu: QEMU: Fix CVE-2020-{7039,7211}.
  gnu: QEMU: Update to 4.2.0.

 gnu/local.mk                                  |   3 +
 gnu/packages/patches/qemu-CVE-2020-7039.patch | 173 ++++++++++++++++++
 gnu/packages/patches/qemu-CVE-2020-7211.patch |  49 +++++
 ...qemu-fix-documentation-build-failure.patch |  43 +++++
 gnu/packages/virtualization.scm               |   7 +-
 5 files changed, 273 insertions(+), 2 deletions(-)
 create mode 100644 gnu/packages/patches/qemu-CVE-2020-7039.patch
 create mode 100644 gnu/packages/patches/qemu-CVE-2020-7211.patch
 create mode 100644 gnu/packages/patches/qemu-fix-documentation-build-failure.patch

Comments

Leo Famulari Jan. 21, 2020, 9:52 p.m. UTC | #1 
On Tue, Jan 21, 2020 at 09:14:40PM +0100, Tobias Geerinckx-Rice wrote:
> Have you run the Guix System test suite with this new Qemu?

The basic and openssh tests did pass. I don't have the computing
resources or time to continue testing it. Can we use Cuirass on
<ci.guix.gnu.org> to test it more fully?
Leo Famulari Jan. 25, 2020, 2:13 a.m. UTC | #2 
On Tue, Jan 21, 2020 at 01:55:50PM -0500, Leo Famulari wrote:
> The security updates work with our current QEMU package of 4.1.1 as well
> as 4.2.0.
> 
> I tested both 4.2.0 and the patched 4.1.1 by creating a vm-image and
> running it with the "full" QEMU package, and the SLIRP networking works
> fine in both cases.

Pushed as 3778b3d9d013a443eec7990c31f47f887f72fe59, along with a 3rd
patch that brings back the QEMU man pages. QEMU 4.0 began requiring the
use of Sphinx to build them:

https://wiki.qemu.org/ChangeLog/4.0#Build_Dependencies