From: Kalle Olavi Niemitalo <kon@iki.fi>
To: libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH 2/2] New internal function __access_noerrno
Date: Mon, 21 Nov 2016 05:12:00 -0000 [thread overview]
Message-ID: <87d1hpiffj.fsf@Niukka.kon.iki.fi> (raw)
In-Reply-To: <60199742-d6f4-3f2a-ad38-619dcfdc7954@linaro.org> (Adhemerval Zanella's message of "Wed, 16 Nov 2016 11:27:42 -0200")
Adhemerval Zanella <adhemerval.zanella@linaro.org> writes:
> Hurd VM does not boot with a recent qemu (2.7.50)
I tried booting debian-hurd-20160824.img (sha256sum
a17547a6b4ae56d2e1e84d82a7308c12f6301c1b4bc9fc210e239730da4a08f5)
with the following versions of QEMU on Debian 8.6 amd64, and did
not see that problem. KVM was enabled, i.e. I ran
qemu-system-i386 -enable-kvm under a user account that was a
member of the kvm group.
* qemu-system-x86 1:2.1+dfsg-12+deb8u6 from Debian
* QEMU 2.7.0 built from source
* QEMU 2.8.0-rc0 + "trace: fix generated code build break"
(commit d4f7ca59017835784c6872dfab0e269d9b41b05a on 2016-11-17)
built from source
next prev parent reply other threads:[~2016-11-21 5:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 17:04 [PATCH 1/2] Consolidate Linux access implementation Adhemerval Zanella
2016-11-10 17:04 ` [PATCH 2/2] New internal function __access_noerrno Adhemerval Zanella
2016-11-10 17:12 ` Andreas Schwab
2016-11-10 18:26 ` Adhemerval Zanella
2016-11-10 17:53 ` Siddhesh Poyarekar
2016-11-10 18:31 ` Adhemerval Zanella
2016-11-16 13:27 ` Adhemerval Zanella
2016-11-16 13:44 ` Adhemerval Zanella
2016-11-16 16:27 ` Carlos O'Donell
2016-11-16 18:29 ` Joseph Myers
2016-11-17 20:53 ` Kalle Olavi Niemitalo
2016-11-17 21:30 ` Adhemerval Zanella
2016-11-18 0:21 ` Kalle Olavi Niemitalo
2016-11-18 18:54 ` Adhemerval Zanella
2016-11-19 3:09 ` Siddhesh Poyarekar
2016-11-21 5:12 ` Kalle Olavi Niemitalo [this message]
2016-11-21 12:45 ` Adhemerval Zanella
2016-11-10 17:44 ` [PATCH 1/2] Consolidate Linux access implementation Siddhesh Poyarekar
2016-11-16 13:16 ` Carlos O'Donell
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=87d1hpiffj.fsf@Niukka.kon.iki.fi \
--to=kon@iki.fi \
--cc=libc-alpha@sourceware.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).