| Re: VE: 102: failed to start with err=-17 [message #25927 is a reply to message #25925] |
Fri, 11 January 2008 11:26   |
yettyn
Messages: 31
Registered: January 2008
Location: Jihlava, CZ
|
Member |
|
|
I did some changes to the nnn.conf files, basically copying over values that worked with the test box and now got a bit more info in dmesg. I think I got a kernel panic now as I am connected remotely and have 2 shh terminals opened. In the one I started VE's, there I got VE101 ok and then for VE102
Starting VE ...
VE is mounted
Adding IP address(es): 192.168.0.102
and there it stops and the console hangs. Now my 2nd console still works though, however I cannot open a new connection to server with shh.
The functinal console show this with dmesg
VE: 101: started
BUG: unable to handle kernel NULL pointer dereference at virtual address 00000228
printing eip:
c06711e0
*pde = 00000000
Oops: 0002 [#1]
SMP
Modules linked in: vznetdev vzmon iptable_raw xt_comment xt_policy ipt_TTL ipt_ttl ipt_TOS ipt_tos ipt_SAME ipt_REJECT ipt_REDIRECT ipt_recent ipt_owner ipt_NETMAP ipt_MASQUERADE ipt_LOG ipt_iprange ipt_ECN ipt_ecn ipt_CLUSTERIP ipt_ah ipt_addrtype nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_amanda nf_conntrack_tftp nf_conntrack_sip nf_conntrack_proto_sctp nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_netbios_ns nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp xt_tcpmss xt_pkttype xt_physdev xt_NFQUEUE xt_NFLOG xt_multiport xt_MARK xt_mark xt_mac xt_limit xt_length xt_helper xt_hashlimit xt_dccp xt_conntrack xt_CONNMARK xt_connmark xt_CLASSIFY xt_tcpudp xt_state iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack iptable_mangle nfnetlink iptable_filter ip_tables simfs vzdquota vzdev ipt_ULOG x_tables i2c_i801 i2c_core sr_mod r8169 cdrom pcspkr floppy
CPU: 0 VCPU: 102.0
EIP: 0060:[<c06711e0>] Not tainted VLI
EFLAGS: 00010206 (2.6.22-ovz005 #10)
EIP is at mutex_lock+0x0/0x10
eax: 00000228 ebx: ce6b3980 ecx: ce6b3984 edx: c049e050
esi: ce6b3980 edi: d6dbb274 ebp: c049e050 esp: ce967dbc
ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0068
Process vzctl (pid: 23959, veid: 0, ti=ce966000 task=ce962000 task.ti=ce966000)
Stack: c04c05d6 00000000 00000000 ce6b3984 ce6b3980 ce6b3980 d6dbb274 00000000
c04c09bd ce967de4 00000000 00000000 c0530a83 c06cf0e1 ce6b3984 ce6b3984
ce967e2c c2304300 ce6b3980 ffffffea d6dbb274 c06cf0de c0530c71 ce6b3980
Call Trace:
[<c04c05d6>] create_dir+0x26/0x1b0
[<c04c09bd>] sysfs_create_dir+0x3d/0x90
[<c0530a83>] kobject_shadow_add+0x93/0x1a0
[<c0530c71>] kobject_register+0x21/0x50
[<c0530e22>] kobject_kset_add_dir+0x52/0xa0
[<c05aac35>] device_add+0x75/0x4e0
[<c0441703>] ub_slab_charge+0x53/0x80
[<c053076f>] kobject_get+0xf/0x20
[<c0603924>] register_netdevice+0x204/0x4b0
[<c0605279>] register_netdev+0x49/0x70
[<f8fd4a58>] real_env_create+0x918/0xb50 [vzmon]
[<f8fd512d>] vzcalls_ioctl+0x49d/0x4d0 [vzmon]
[<f897117b>] vzctl_ioctl+0x5b/0x60 [vzdev]
[<f8fd4c90>] vzcalls_ioctl+0x0/0x4d0 [vzmon]
[<f8971120>] vzctl_ioctl+0x0/0x60 [vzdev]
[<c04877db>] do_ioctl+0x2b/0xc0
[<c0673be7>] do_page_fault+0x1d7/0x5d0
[<c0487a9e>] vfs_ioctl+0x22e/0x2b0
[<c0487b5d>] sys_ioctl+0x3d/0x70
[<c04041ca>] syscall_call+0x7/0xb
[<c0670000>] schedule+0x920/0x1180
=======================
Code: f9 c7 44 24 0c 00 00 00 00 c7 44 24 14 a0 73 43 c0 e8 35 ff ff ff 8b 5c 24 20 8b 74 24 24 8b 7c 24 28 83 c4 2c c3 00 00 00 00 00 <f0> ff 08 79 05 e8 36 01 00 00 c3 90 8d 74 26 00 f0 ff 00 7f 05
EIP: [<c06711e0>] mutex_lock+0x0/0x10 SS:ESP 0068:ce967dbc
I had this situation yesterday as well, although I didn't check dmesg but used the functional console to reboot computer. However boot down hanged and I had to visit my ISP, which luckily is onlo 150 meters away  and reboot manually twice before I got it up again. It turned out it hang on firewall when boot down, and then on reset there were a lock firewall couldn't handle and I had to boot backup kernel once before I could boot openvz kernel again.
I know there is nothing further to do fixing 2.6.22, but if the above possibly give some info on what I can do to get around it I would be gratful. I am not a C programmer although I understand to read some C code, but knows very little about kernel programing and less about asm. I understand the above as therer is some conflict and that it possibly have to do with SMP and my intel core 2 duo E6750 CPU. Possibly this can be fixed by reconfig the kernel although I am not happy if I have to leave one of my cores out of duty.
Now I think I have to pay my ISP another visit as well
EDIT:
I thought tis info may be useful as well
merc ~ # ps axl | grep D
F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND
4 0 23955 15014 21 0 1788 772 rwsem_ D+ pts/1 0:00 vzctl start 102
0 0 23964 2828 18 0 7108 1776 - D ? 0:00 smtpd -n smtp -t inet -u -o cleanup_service_name pre-cleanup
4 0 23992 2587 20 0 3984 1216 - Ds ? 0:00 /usr/sbin/sshd -R
0 0 24777 21934 25 0 1644 504 - D ? 0:00 /sbin/ifconfig -a
0 0 24888 5551 18 0 1768 608 pipe_w S+ pts/0 0:00 grep --colour=auto D
Kernel 2.6.32-125.3
vzctl 4.9.4
Gentoo Linux x64
[Updated on: Fri, 11 January 2008 11:47] Report message to a moderator |
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
