From: Anthony Brock <brocka@st...> - 2008-06-22 05:21:20
I have been running several UML instances on older kernels for some time
hoping to see a fix for the random issue. However, a recent upgrade to
2.6.26-rc5 now reults in periodic boot failures of the virtual systems.
Downgrading to 2.6.25-rc2-mm1 returns to previous behavior (reliable boot,
but other issues).
This is running on a host with SKAS3 patches applied (18.104.22.168-skas3-v8.2)
in a chroot'ed environment (/proc/mm is mounted in the chroot).
Unfortunately, I'm uncertain of what information will help. Here is the
output from a strace on an instance that "froze" during boot:
# strace -p 4997
Process 4997 attached - interrupt to quit
restart_syscall(<... resuming interrupted call ...>
I never moves beyond this point. The console output for this "freeze" is
Locating the top of the address space ... 0xc0000000
Core dump limits :
soft - 0
hard - NONE
Checking that ptrace can change system call numbers...OK
Checking syscall emulation patch for ptrace...OK
Checking advanced syscall emulation patch for ptrace...OK
Checking for tmpfs mount on /dev/shm...failed to open /proc/mounts, errno = 2
Checking PROT_EXEC mmap in /dev/shm/...OK
Checking for the skas3 patch in the host:
UML running in SKAS3 mode
This is a show-stopper for upgrading as:
1. What instances fail to boot change every time the host is rebooted.
2. Once an instance decides to fail, to further attempts to start it will
succeed until I downgrade the kernel.
Ideas? Thanks in advance!