From: Antoine Martin <antoine@nagafix.co.uk>
To: Antoine Martin <antoine@nagafix.co.uk>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] buggy UML AMD64?
Date: Fri, 19 Jan 2007 19:56:25 +0000 [thread overview]
Message-ID: <45B12269.8040203@nagafix.co.uk> (raw)
In-Reply-To: <45B10106.6060107@nagafix.co.uk>
Antoine Martin wrote:
>>>> I have downgraded the x86 boxes to 2.6.15.7 and these are up and
>>>> running again. But I can't do that for all of them, and this is just
>>>> not an option for some of the amd64 boxes.
>>>
>>> My setup is:
>> Thanks for that. That is very similar to mine.
>> I don't think this has anything to do with the guest... So I'll try to
>> remove the skas3 patch from the host and see how it goes.
>>
> I did, and no improvement... x86 guests still hang.
> Could you post a binary guest kernel somewhere so I can try that?
> (even if it isn't static - glibc should be similar since we're using
> Gentoo amd64)
> If that still does not work then I can be certain that it is something
> to do with the host.
I've just tried on 3 more hosts, all AMD64 Gentoo fully up to date,
kernel 2.6.19.2. No skas, no exec shield, no selinux, plain kernel.org:
None of them work with any of the 32-bit kernels!
It prints nothing, just sits there spinning at 100% cpu.
So I am now totally convinced that i haven't got a weird setup.
Something else is broken in UML.
On fully up to date Fedora Core 6 x86_64, the kernel does display
something before crashing:
# uname -a
Linux localhost.localdomain 2.6.18-1.2869.fc6 #1 SMP Wed Dec 20 14:51:34
EST 2006 x86_64 x86_64 x86_64 GNU/Linux
# ./kernel32-2.6.19.2
Checking that ptrace can change system call numbers...OK
Checking syscall emulation patch for ptrace...missing
Checking for tmpfs mount on /dev/shm...OK
Checking PROT_EXEC mmap in /dev/shm/...OK
Checking for the skas3 patch in the host:
- /proc/mm...not found
- PTRACE_FAULTINFO...not found
- PTRACE_LDT...not found
UML running in SKAS0 mode
[root@localhost home]#
This is 100% repeatable. Plain Fedora.
Many users will have a similar setup and will just give up on UML.
So I as I said before, UML is currently unusable for most people out
there running fairly recent systems.
Antoine
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2007-01-19 19:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 16:15 [uml-devel] UML/64bit is miscompiled by gcc 4.0.3 on Ubuntu 6.06 LTS Blaisorblade
2007-01-17 18:17 ` Christopher S. Aker
2007-01-17 18:15 ` Antoine Martin
2007-01-17 19:50 ` Antoine Martin
2007-01-19 11:00 ` [uml-devel] buggy UML AMD64? Antoine Martin
2007-01-19 16:07 ` Daniel Gryniewicz
2007-01-19 16:14 ` Antoine Martin
2007-01-19 16:38 ` Daniel Gryniewicz
2007-01-19 16:42 ` Antoine Martin
2007-01-19 17:33 ` Antoine Martin
2007-01-19 19:56 ` Antoine Martin [this message]
2007-01-21 9:17 ` Boaz Harrosh
2007-01-21 13:04 ` Antoine Martin
2007-01-23 15:20 ` Boaz Harrosh
2007-01-21 14:38 ` Joel Palmius
2007-01-21 14:46 ` Antoine Martin
2007-01-21 14:55 ` Joel Palmius
2007-01-21 16:11 ` Joel Palmius
2007-01-22 22:09 ` Jeff Dike
2007-01-23 0:59 ` Antoine Martin
2007-01-19 16:38 ` Antoine Martin
2007-02-15 3:43 ` [uml-devel] UML/64bit is miscompiled by gcc 4.0.3 on Ubuntu 6.06 LTS Blaisorblade
2007-01-19 23:31 ` Blaisorblade
2007-01-17 23:26 ` Jeff Dike
2007-01-19 23:18 ` Blaisorblade
2007-01-22 20:59 ` Jeff Dike
2007-01-23 8:09 ` 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=45B12269.8040203@nagafix.co.uk \
--to=antoine@nagafix.co.uk \
--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