Invalid Kernel: FC6 Guest + Asterisk, FC10 Host [message #35399] |
Mon, 23 March 2009 16:01 |
sjdean
Messages: 30 Registered: May 2008
|
Member |
|
|
Im trying to run a Fedora 6 install that I rescued off some old hardware as a container on a Fedora 10 host. Both x86 versions.
When I try to start the container, I get:
Invalid Kernel, or some kernel modules not loaded
Now bear in mind, that the Fedora 6 guest, is running kernel 2.6.18, while the Fed 10 host is running 2.6.27 the devel branch downloaded from OpenVZ.
Is that the problem?
Or is the problem that the fedora 6 guest also is running Asterisk? I forget whether Asterisk has any modules that need loading.
Any thoughts?
Maybe just downgrade to Fedora 6 for the host too?
Cya
Simon
|
|
|
|
|
|
|
|
Re: Invalid Kernel: FC6 Guest + Asterisk, FC10 Host [message #35418 is a reply to message #35399] |
Tue, 24 March 2009 22:52 |
sjdean
Messages: 30 Registered: May 2008
|
Member |
|
|
Still got the same problems with the Fedora Core 6 container I copied from a physical host.
I've installed a CentOS 5 container template from OpenVZ which works fine.
I've gone through the entire /dev of the CentOS 5 Container (102) and copied to my Fedora Core 6 Container (101) without any joy.
The last few lines of the strace -ff are:
[pid 19341] ioctl(4, 0x400c2e05, 0xbfacebd0) = 101
[pid 19341] setgroups32(0, []) = 0
[pid 19341] close(4) = 0
[pid 19341] open("/dev/ptmx", O_RDWR) = -1 ENOENT (No such file or directory)
[pid 19341] open("/dev/ptyp0", O_RDWR) = -1 ENOENT (No such file or directory)
[pid 19341] write(2, "Unable to open pty", 18) = 18
[pid 19341] write(2, ": No such file or directory", 27) = 27
[pid 19341] write(2, "\n", 1) = 1
[pid 19341] write(9, "\377\377\377\377", 4) = 4
[pid 19340] <... read resumed> "\377\377\377\377", 4) = 4
[pid 19340] fstat64(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 1), ...}) = 0
[pid 19340] mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7f97000
[pid 19340] write(1, "enter into CT 101 failed\n", 25enter into CT 101 failed
) = 25
[pid 19340] fcntl64(6, F_GETFL) = 0 (flags O_RDONLY)
[pid 19340] fcntl64(6, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
[pid 19340] read(6, "Unable to open pty: No such file"..., 10239) = 46
[pid 19340] write(1, "Unable to open pty: No such file"..., 46Unable to open pty: No such file or directory
) = 46
[pid 19340] read(6, 0xbfacc3e0, 10239) = -1 EAGAIN (Resource temporarily unavailable)
I've checked rc.sysinit on both, and both have the udev start line:
rc.sysinit has udev started on both
rc.sysinit:/sbin/start_udev
/etc/udev/makedev.d/50-udev.nodes shows the following on 101:
tty1
tty2
tty3
tty4
tty5
tty6
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
parport0
parport1
parport2
parport3
net/tun
ppp
console
null
zero
while the Working system, 102, shows:
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
parport0
parport1
parport2
parport3
net/tun
ppp
console
null
zero
user_beancounters show:
uid resource held maxheld barrier limit failcnt
102: kmemsize 934718 1315837 11055923 11377049 0
lockedpages 0 0 256 256 0
privvmpages 3332 7240 65536 69632 0
shmpages 31 31 21504 21504 0
dummy 0 0 0 0 0
numproc 12 18 240 240 0
physpages 1940 2559 0 2147483647 0
vmguarpages 0 0 33792 2147483647 0
oomguarpages 1940 2559 26112 2147483647 0
numtcpsock 4 4 360 360 0
numflock 5 7 188 206 0
numpty 0 0 16 16 0
numsiginfo 0 2 256 256 0
tcpsndbuf 35776 0 1720320 2703360 0
tcprcvbuf 65536 0 1720320 2703360 0
othersockbuf 6708 8620 1126080 2097152 0
dgramrcvbuf 0 8380 262144 262144 0
numothersock 9 11 360 360 0
dcachesize 0 0 3409920 3624960 0
numfile 433 584 9312 9312 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
numiptent 10 10 128 128 0
101: kmemsize 3867358 4067179 11055923 11377049 0
lockedpages 0 0 256 384 0
privvmpages 62330 62783 65536 69632 0
shmpages 173 173 21504 21504 0
dummy 0 0 0 0 0
numproc 56 61 240 240 0
physpages 14200 14800 0 2147483647 0
vmguarpages 0 0 33792 2147483647 0
oomguarpages 14200 14800 26112 2147483647 0
numtcpsock 16 17 360 360 0
numflock 8 10 188 206 0
numpty 0 1 16 16 0
numsiginfo 1 4 256 256 0
tcpsndbuf 143104 0 1720320 2703360 0
tcprcvbuf 212992 0 1720320 2703360 0
othersockbuf 64144 72492 1126080 2097152 0
dgramrcvbuf 0 8380 262144 262144 0
numothersock 46 50 360 360 0
dcachesize 0 0 3409920 3624960 0
numfile 1430 1491 9312 9312 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
numiptent 10 10 128 128 0
While the dev folder on 101 contains:
[root@localhost dev]# dir
console mem ptya1 ptya8 ptyaf ptyp6 ptypd random ttya3 ttyaa ttyp1 ttyp8 ttypf
core null ptya2 ptya9 ptyp0 ptyp7 ptype stderr ttya4 ttyab ttyp2 ttyp9 urandom
fd port ptya3 ptyaa ptyp1 ptyp8 ptypf stdin ttya5 ttyac ttyp3 ttypa zero
full ptmc ptya4 ptyab ptyp2 ptyp9 ram stdout ttya6 ttyad ttyp4 ttypb
initctl ptmx ptya5 ptyac ptyp3 ptypa ram0 ttya0 ttya7 ttyae ttyp5 ttypc
kmem pts ptya6 ptyad ptyp4 ptypb ram1 ttya1 ttya8 ttyaf ttyp6 ttypd
kmsg ptya0 ptya7 ptyae ptyp5 ptypc ramdisk ttya2 ttya9 ttyp0 ttyp7 ttype
The container cannot be entered if I simply do this from outside the container:
/sbin/MAKEDEV -d /vz/private/123/dev ttyp ptyp
But I can do this:
vzctl exec 101 /sbin/MAKEDEV tty
vzctl exec 101 /sbin/MAKEDEV pty
vzctl enter 101
At this stage, Im thinking... Memory?
Cheers
Simon
|
|
|
|
Re: Invalid Kernel: FC6 Guest + Asterisk, FC10 Host [message #35428 is a reply to message #35423] |
Wed, 25 March 2009 09:04 |
sjdean
Messages: 30 Registered: May 2008
|
Member |
|
|
Well this is the listing of dev in the container before I run the commands:
[root@localhost dev]# ls -al pt*
crw-rw-rw- 1 root root 5, 2 Mar 24 12:41 ptmc
crw-rw-rw- 1 root root 5, 2 Mar 24 19:35 ptmx
crw-rw-rw- 1 root tty 2, 176 Mar 24 20:05 ptya0
.
.
.
crw-rw-rw- 1 root tty 2, 191 Mar 24 20:05 ptyaf
crw-rw-rw- 1 root tty 2, 0 Mar 24 20:05 ptyp0
.
.
.
crw-rw-rw- 1 root tty 2, 15 Mar 24 20:05 ptypf
And in fact, I only have to run one of the commands in order to enter the container.
I either run
vzctl exec 101 /sbin/MAKEDEV ptmx
or I run
vzctl exec 101 /sbin/MAKEDEV ptyp0
I don't understand this to be honest. But I think something really strange is happening.
[Updated on: Wed, 25 March 2009 09:06] Report message to a moderator
|
|
|