OpenVZ Forum


Home » International » Russian » Проблема при выключении VE с проброшенным netdev
Проблема при выключении VE с проброшенным netdev [message #48046] Wed, 26 September 2012 10:04 Go to next message
pavelk
Messages: 2
Registered: September 2012
Junior Member
From: 195.209.96*
Помогите понять, это баг или я что-то не понял.
Есть HN:
CentOS release 6.3 (Final) ядро с OVZ 2.6.32-042stab061.2

Создаю VE из шаблона centos-5-x86
Создаю в нем один veth интерфейс, потом пробрасываю еще физический интерфейс eth3
vzctl set 10209 --netdev_add eth3 --save

конфигурационный файл:
cat /etc/vz/conf/10209.conf
# RAM
PHYSPAGES="0:131072"
# Swap
SWAPPAGES="0:131072"
# Disk quota parameters (in form of softlimit:hardlimit)
DISKSPACE="10485760:10485760"
DISKINODES="200000:220000"
QUOTATIME="0"
# CPU fair scheduler parameter
CPUUNITS="5000"
HOSTNAME="rec"
VE_ROOT="/vz/root/$VEID"
VE_PRIVATE="/vz/private/$VEID"
OSTEMPLATE="centos-5-x86"
ORIGIN_SAMPLE="vswap-m512"
SHMPAGES="131072"
NUMPROC="1024"
NUMTCPSOCK="1024"
TCPSNDBUF="1048576:2097152"
TCPRCVBUF="1048576:2097152"
NUMOTHERSOCK="1024"
NUMFILE="4096"
CPULIMIT="60"
CPUS="1"
NETDEV="eth3"
ONBOOT="yes"
NETIF="ifname=eth0,bridge=br555,mac=00:18:51:CF:87:DF,host_ifname=veth10209.0,host_mac=00:18:51:A8:0D:90"
CONFIG_CUSTOMIZED="yes"
VZHOSTBR="br555
"

Настраиваю сеть в VE

Далее:
# vzctl start 10209
Starting container ...
Container is mounted
Setting CPU limit: 60
Setting CPU units: 5000
Setting CPUs: 1
Configure veth devices: veth10209.0
Adding interface veth10209.0 to bridge br555 on CT0 for CT10209
Container start in progress...
# vzctl exec 10209 ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: venet0: <BROADCAST,POINTOPOINT,NOARP> mtu 1500 qdisc noop
    link/void
5: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq qlen 1000
    link/ether 00:1b:21:8c:bf:07 brd ff:ff:ff:ff:ff:ff
    inet 192.168.199.126/30 brd 192.168.199.127 scope global eth3
    inet6 fe80::21b:21ff:fe8c:bf07/64 scope link
       valid_lft forever preferred_lft forever
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
    link/ether 00:18:51:cf:87:df brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.209/24 brd 10.24.10.255 scope global eth0
    inet6 fe80::218:51ff:fecf:87df/64 scope link
       valid_lft forever preferred_lft forever
#vzctl stop 10209
Stopping container ...
Container was stopped
Container is unmounted
#


В логе вижу следующее:

Sep 26 09:46:46 r24p-vm2 kernel: [16239.599502] CT: 10209: started
Sep 26 09:46:46 r24p-vm2 kernel: [16239.840967] device veth10209.0 entered promiscuous mode
Sep 26 09:46:46 r24p-vm2 kernel: [16239.841055] br555: port 3(veth10209.0) entering forwarding state
Sep 26 09:46:49 r24p-vm2 kernel: [16242.700475] ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep 26 09:46:49 r24p-vm2 kernel: [16242.700480] 8021q: adding VLAN 0 to HW filter on device eth3
Sep 26 09:46:51 r24p-vm2 kernel: [16244.202500] igb: eth3 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX
Sep 26 09:46:51 r24p-vm2 kernel: [16244.202759] ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready
Sep 26 09:48:35 r24p-vm2 kernel: [16347.873431] proc: unrecognized mount option "relatime" or missing value
Sep 26 09:48:37 r24p-vm2 kernel: [16349.896409] br555: port 3(veth10209.0) entering disabled state
Sep 26 09:48:37 r24p-vm2 kernel: [16349.899123] device veth10209.0 left promiscuous mode
Sep 26 09:48:37 r24p-vm2 kernel: [16349.899135] br555: port 3(veth10209.0) entering disabled state
Sep 26 09:48:37 r24p-vm2 kernel: [16349.911028] Can't delete virtual device 0000:0b:00.1 in case it is not present in VE.
Sep 26 09:48:37 r24p-vm2 kernel: [16349.911146] ------------[ cut here ]------------
Sep 26 09:48:37 r24p-vm2 kernel: [16349.911156] WARNING: at net/core/dev.c:6303 __dev_change_net_namespace+0x153/0x340() (Tainted: G        W  ---------------   )
Sep 26 09:48:37 r24p-vm2 kernel: [16349.911161] Hardware name: ProLiant DL380 G5
Sep 26 09:48:37 r24p-vm2 kernel: [16349.911164] Modules linked in: iptable_nat vzethdev pio_nfs pio_direct pfmt_raw pfmt_ploop1 ploop simfs vzrst nf_nat vzcpt nfs lockd fscache nfs_acl auth_rpcgss sunrpc vzdquota ip6table_mangle xt_length xt_hl xt_tcpmss xt_TCPMSS iptable_mangle xt_multiport xt_limit xt_dscp vzevent p4_clockmod bridge vznetdev vzmon vzdev bonding 8021q garp stp llc ipt_REJECT nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter ip_tables ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables ipv6 igb dca hpwdt ipmi_si ipmi_msghandler hpilo bnx2 microcode sg iTCO_wdt iTCO_vendor_support i5000_edac edac_core i5k_amb ext4 mbcache jbd2 sr_mod cdrom hpsa cciss pata_acpi ata_generic ata_piix radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core dm_mirror dm_region_hash dm_log dm_mod [last unloaded: mperf]
Sep 26 09:48:37 vm2 kernel: [16349.911244] Pid: 15, comm: netns veid: 0 Tainted: G        W  ---------------    2.6.32-042stab061.2 #1
Sep 26 09:48:37 vm2 kernel: [16349.911249] Call Trace:
Sep 26 09:48:37 vm2 kernel: [16349.911256]  [<c04583d1>] ? warn_slowpath_common+0x81/0xc0
Sep 26 09:48:37 vm2 kernel: [16349.911261]  [<c0794ad3>] ? __dev_change_net_namespace+0x153/0x340
Sep 26 09:48:37 vm2 kernel: [16349.911265]  [<c0794ad3>] ? __dev_change_net_namespace+0x153/0x340
Sep 26 09:48:37 vm2 kernel: [16349.911270]  [<c045842b>] ? warn_slowpath_null+0x1b/0x20
Sep 26 09:48:37 vm2 kernel: [16349.911275]  [<c0794ad3>] ? __dev_change_net_namespace+0x153/0x340
Sep 26 09:48:37 vm2 kernel: [16349.911280]  [<c0794cd9>] ? dev_change_net_namespace+0x19/0x20
Sep 26 09:48:37 vm2 kernel: [16349.911284]  [<c0794d85>] ? default_device_exit+0xa5/0xd0
Sep 26 09:48:37 vm2 kernel: [16349.911291]  [<c078e9d9>] ? ops_exit_list+0x49/0x90
Sep 26 09:48:37 vm2 kernel: [16349.911295]  [<c078ec40>] ? cleanup_net+0x0/0x180
Sep 26 09:48:37 vm2 kernel: [16349.911299]  [<c078ed11>] ? cleanup_net+0xd1/0x180
Sep 26 09:48:37 vm2 kernel: [16349.911305]  [<c0475fb3>] ? worker_thread+0x133/0x250
Sep 26 09:48:37 vm2 kernel: [16349.911310]  [<c047b350>] ? autoremove_wake_function+0x0/0x40
Sep 26 09:48:37 vm2 kernel: [16349.911315]  [<c0475e80>] ? worker_thread+0x0/0x250
Sep 26 09:48:37 vm2 kernel: [16349.911319]  [<c047af84>] ? kthread+0x74/0x80
Sep 26 09:48:37 vm2 kernel: [16349.911323]  [<c047af10>] ? kthread+0x0/0x80
Sep 26 09:48:37 vm2 kernel: [16349.911328]  [<c040a07f>] ? kernel_thread_helper+0x7/0x10
Sep 26 09:48:37 vm2 kernel: [16349.911332] ---[ end trace dcdd52c54ebcd431 ]---
Sep 26 09:48:37 vm2 kernel: [16349.940385] CT: 10209: stopped
Sep 26 09:48:37 vm2 kernel: [16350.037381] ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep 26 09:48:37 vm2 kernel: [16350.037386] 8021q: adding VLAN 0 to HW filter on device eth3
Sep 26 09:48:38 vm2 abrtd: Directory 'oops-2012-09-26-09:48:38-1868-0' creation detected
Sep 26 09:48:38 vm2 abrt-dump-oops: Reported 1 kernel oopses to Abrt
Sep 26 09:48:38 vm2 abrtd: Can't open file '/var/spool/abrt/oops-2012-09-26-09:48:38-1868-0/uid': Нет такого файла или каталога
Sep 26 09:48:38 vm2 kernel: [16351.552511] igb: eth3 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX
Sep 26 09:48:38 vm2 kernel: [16351.552757] ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready
Sep 26 09:48:42 vm2 abrtd: Отправляется сообщение...
Sep 26 09:48:42 vm2 abrtd: Сообщение отправлено на адрес root@localhost


Что это за "Can't delete virtual device 0000:0b:00.1 in case it is not present in VE."?
без проброшенного eth3 все работает
Re: Проблема при выключении VE с проброшенным netdev [message #48410 is a reply to message #48046] Tue, 16 October 2012 15:11 Go to previous messageGo to next message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member

From: *sw.ru
возможно, эта проблема починилась в 042stab062.22
http://wiki.openvz.org/Download/kernel/rhel6-testing/042stab 062.22

попробуйте его


Kir Kolyshkin
http://static.openvz.org/userbars/openvz-developer.png
Re: Проблема при выключении VE с проброшенным netdev [message #48559 is a reply to message #48046] Mon, 22 October 2012 14:05 Go to previous messageGo to next message
ravx is currently offline  ravx
Messages: 1
Registered: October 2012
Junior Member
From: 195.112.113*
Аналогичная проблема. Не решается и с ядром 042stab062.22
Re: Проблема при выключении VE с проброшенным netdev [message #48808 is a reply to message #48046] Fri, 07 December 2012 06:53 Go to previous message
pavelk
Messages: 2
Registered: September 2012
Junior Member
From: 195.209.96*
Для меня уже не сильно актуально, но как понимаю проблема не только у меня. Отписал в багзиллу: Bug 2457
Previous Topic: Проблема со свободным местом в CT
Next Topic: ploop кто-то использовал?
Goto Forum:
  


Current Time: Sat Sep 22 16:46:36 GMT 2018