From: Mark H Weaver <mhw@netris.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: 01/02: gnu: qemu: Update to 2.9.0 [security fixes].
Date: Thu, 20 Apr 2017 21:06:51 -0400 [thread overview]
Message-ID: <87zifa602c.fsf@netris.org> (raw)
In-Reply-To: <20170420182405.ED2D520740@vcs0.savannah.gnu.org> (Leo Famulari's message of "Thu, 20 Apr 2017 14:24:05 -0400 (EDT)")
leo@famulari.name (Leo Famulari) writes:
> lfam pushed a commit to branch master
> in repository guix.
>
> commit dfa663c963a7c0745f18cbfab4b45eb335742602
> Author: Leo Famulari <leo@famulari.name>
> Date: Fri Apr 7 09:03:28 2017 -0400
>
> gnu: qemu: Update to 2.9.0 [security fixes].
>
> Fixes CVE-2017-{5857,5973,5987,6058,6505,7377,7471,7718}.
Thanks for this! Obviously it's an important security update, but:
On my x86_64 system running GuixSD, 'grub' now fails to build from
source. Three times in a row, the 'grub_cmd_set_date' has failed.
Here's the relevant excerpt from test-suite.log (lightly formatted):
FAIL: grub_cmd_set_date
=======================
qemu-system-i386: Trying to execute code outside RAM or ROM at 0xefffff53
This usually means one of the following happened:
(1) You told QEMU to execute a kernel for the wrong machine type, and
it crashed on startup (eg trying to run a raspberry pi kernel on a
versatilepb QEMU machine)
(2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU
executed a ROM full of no-op instructions until it fell off the end
(3) Your guest kernel has a bug and crashed by jumping off into nowhere
This is almost always one of the first two, so check your command line
and that you are using the right type of kernel for this machine.
If you think option (3) is likely then you can try debugging your
guest with the -d debug options; in particular -d guest_errors will
cause the log to include a dump of the guest register state at this
point.
Execution cannot continue; stopping here.
Test failed: 2017-04-21 00:08:44 Friday
The build appears to have succeeded on Hydra:
https://hydra.gnu.org/eval/109616?filter=grub
Unfortunately the substitute is not yet available, so for the moment I'm
stuck. I'll look into disabling this test for now.
Has anyone else seen this?
Mark
next parent reply other threads:[~2017-04-21 1:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170420182405.2682.82446@vcs0.savannah.gnu.org>
[not found] ` <20170420182405.ED2D520740@vcs0.savannah.gnu.org>
2017-04-21 1:06 ` Mark H Weaver [this message]
2017-04-21 17:37 ` 01/02: gnu: qemu: Update to 2.9.0 [security fixes] Leo Famulari
2017-04-21 18:31 ` Mark H Weaver
2017-04-21 19:02 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zifa602c.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.