From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: qemu again :(
Date: Thu, 05 Nov 2009 10:29:32 +0100 [thread overview]
Message-ID: <4AF29AFC.8030804@dresearch.de> (raw)
In-Reply-To: <alpine.LFD.2.00.0911050322460.17459@localhost>
Robert P. J. Day wrote:
>> Yesterday i tried to use OE at my new notebook for the first time. But
>> i hit a qemu problem again:
>> ...
>> | mmap: Permission denied
>>
>> All solutions for this problem i found see the cause in a wrong
>> setting of mmap_min_addr (see e.g.
>> <http://www.bugcommunity.com/wiki/index.php/Kernel_and_Rootfs_Build_System#Potential_Problems_.26_Their_Solutions:>).
>>
>> But this setting is correct at my notebook:
>>
>> # cat /proc/sys/vm/mmap_min_addr
>> 0
> ...
> and if you read carefully, you'll notice that even if that value is
> correctly set to zero, you might still get an SELinux violation. it's
> just a suggestion.
Thanx for the hint, but there's no SELinux (and no Apparmor) running.
Steffen
next prev parent reply other threads:[~2009-11-05 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 16:03 qemu again :( Steffen Sledz
2009-11-05 8:24 ` Robert P. J. Day
2009-11-05 9:29 ` Steffen Sledz [this message]
2010-01-12 12:06 ` Marc Olzheim
2010-01-18 10:57 ` Steffen Sledz
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=4AF29AFC.8030804@dresearch.de \
--to=sledz@dresearch.de \
--cc=openembedded-devel@lists.openembedded.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