OpenVZ Forum - RDF feed
type: channel
items: *SOLVED* VE: 102: failed to start with err=-17
items: Re: VE: 102: failed to start with err=-17
items: I am sooo happy!

*SOLVED* VE: 102: failed to start with err=-17
type: item
description: 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 v…
creator: yettyn
date: 2008-01-10T09:52:45-00:00

Re: VE: 102: failed to start with err=-17
type: item
description: include/asm-generic/errno-base.h ... #define EEXIST 17 /* File exists */ As far as I see VE cannot register some network device. Do you want to use some additional network device inside VE? If you do not tried to add something unusual -- please tell us what the kernel you use. thank you, Vasily Averin
creator: vaverin
date: 2008-01-11T07:13:36-00:00

Re: VE: 102: failed to start with err=-17
type: item
description: 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
creator: yettyn
date: 2008-01-11T09:29:28-00:00

Re: VE: 102: failed to start with err=-17
type: item
description: 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: 239…
creator: yettyn
date: 2008-01-11T11:26:42-00:00

Re: VE: 102: failed to start with err=-17
type: item
description: Unfortunately our 2.6.20/22/24 kernels are not stable now. I would recommend you to check rhel5-based 2.6.18 kernel. IMHO last ones use libata drivers and have sd-like devices. Also you can try to use debian-based kernels provided by Thorsten Schifferdecker aka crux@ http://debian.systs.org/debian thank you, Vasily Averin
creator: vaverin
date: 2008-01-11T13:49:00-00:00

Re: VE: 102: failed to start with err=-17
type: item
description: 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
creator: yettyn
date: 2008-01-11T14:07:07-00:00

Re: VE: 102: failed to start with err=-17
type: item
description: 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 ?
creator: curx
date: 2008-01-11T15:23:24-00:00

Re: VE: 102: failed to start with err=-17
type: item
description: 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 # # …
creator: yettyn
date: 2008-01-11T17:13:20-00:00

Re: VE: 102: failed to start with err=-17
type: item
description: 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…
creator: yettyn
date: 2008-01-11T17:37:38-00:00

Re: VE: 102: failed to start with err=-17
type: item
description: I decided to yet another time get the 2.6.18 kernel configured to see and boot my SATA disk and guess what I did it! The trick was to select some options in SCSI were I found an option for SATA in the low-level drivers. But then I also had to select the depreciated sata option in in the IDE config section. So now I can boot this kernel which is a big step forward... however... Now it refuses to see my built in NIC RTL-8110SC/8169SC, well it show up in lspci but it doesn't bother about r8169.ko driver, although I load it with autoload.d/kernel-2.6 it doesn't attach to the eth0 interface, it simply doesn't exists!
creator: yettyn
date: 2008-01-11T20:38:00-00:00

Re: VE: 102: failed to start with err=-17
type: item
description: 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?
creator: yettyn
date: 2008-01-11T21:20:58-00:00

Re: VE: 102: failed to start with err=-17
type: item
description: 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?
creator: yettyn
date: 2008-01-12T01:07:03-00:00

I am sooo happy!
type: item
description: 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.
creator: yettyn
date: 2008-01-12T14:09:10-00:00