| *SOLVED* VE: 102: failed to start with err=-17 [message #25883] |
Thu, 10 January 2008 09:52  |
yettyn
Messages: 31
Registered: January 2008
Location: Jihlava, CZ
|
Member |
|
|
What does err=-17 mean?
I can only start 1 VE, when I try to start further ones I get this error in dmesg together with some other output.
VE: 101: started
kobject_add failed for net with -EEXIST, don't try to register things with the same name in the same directory.
[<c0530b03>] kobject_shadow_add+0x113/0x1a0
[<c0530c71>] kobject_register+0x21/0x50
[<c0530e22>] kobject_kset_add_dir+0x52/0xa0
[<c05aac35>] device_add+0x75/0x4e0
[<c053076f>] kobject_get+0xf/0x20
[<c0603924>] register_netdevice+0x204/0x4b0
[<c0605279>] register_netdev+0x49/0x70
[<f8e8ba58>] real_env_create+0x918/0xb50 [vzmon]
[<f8e8c12d>] vzcalls_ioctl+0x49d/0x4d0 [vzmon]
[<f894517b>] vzctl_ioctl+0x5b/0x60 [vzdev]
[<f8e8bc90>] vzcalls_ioctl+0x0/0x4d0 [vzmon]
[<f8945120>] 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
=======================
kobject_kset_add_dir: kobject_register error: -17
kobject_add failed for lo with -EEXIST, don't try to register things with the same name in the same directory.
[<c0530b03>] kobject_shadow_add+0x113/0x1a0
[<c0530d47>] kobject_set_name+0x37/0xc0
[<c05aac70>] device_add+0xb0/0x4e0
[<c053076f>] kobject_get+0xf/0x20
[<c0603924>] register_netdevice+0x204/0x4b0
[<c0605279>] register_netdev+0x49/0x70
[<f8e8ba58>] real_env_create+0x918/0xb50 [vzmon]
[<f8e8c12d>] vzcalls_ioctl+0x49d/0x4d0 [vzmon]
[<f894517b>] vzctl_ioctl+0x5b/0x60 [vzdev]
[<f8e8bc90>] vzcalls_ioctl+0x0/0x4d0 [vzmon]
[<f8945120>] 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
=======================
VE: 102: failed to start with err=-17
and in vzctl.log
2008-01-10T10:36:14+0100 vzctl : Setting CPU units: 20000
2008-01-10T10:36:14+0100 vzctl : WARNING: Settings were not saved and will be resetted to original values on next start (use --save flag)
2008-01-10T10:36:14+0100 vzctl : VE 101 : Starting VE ...
2008-01-10T10:36:14+0100 vzctl : VE 101 : Mounting root: /vz/root/101 /vz/private/101
2008-01-10T10:36:14+0100 vzctl : VE 101 : VE is mounted
2008-01-10T10:36:14+0100 vzctl : VE 101 : Adding IP address(es): 192.168.0.101
2008-01-10T10:36:14+0100 vzctl : VE 101 : Running: /usr/lib/vzctl/scripts/vps-net_add
2008-01-10T10:36:14+0100 vzctl : VE 101 : Running VE script: /etc/vz/dists/scripts/gentoo-add_ip.sh
2008-01-10T10:36:14+0100 vzctl : VE 101 : Setting CPU units: 12705
2008-01-10T10:36:14+0100 vzctl : VE 101 : Configure meminfo: 298782
2008-01-10T10:36:14+0100 vzctl : VE 101 : Set hostname: ns.astrocalc.net
2008-01-10T10:36:14+0100 vzctl : VE 101 : Running VE script: /etc/vz/dists/scripts/gentoo-set_hostname.sh
2008-01-10T10:36:14+0100 vzctl : VE 101 : Running VE script: /etc/vz/dists/scripts/set_dns.sh
2008-01-10T10:36:14+0100 vzctl : VE 101 : File resolv.conf was modified
2008-01-10T10:36:14+0100 vzctl : VE 101 : VE start in progress...
2008-01-10T10:36:49+0100 vzctl : VE 102 : Starting VE ...
2008-01-10T10:36:49+0100 vzctl : VE 102 : Mounting root: /vz/root/102 /vz/private/102
2008-01-10T10:36:49+0100 vzctl : VE 102 : VE is mounted
2008-01-10T10:36:49+0100 vzctl : VE 102 : VE start failed
2008-01-10T10:36:49+0100 vzctl : VE 102 : Running: /usr/sbin/vzquota stat 102 -f
2008-01-10T10:36:49+0100 vzctl : VE 102 : VE is unmounted
2008-01-10T10:40:01+0100 venetclean : VE 102 : VE died, clear IPs:
I have tried so set DISK_QUOTA=no to no avail.
/Joakim
Kernel 2.6.32-125.3
vzctl 4.9.4
Gentoo Linux x64
[Updated on: Sat, 12 January 2008 14:09] Report message to a moderator |
|
|
|
|
|
| Re: VE: 102: failed to start with err=-17 [message #25925 is a reply to message #25883] |
Fri, 11 January 2008 09:29  |
yettyn
Messages: 31
Registered: January 2008
Location: Jihlava, CZ
|
Member |
|
|
As far as I am aware no extra network device is used/added, and I have the same setup working on another box with much less/older hw spec. I am using kernel 2.6.22-005.1 on gentoo, and I have come to understand now that kernel has no future - but using 2.6.18-stable is not really an option due to HW complications.
The problem I had on 2.6.18 is with recognition of my SATA disks as sda, I can just make them be seen as hda and running at 33Mhz bus speed - which is not acceptable. I will give 2.6.22 some more investigation on the network part, maybe there is something not so obvious that I don't see. Also a diff to the working test box apart from HW is this one is running a Shorewall 4.0.7 firewall so there might be something there as well?
If not anything else work I would have to try getting a 2.6.24 kernel running from git. I can't find any patches there to apply on vanilla rc, just prepatched source tree I think, is this correct?
/Joakim
Kernel 2.6.32-125.3
vzctl 4.9.4
Gentoo Linux x64
|
|
|
|
| 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 |
|
|
|
|
|
| Re: VE: 102: failed to start with err=-17 [message #25940 is a reply to message #25938] |
Fri, 11 January 2008 14:07 |
yettyn
Messages: 31
Registered: January 2008
Location: Jihlava, CZ
|
Member |
|
|
you think any of these will run on Gentoo?
I have tried again with the Gentoo stable 2.6.18 kernel but I cannot make it deal with my sata.
As for 2.6.24 I am prepared to test it, even if it's unstable, in case I cannot get 2.6.22 to work. I am trying now with some alter in kernel config, noticed some diffs commpared to my test box where 2.6.22 seem to work. Proplem for me now is I need to take decision in less then 2 hours as I then can't get on place access untill monday in case it hangs, and with testing it's fair chance it does so... If my new compile doesn't work I probably will take home the server for further work although it mean an approx 48h downtime.
I simply must have this working.
/Joakim
Kernel 2.6.32-125.3
vzctl 4.9.4
Gentoo Linux x64
|
|
|
|
|
|
| Re: VE: 102: failed to start with err=-17 [message #25944 is a reply to message #25942] |
Fri, 11 January 2008 17:13 |
yettyn
Messages: 31
Registered: January 2008
Location: Jihlava, CZ
|
Member |
|
|
| curx wrote on Fri, 11 January 2008 16:23 |
Hi Joakim,
please provide more info about:
* which kind of controller is used (output from lspci or lshw)
* used kernel config, and is this kernel from git.openvz.org or from a openvz-enabled g2 kernel-source ?
|
Hi curx,
thanks for jumping in, here is the info.
merc ~ # lspci
00:00.0 Host bridge: Intel Corporation DRAM Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corporation Integrated Graphics Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01)
00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family) SATA IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
01:05.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8110SC/8169SC Gigabit Ethernet (rev 10)
source for the kernel is vanilla-2.6.22 patched with patch-ovz005.1-combined.gz from ovz ftp, I also used the .config file from openvz instead of the gentoo supplied one. Reconfigured for my CPU and removed some things I am pretty use I don't use. There is of course a chance I accidently removed something needed. Here is my kernel config
merc linux # cat /usr/src/linux/.config
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.22-ovz005
# Fri Jan 11 17:57:30 2008
#
CONFIG_X86_32=y
CONFIG_GENERIC_TIME=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_QUICKLIST=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_IPC_NS=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
CONFIG_UTS_NS=y
CONFIG_USER_NS=y
# CONFIG_AUDIT is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=17
# CONFIG_CPUSETS is not set
# CONFIG_SYSFS_DEPRECATED is not set
CONFIG_RELAY=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_EXTRA_PASS=y
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLUB_DEBUG=y
# CONFIG_SLAB is not set
CONFIG_SLUB=y
# CONFIG_SLOB is not set
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_MODVERSIONS=y
CONFIG_MODULE_SRCVERSION_ALL=y
CONFIG_KMOD=y
CONFIG_STOP_MACHINE=y
#
# Block layer
#
CONFIG_BLOCK=y
# CONFIG_LBD is not set
CONFIG_BLK_DEV_IO_TRACE=y
# CONFIG_LSF is not set
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
#
# Processor type and features
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_SMP=y
# CONFIG_X86_PC is not set
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
CONFIG_X86_GENERICARCH=y
# CONFIG_X86_ES7000 is not set
# CONFIG_PARAVIRT is not set
CONFIG_X86_CYCLONE_TIMER=y
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
CONFIG_MCORE2=y
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_MVIAC7 is not set
CONFIG_X86_GENERIC=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_X86_XADD=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_TSC=y
CONFIG_X86_MINIMUM_CPU_MODEL=4
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_NR_CPUS=8
CONFIG_SCHED_VCPU=y
CONFIG_FAIRSCHED=y
# CONFIG_SCHED_SMT is not set
CONFIG_SCHED_MC=y
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
CONFIG_PREEMPT_BKL=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_NMI_WATCHDOG=y
CONFIG_X86_MCE=y
# CONFIG_X86_MCE_NONFATAL is not set
# CONFIG_X86_MCE_P4THERMAL is not set
CONFIG_VM86=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_X86_REBOOTFIXUPS is not set
CONFIG_MICROCODE=m
CONFIG_MICROCODE_OLD_INTERFACE=y
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m
#
# Firmware Drivers
#
CONFIG_EDD=m
CONFIG_DELL_RBU=m
CONFIG_DCDBAS=m
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_HIGHMEM=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
# CONFIG_SPARSEMEM_STATIC is not set
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_RESOURCES_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_NR_QUICK=1
CONFIG_HIGHPTE=y
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_IRQBALANCE=y
# CONFIG_SECCOMP is not set
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
CONFIG_HZ_300=y
# CONFIG_HZ_1000 is not set
CONFIG_HZ=300
CONFIG_KEXEC=y
CONFIG_CRASH_DUMP=y
CONFIG_PHYSICAL_START=0x100000
CONFIG_RELOCATABLE=y
CONFIG_PHYSICAL_ALIGN=0x400000
# CONFIG_COMPAT_VDSO is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_PM_LEGACY is not set
# CONFIG_PM_DEBUG is not set
# CONFIG_PM_SYSFS_DEPRECATED is not set
# CONFIG_SOFTWARE_SUSPEND is not set
#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
# CONFIG_ACPI_PROCFS is not set
# CONFIG_ACPI_AC is not set
# CONFIG_ACPI_BATTERY is not set
CONFIG_ACPI_BUTTON=y
# CONFIG_ACPI_VIDEO is not set
CONFIG_ACPI_FAN=y
# CONFIG_ACPI_DOCK is not set
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
# CONFIG_ACPI_CONTAINER is not set
# CONFIG_ACPI_SBS is not set
# CONFIG_APM is not set
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_STAT=m
CONFIG_CPU_FREQ_STAT_DETAILS=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=m
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m
#
# CPUFreq processor drivers
#
CONFIG_X86_ACPI_CPUFREQ=y
# CONFIG_X86_POWERNOW_K6 is not set
# CONFIG_X86_POWERNOW_K7 is not set
# CONFIG_X86_POWERNOW_K8 is not set
# CONFIG_X86_GX_SUSPMOD is not set
# CONFIG_X86_SPEEDSTEP_CENTRINO is not set
# CONFIG_X86_SPEEDSTEP_ICH is not set
# CONFIG_X86_SPEEDSTEP_SMI is not set
CONFIG_X86_P4_CLOCKMOD=m
# CONFIG_X86_CPUFREQ_NFORCE2 is not set
# CONFIG_X86_LONGRUN is not set
# CONFIG_X86_LONGHAUL is not set
# CONFIG_X86_E_POWERSAVER is not set
#
# shared options
#
# CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set
CONFIG_X86_SPEEDSTEP_LIB=m
#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCIEPORTBUS=y
CONFIG_HOTPLUG_PCI_PCIE=m
# CONFIG_HOTPLUG_PCI_PCIE_POLL_EVENT_MODE is not set
CONFIG_PCIEAER=y
CONFIG_ARCH_SUPPORTS_MSI=y
# CONFIG_PCI_MSI is not set
CONFIG_HT_IRQ=y
CONFIG_ISA_DMA_API=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
CONFIG_K8_NB=y
#
# PCCARD (PCMCIA/CardBus) support
#
CONFIG_PCCARD=y
# CONFIG_PCMCIA_DEBUG is not set
CONFIG_PCMCIA=y
CONFIG_PCMCIA_LOAD_CIS=y
CONFIG_PCMCIA_IOCTL=y
CONFIG_CARDBUS=y
#
# PC-card bridges
#
CONFIG_YENTA=y
CONFIG_YENTA_O2=y
CONFIG_YENTA_RICOH=y
CONFIG_YENTA_TI=y
CONFIG_YENTA_ENE_TUNE=y
CONFIG_YENTA_TOSHIBA=y
CONFIG_PD6729=m
# CONFIG_I82092 is not set
CONFIG_PCCARD_NONSTATIC=y
CONFIG_HOTPLUG_PCI=y
CONFIG_HOTPLUG_PCI_FAKE=m
CONFIG_HOTPLUG_PCI_COMPAQ=m
# CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM is not set
# CONFIG_
Kernel 2.6.32-125.3
vzctl 4.9.4
Gentoo Linux x64
|
|
|
|
| Re: VE: 102: failed to start with err=-17 [message #25945 is a reply to message #25883] |
Fri, 11 January 2008 17:37 |
yettyn
Messages: 31
Registered: January 2008
Location: Jihlava, CZ
|
Member |
|
|
This might be of importance as well, even when just VE101 is started only (it starts ok) the EEXIST message is spitted out in dmesg
VE: 101: stopped
kobject_add failed for net with -EEXIST, don't try to register things with the same name in the same directory.
[<c052f593>] kobject_shadow_add+0x113/0x1a0
[<c052f701>] kobject_register+0x21/0x50
[<c052f8b2>] kobject_kset_add_dir+0x52/0xa0
[<c05a8755>] device_add+0x75/0x4e0
[<c0442383>] ub_slab_charge+0x53/0x80
[<c052f1ff>] kobject_get+0xf/0x20
[<c0601464>] register_netdevice+0x204/0x4b0
[<c0602db9>] register_netdev+0x49/0x70
[<f8e8aa58>] real_env_create+0x918/0xb50 [vzmon]
[<f8e8b12d>] vzcalls_ioctl+0x49d/0x4d0 [vzmon]
[<c043ce14>] getnstimeofday+0x34/0xf0
[<f896917b>] vzctl_ioctl+0x5b/0x60 [vzdev]
[<f8e8ac90>] vzcalls_ioctl+0x0/0x4d0 [vzmon]
[<f8969120>] vzctl_ioctl+0x0/0x60 [vzdev]
[<c048628b>] do_ioctl+0x2b/0xc0
[<c06716e7>] do_page_fault+0x1d7/0x5d0
[<c048654e>] vfs_ioctl+0x22e/0x2b0
[<c048660d>] sys_ioctl+0x3d/0x70
[<c04051ca>] syscall_call+0x7/0xb
[<c0660000>] __xfrm_find_acq_byseq+0x10/0x60
=======================
kobject_kset_add_dir: kobject_register error: -17
kobject_add failed for net with -EEXIST, don't try to register things with the same name in the same directory.
[<c052f593>] kobject_shadow_add+0x113/0x1a0
[<c052f701>] kobject_register+0x21/0x50
[<c052f8b2>] kobject_kset_add_dir+0x52/0xa0
[<c05a8755>] device_add+0x75/0x4e0
[<c052f1ff>] kobject_get+0xf/0x20
[<c0601464>] register_netdevice+0x204/0x4b0
[<c04602f9>] __kzalloc+0x19/0x50
[<c0602db9>] register_netdev+0x49/0x70
[<f8f99791>] venet_dev_start+0x41/0x80 [vznetdev]
[<f8f99129>] veip_start+0x59/0x80 [vznetdev]
[<f8f9980c>] venet_start+0x3c/0x50 [vznetdev]
[<c04482f6>] ve_hook_iterate_init+0x76/0xf0
[<f8e8abcb>] real_env_create+0xa8b/0xb50 [vzmon]
[<f8e8b12d>] vzcalls_ioctl+0x49d/0x4d0 [vzmon]
[<c043ce14>] getnstimeofday+0x34/0xf0
[<f896917b>] vzctl_ioctl+0x5b/0x60 [vzdev]
[<f8e8ac90>] vzcalls_ioctl+0x0/0x4d0 [vzmon]
[<f8969120>] vzctl_ioctl+0x0/0x60 [vzdev]
[<c048628b>] do_ioctl+0x2b/0xc0
[<c06716e7>] do_page_fault+0x1d7/0x5d0
[<c048654e>] vfs_ioctl+0x22e/0x2b0
[<c048660d>] sys_ioctl+0x3d/0x70
[<c04051ca>] syscall_call+0x7/0xb
[<c0660000>] __xfrm_find_acq_byseq+0x10/0x60
=======================
kobject_kset_add_dir: kobject_register error: -17
VE: 101: started
and I can access internet after
#vzctrl enter 101
Kernel 2.6.32-125.3
vzctl 4.9.4
Gentoo Linux x64
|
|
|
|
|
|
| Re: VE: 102: failed to start with err=-17 [message #25948 is a reply to message #25883] |
Fri, 11 January 2008 21:20 |
yettyn
Messages: 31
Registered: January 2008
Location: Jihlava, CZ
|
Member |
|
|
hmm something must be really wrong as not even if I plugin a 3Com905C and load the driver eth0 exist, only lo - really wired. lspci sees it though so hw must be functional and I been over the config and can't see anything missing or that shouldn't be there. Anyone have an idea what can cause such thing?
Kernel 2.6.32-125.3
vzctl 4.9.4
Gentoo Linux x64
|
|
|
|
| Re: VE: 102: failed to start with err=-17 [message #25950 is a reply to message #25883] |
Sat, 12 January 2008 01:07 |
yettyn
Messages: 31
Registered: January 2008
Location: Jihlava, CZ
|
Member |
|
|
Well it appear 2.6.18 kernel is a dead end for me. I have now tried with a vanilla-2.6.18 and it show same problem - it doesn't even try to load my nic's so there must be some kind of hw problem here.
So not sure which road to go now as 2.6.22 also seem to be a dead road due to being a frosen ovz tree, remains 2.6.24 but how unstable is it?
Kernel 2.6.32-125.3
vzctl 4.9.4
Gentoo Linux x64
|
|
|
|
| I am sooo happy! [message #25958 is a reply to message #25950] |
Sat, 12 January 2008 14:09 |
yettyn
Messages: 31
Registered: January 2008
Location: Jihlava, CZ
|
Member |
|
|
Yes! I got it working with the 2.6.22 kernel. I am not sure what I have done differently but it doesn't matter as I am sooo happy now!
I was on the edge to give up as not even vanilla-2.6.18 would load and use my nic drivers and all the dispersing attempts to get 2.6.22-005.1 working properly. But I thought I would give it a last chance. So I brought home the box from my ISP over the weekend, cleaned out the old kernels and started fresh anew with 2.6.22, and made sure to use ovz config file, made my necessary changes for hardware and removed stuff I definitively not need like for Notebooks, Compac, Dell etc. etc. as the config loads pretty much everything, although mostly as modules. Recompiled kernel and wops! now it works.
Yes, I did one other thing, I plugged in another nic card although I haven't decided if to use it or not yet - but I will certainly leave it in as everything work as is now! Finally I can start to rearrange the box.
Kernel 2.6.32-125.3
vzctl 4.9.4
Gentoo Linux x64
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
