I have been trying to replicate the 2.6.9-bb4 shutdown hangs that some
users have been experiencing. At the same time, I am building a new
server at home that has a VERY minimal host os (think just enough to run
iptables and uml-tools). The only way I have found to replicate the hang
is if /p
Hi !
>The only way I have found to replicate the hang
> is if /proc is not mounted on the host system.
Doesn`t this mean, your UML is beig forced to run in TT mode this way ?
IIRC, UML checks for /proc/mm on startup - if it finds it, it runs in SKAS-Mode
- if not, it runs in TT mode.
Probably I`m
My uml system hangs after running for 16-48 hours. I cannot connect,
nor can I use mconsole.
I am running debian testing on both host and uml. Uml kernel is from
debian package 2.4.26-1um. Host kernel is 2.4.24 with SKAS patch.
I am new to UML, how do I investigate this?
--
"In the land
Hi,
In my case I have normal access to /proc. Also I execute uml's as root so I
do not have permission problems.
The problem could be related with xterm. See my answer to the ""Zombie"
linux process (UML 2.6.9 on 2.6.9-skas3-v7 host)" subject in a next mail.
Best regards,
David
> -Mensaj
Just a new fact (and solution) I discovered related to the zombie process.
As pointed by Paolo, It seems the problem is related in some way to xterms.
I have checked that adding the following to the command line:
xterm=gnome-terminal,-t,-x
which changes xterms to gnome-terminals, the zombie pro
hi,
i've compiled my own guest-kernel (2.6.9 with bb4-patch)
my host is a 2.6.10 with skas-v7-patch.
when I start my own guest-kernel, the kernel quits at
"kernel: Initializing stdio console driver"
with no error.
when I start die UML-kernel which comes with debian,
the uml starts fine.
greets
good point, but it still seems to find the skas patch and continue on its
way. Not sure why that is working.
Jason
The place where you made your stand never mattered.
Only that you were there... And still on your feet.
On Tue, 4 Jan 2005, roland wrote:
Hi !
The only way I have found to re
hi,
maybe your guest filesystem has empty /dev. Check if in your own guest
kernel you added devfs:
File system -> Pseudo filesystems
[*] /dev file system support (OBSOLETE)
[*] Automatically mount at boot (NEW)
Rgds,
Konrad
---
[EMAIL PROTECTED] wrote:
> hi,
>
> i've compiled my