linux-um archives
 help / color / mirror / Atom feed
From: "Phill Wombat" <uml@webwombat.com>
To: user-mode-linux-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: [uml-devel] sysctl -w va.legacy_va_layout=1
Date: Mon, 1 Aug 2005 12:53:39 +1000	[thread overview]
Message-ID: <003e01c59644$3893a5b0$3c01010a@webwombat.com.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1966 bytes --]

RegardsHi Paolo,

Looking into another issue (my son's gaming machine - counter-strike source on linux) I came across this interesting parameter whereby winex/Cedega won't run steam unless legacy support for legacy VA layout is enabled on a 2.6.9 kernel.

Well, I thought, I'd better try that out......

With 2.6.12+bs9 on x86_64 the error now changes

On the host set:
sysctl -w va.legacy_va_layout=1
sysctl -w kernel.randomize_va_space=0

Starting the uml with init=/bin/sh starts up as usual. Performing the ls command now result in a different thing happening:
Bad op in do_proc_op

Where as before it produced:
Child 22915 exited with signal 11

Furthermore, Ctrl-C shuts everything down cleanly. Don't the significance if any of all this, but if feels better.

Conducting the same test on 32bit 2.6.12+bs9 results in total disaster (feels very bad):

<0>Kernel panic - not syncing: fix_range fixing wrong address space, current=0xabebf6c0
folloed by lost of register dumps and traceback stuff (2 lots actually - which I take to mean it really really crashed).

I can only get init=/bin/sh to go when kernel.randomize_va_space=1 and vm.legacy_va_layout=0
Running the ls command then results in a message similar to:
Child 22915 exited with signal 11

Perhaps the only thing of value in all this is va.legacy_va_layout which may be useful to UML. It seems to do something, I just don't know what.

Cheers
Phill.

>Hi Paolo,
>
>>Try also following this (from another email) - it appeared in vanilla
>>2.6.12 
>>and may be in your FC4 kernel. Not sure but it may be playing a role
>>here:
>>
>>"It looks like VA space randomization is the culprit.  The problem only
>>shows up when the host is 2.6.12, and can be solved by setting the
>>kernel.randomize_va_space sysctl to zero.  Thanks for the pointer
>>there."
>
>Here are the results with sysctl -w kernel.randomize_va_space=0.
>Essentially no effect observed.


[-- Attachment #2: Type: text/html, Size: 5086 bytes --]

             reply	other threads:[~2005-08-01  2:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-01  2:53 Phill Wombat [this message]
2005-10-04 17:01 ` [uml-devel] sysctl -w va.legacy_va_layout=1 Blaisorblade

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='003e01c59644$3893a5b0$3c01010a@webwombat.com.au' \
    --to=uml@webwombat.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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