Xen отключение пара виртуальной сетевой карты после segfault
Форум — Admin
Вводные данные HVX3, HVX4 (физические хосты с гипервизором):
Operating System: SUSE Linux Enterprise Server 12 SP1
CPE OS Name: cpe:/o:suse:sles:12:sp1
Kernel: Linux 3.12.49-11-xen
Architecture: x86-64
Xen version 4.5.1_12-2 (gcc (SUSE Linux) 4.8.5) debug=n
xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
MSK-HVX04:/var/log/libvirt # virsh version
Compiled against library: libvirt 1.2.18
Using library: libvirt 1.2.18
Using API: Xen 1.2.18
Running hypervisor: Xen 4.5.0
На серверах работают 4 виртуальные машины:
MSK-HVX04:/etc/xen/scripts # xl list
|Name | ID Mem | VCPUs | State Time(s)|
|----------------------|:-------------------|:----------------:|
|Domain-0 |0 5525 | 40 | r----- 452515.7 |
|MSA-AD02 |7 7936 | 8 | -b---- 51604.6 |
|MSA-ER04 |8 7936 | 2 | -b---- 189176.5 |
|MSA-EV04 |9 48896 | 16 | -b---- 906702.5 |
|MS-APP02 |10 42752 | 8 | r----- 82432.4|
MSK-HVX03:~ # xl list
|Name |ID Mem |VCPUs | State Time(s) |
|----------------------|:----------------|:------------------:|
|Domain-0 |0 5514 | 40 | r----- 303328.2 |
|MSA-AD01 | 4 7936 | 8 | -b---- 47634.3 |
|MSA-ER03 | 5 7936 | 2 | r----- 169682.1 |
|MSA-EV03 | 6 48896 | 16 | r----- 944605.8 |
|MS-APP01 |7 42752 | 8 | -b---- 38110.5 |
MSK-HVX03:/etc/sysconfig/network # brctl show
|bridge name| bridge id | STP enabled | interfaces|
|-----------|:-----------------------|:------------:|----------:|
| | | | bond0 |
|br0 | 8000.70106f4305b8 | no | |
| | | | vif4.0 |
| | | |vif4.0-emu |
| | | |vif5.0 |
| | | |vif5.0-emu |
| | | |vif6.0 |
| | | |vif6.0-emu |
| | | |vif7.0 |
| | | |vif7.0-emu |
MSK-HVX04:/var/log/libvirt # brctl show
|bridge name| bridge id | STP enabled |interfaces |
|-----------|:-----------------------|:-----------:|-----------:|
| | | | |
|br0 | 8000.70106f433478 | no | bond0 |
| | | |vif10.0 |
| | | |vif10.0-emu |
| | | |vif7.0 |
| | | |vif7.0-emu |
| | | |vif8.0 |
| | | |vif8.0-emu |
| | | |vif9.0 |
| | | |vif9.0-emu |
MSK-HVX03:cat ifcfg-br0
BOOTPROTO='static'
BRIDGE='yes'
BRIDGE_FORWARDDELAY='0'
BRIDGE_PORTS='bond0'
BRIDGE_STP='off'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR='1.1.43.13/16'
MTU=''
NETWORK=''
PREFIXLEN='16'
REMOTE_IPADDR=''
STARTMODE='auto'
NAME=''
MSK-HVX04:cat /etc/sysconfig/network/ifcfg-br0
BOOTPROTO='static'
BRIDGE='yes'
BRIDGE_FORWARDDELAY='0'
BRIDGE_PORTS='bond0'
BRIDGE_STP='off'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR='1.1.43.14/16'
MTU=''
NETWORK=''
PREFIXLEN='16'
REMOTE_IPADDR=''
STARTMODE='auto'
NAME=''
MSK-HVX04:/var/log/libvirt # lsmod | head -5
Module Size Used by
binfmt_misc 17468 1
tun 31262 8
ebtable_filter 12827 0
ebtables 35009 1 ebtable_filter
MSK-HVX03:/etc/sysconfig/network # lsmod | head -5
Module Size Used by
tun 31262 8
binfmt_misc 17468 1
ebtable_filter 12827 0
ebtables 35009 1 ebtable_filter
MS-APP02:~ # lsmod | head -5
Module Size Used by
fuse 95758 3
nfsd 309068 37
binfmt_misc 17468 1
nfsv3 43466 2
MS-APP01:~ # lsmod | head -5
Module Size Used by
st 44723 0
fuse 95758 3
binfmt_misc 17468 1
nfsv3 43466 2
Ошибка происходит с виртуальными сетевыми адаптерами машин на хосте HVX03-04:
MS-APP01 -Node 1 Cluster peacemaker + COROSYNC
MS-APP02 - Node 2 Cluster peacemaker + COROSYNC
На сервере HVX03 после ошибки segfault отключился, удалился и пересоздался виртуальный сетевой интерфейс виртуальной машины MS-APP01. Все ресурсы кластера были запущенны на сервре MSK-HVX04 в виртуальной машине MS-APP02. На виртуальной машине по прошествии 8 дней возникла такая же ошибка. После ошибки segfault отключился, удалился и пересоздался виртуальный сетевой интерфейс виртуальной машины MS-APP02
Детализация ошибки
На сервере HVX3
Successful vif-bridge remove for vif2.0-emu, bridge br0.
2022-02-05T10:54:27.177824+03:00 MSK-HVX03 kernel: [ 3661.182659] qemu-system-i38[5088]: segfault at 0 ip 00007f48c3fc7ff6 sp 00007ffdd3a43cf8 error 4 in libc-2.19.so[7f48c3f38000+19e000]
2022-02-05T10:54:27.190280+03:00 MSK-HVX03 avahi-daemon[11931]: Interface vif2.0-emu.IPv6 no longer relevant for mDNS.
2022-02-05T10:54:27.190911+03:00 MSK-HVX03 avahi-daemon[11931]: Leaving mDNS multicast group on interface vif2.0-emu.IPv6 with address fe80::fcff:ffff:feff:ffff.
2022-02-05T10:54:27.191477+03:00 MSK-HVX03 avahi-daemon[11931]: Withdrawing address record for fe80::fcff:ffff:feff:ffff on vif2.0-emu.
2022-02-05T10:54:27.192029+03:00 MSK-HVX03 avahi-daemon[11931]: Withdrawing workstation service for vif2.0-emu.
2022-02-05T10:54:27.193917+03:00 MSK-HVX03 kernel: [ 3661.197089] br0: port 3(vif2.0-emu) entered disabled state
2022-02-05T10:54:27.193940+03:00 MSK-HVX03 kernel: [ 3661.197608] device vif2.0-emu left promiscuous mode
2022-02-05T10:54:27.193945+03:00 MSK-HVX03 kernel: [ 3661.197642] br0: port 3(vif2.0-emu) entered disabled state
2022-02-05T11:00:30.922318+03:00 MSK-HVX03 libvirtd[12838]: this function is not supported by the connection driver: virConnectGetCPUModelNames
2022-02-05T11:00:31.986745+03:00 MSK-HVX03 libvirtd[12838]: this function is not supported by the connection driver: virDomainGetMetadata
2022-02-05T11:00:31.987565+03:00 MSK-HVX03 libvirtd[12838]: this function is not supported by the connection driver: virDomainMemoryStats
2022-02-05T11:00:32.019247+03:00 MSK-HVX03 libvirtd[12838]: this function is not supported by the connection driver: virDomainListAllSnapshots
2022-02-05T11:00:35.593142+03:00 MSK-HVX03 libvirtd[12838]: this function is not supported by the connection driver: virConnectGetDomainCapabilities
2022-02-05T11:02:42.321009+03:00 MSK-HVX03 libvirtd[12838]: this function is not supported by the connection driver: virConnectGetCPUModelNames
2022-02-05T11:02:42.769313+03:00 MSK-HVX03 libvirtd[12838]: this function is not supported by the connection driver: virDomainGetMetadata
2022-02-05T11:02:42.770978+03:00 MSK-HVX03 libvirtd[12838]: this function is not supported by the connection driver: virDomainMemoryStats
2022-02-05T11:02:42.798949+03:00 MSK-HVX03 libvirtd[12838]: this function is not supported by the connection driver: virDomainListAllSnapshots
2022-02-05T11:02:45.136335+03:00 MSK-HVX03 libvirtd[12838]: this function is not supported by the connection driver: virConnectGetDomainCapabilities
2022-02-05T11:03:09.113615+03:00 MSK-HVX03 libvirtd[12838]: End of file while reading data: Input/output error
2022-02-05T11:03:12.881423+03:00 MSK-HVX03 libvirtd[12838]: this function is not supported by the connection driver: virConnectGetCPUModelNames
2022-02-05T11:03:13.335905+03:00 MSK-HVX03 libvirtd[12838]: this function is not supported by the connection driver: virDomainGetMetadata
2022-02-05T11:03:13.336799+03:00 MSK-HVX03 libvirtd[12838]: this function is not supported by the connection driver: virDomainMemoryStats
2022-02-05T11:03:13.367980+03:00 MSK-HVX03 libvirtd[12838]: this function is not supported by the connection driver: virDomainListAllSnapshots
2022-02-05T11:03:15.436348+03:00 MSK-HVX03 libvirtd[12838]: this function is not supported by the connection driver: virConnectGetDomainCapabilities
2022-02-05T11:04:24.664784+03:00 MSK-HVX03 libvirtd[12838]: this function is not supported by the connection driver: virConnectGetCPUModelNames
2022-02-05T11:04:25.106333+03:00 MSK-HVX03 libvirtd[12838]: this function is not supported by the connection driver: virDomainGetMetadata
2022-02-05T11:04:25.107135+03:00 MSK-HVX03 libvirtd[12838]: this function is not supported by the connection driver: virDomainMemoryStats
2022-02-05T11:04:25.138921+03:00 MSK-HVX03 libvirtd[12838]: this function is not supported by the connection driver: virDomainListAllSnapshots
2022-02-05T11:04:34.912256+03:00 MSK-HVX03 libvirtd[12838]: this function is not supported by the connection driver: virConnectGetDomainCapabilities
2022-02-05T11:05:31.214325+03:00 MSK-HVX03 kernel: [ 4325.219260] br0: port 2(vif2.0) entered disabled state
2022-02-05T11:05:31.214352+03:00 MSK-HVX03 kernel: [ 4325.219734] device vif2.0 left promiscuous mode
2022-02-05T11:05:31.214358+03:00 MSK-HVX03 kernel: [ 4325.219772] br0: port 2(vif2.0) entered disabled state
2022-02-05T11:05:31.214611+03:00 MSK-HVX03 avahi-daemon[11931]: Interface vif2.0.IPv6 no longer relevant for mDNS.
2022-02-05T11:05:31.215095+03:00 MSK-HVX03 avahi-daemon[11931]: Leaving mDNS multicast group on interface vif2.0.IPv6 with address fe80::fcff:ffff:feff:ffff.
2022-02-05T11:05:31.215476+03:00 MSK-HVX03 avahi-daemon[11931]: Withdrawing address record for fe80::fcff:ffff:feff:ffff on vif2.0.
2022-02-05T11:05:31.215841+03:00 MSK-HVX03 avahi-daemon[11931]: Withdrawing workstation service for vif2.0.
2022-02-05T11:05:31.306481+03:00 MSK-HVX03 logger: /etc/xen/scripts/vif-bridge: offline type_if=vif XENBUS_PATH=backend/vif/2/0
2022-02-05T11:05:31.390050+03:00 MSK-HVX03 logger: /etc/xen/scripts/vif-bridge: brctl delif br0 vif2.0 failed
2022-02-05T11:05:31.414700+03:00 MSK-HVX03 logger: /etc/xen/scripts/vif-bridge: ifconfig vif2.0 down failed
2022-02-05T11:05:31.419938+03:00 MSK-HVX03 logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge offline for vif2.0, bridge br0.
2022-02-05T11:05:31.460123+03:00 MSK-HVX03 logger: /etc/xen/scripts/vif-bridge: remove type_if=tap XENBUS_PATH=backend/vif/2/0
2022-02-05T11:05:31.504989+03:00 MSK-HVX03 logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge remove for vif2.0-emu, bridge br0.
2022-02-05T11:05:43.102744+03:00 MSK-HVX03 logger: /etc/xen/scripts/vif-bridge: online type_if=vif XENBUS_PATH=backend/vif/3/0
2022-02-05T11:05:43.169839+03:00 MSK-HVX03 kernel: [ 4337.173089] device vif3.0 entered promiscuous mode
2022-02-05T11:05:43.173840+03:00 MSK-HVX03 kernel: [ 4337.176484] br0: port 2(vif3.0) entered forwarding state
2022-02-05T11:05:43.173865+03:00 MSK-HVX03 kernel: [ 4337.176504] br0: port 2(vif3.0) entered forwarding state
2022-02-05T11:05:43.175298+03:00 MSK-HVX03 logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge online for vif3.0, bridge br0.
2022-02-05T11:05:43.180259+03:00 MSK-HVX03 logger: /etc/xen/scripts/vif-bridge: Writing backend/vif/3/0/hotplug-status connected to xenstore.
2022-02-05T11:05:43.224042+03:00 MSK-HVX03 logger: /etc/xen/scripts/vif-bridge: add type_if=tap XENBUS_PATH=backend/vif/3/0
2022-02-05T11:05:43.287426+03:00 MSK-HVX03 kernel: [ 4337.290844] device vif3.0-emu entered promiscuous mode
2022-02-05T11:05:43.289808+03:00 MSK-HVX03 kernel: [ 4337.293929] br0: port 3(vif3.0-emu) entered forwarding state
2022-02-05T11:05:43.289827+03:00 MSK-HVX03 kernel: [ 4337.293947] br0: port 3(vif3.0-emu) entered forwarding state
2022-02-05T11:05:43.292618+03:00 MSK-HVX03 logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge add for vif3.0-emu, bridge br0.
2022-02-05T11:05:44.730090+03:00 MSK-HVX03 avahi-daemon[11931]: Joining mDNS multicast group on interface vif3.0-emu.IPv6 with address fe80::fcff:ffff:feff:ffff.
2022-02-05T11:05:44.730732+03:00 MSK-HVX03 avahi-daemon[11931]: New relevant interface vif3.0-emu.IPv6 for mDNS.
2022-02-05T11:05:44.731134+03:00 MSK-HVX03 avahi-daemon[11931]: Registering new address record for fe80::fcff:ffff:feff:ffff on vif3.0-emu.*.
2022-02-05T11:05:44.822337+03:00 MSK-HVX03 avahi-daemon[11931]: Joining mDNS multicast group on interface vif3.0.IPv6 with address fe80::fcff:ffff:feff:ffff.
2022-02-05T11:05:44.822822+03:00 MSK-HVX03 avahi-daemon[11931]: New relevant interface vif3.0.IPv6 for mDNS.
2022-02-05T11:05:44.823226+03:00 MSK-HVX03 avahi-daemon[11931]: Registering new address record for fe80::fcff:ffff:feff:ffff on vif3.0.*.
На сервере HVX4 появляется ошибка
[730951.599750] qemu-system-i38[12805]: segfault at 0 ip 00007f1549972fae sp 00007ffe2cbb1d98 error 4 in libc-2.19.so[7f15498e3000+19e000]
[730952.199911] br0: port 3(vif6.0-emu) entered disabled state
[730952.200687] device vif6.0-emu left promiscuous mode
[730952.200769] br0: port 3(vif6.0-emu) entered disabled state
Детализация ошибки: MSK-HVX04 Successful vif-bridge remove for vif6.0-emu, bridge br0.
2022-02-13T21:16:39.379444+03:00 MSK-HVX04 libvirtd[12288]: this function is not supported by the connection driver: virDomainGetMetadata
2022-02-13T21:16:39.382492+03:00 MSK-HVX04 libvirtd[12288]: this function is not supported by the connection driver: virDomainMemoryStats
2022-02-13T21:16:39.438856+03:00 MSK-HVX04 libvirtd[12288]: this function is not supported by the connection driver: virDomainListAllSnapshots
2022-02-13T21:17:35.952402+03:00 MSK-HVX04 libvirtd[12288]: this function is not supported by the connection driver: virConnectGetDomainCapabilities
2022-02-13T21:17:50.520078+03:00 MSK-HVX04 avahi-daemon[11205]: Interface vif6.0.IPv6 no longer relevant for mDNS.
2022-02-13T21:17:50.520859+03:00 MSK-HVX04 avahi-daemon[11205]: Leaving mDNS multicast group on interface vif6.0.IPv6 with address fe80::fcff:ffff:feff:ffff.
2022-02-13T21:17:50.521289+03:00 MSK-HVX04 avahi-daemon[11205]: Withdrawing address record for fe80::fcff:ffff:feff:ffff on vif6.0.
2022-02-13T21:17:50.521701+03:00 MSK-HVX04 avahi-daemon[11205]: Withdrawing workstation service for vif6.0.
2022-02-13T21:17:50.522038+03:00 MSK-HVX04 kernel: [732253.813489] br0: port 2(vif6.0) entered disabled state
2022-02-13T21:17:50.522052+03:00 MSK-HVX04 kernel: [732253.814036] device vif6.0 left promiscuous mode
2022-02-13T21:17:50.522055+03:00 MSK-HVX04 kernel: [732253.814075] br0: port 2(vif6.0) entered disabled state
2022-02-13T21:17:50.854232+03:00 MSK-HVX04 logger: /etc/xen/scripts/vif-bridge: offline type_if=vif XENBUS_PATH=backend/vif/6/0
2022-02-13T21:17:51.076734+03:00 MSK-HVX04 logger: /etc/xen/scripts/vif-bridge: brctl delif br0 vif6.0 failed
2022-02-13T21:17:51.171396+03:00 MSK-HVX04 logger: /etc/xen/scripts/vif-bridge: ifconfig vif6.0 down failed
2022-02-13T21:17:51.176571+03:00 MSK-HVX04 logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge offline for vif6.0, bridge br0.
2022-02-13T21:17:51.224262+03:00 MSK-HVX04 logger: /etc/xen/scripts/vif-bridge: remove type_if=tap XENBUS_PATH=backend/vif/6/0
2022-02-13T21:17:51.270499+03:00 MSK-HVX04 logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge remove for vif6.0-emu, bridge br0.
2022-02-13T21:18:11.102665+03:00 MSK-HVX04 logger: /etc/xen/scripts/vif-bridge: online type_if=vif XENBUS_PATH=backend/vif/10/0
2022-02-13T21:18:11.226099+03:00 MSK-HVX04 kernel: [732274.518803] device vif10.0 entered promiscuous mode
2022-02-13T21:18:11.230069+03:00 MSK-HVX04 kernel: [732274.521906] br0: port 2(vif10.0) entered forwarding state
2022-02-13T21:18:11.230089+03:00 MSK-HVX04 kernel: [732274.521926] br0: port 2(vif10.0) entered forwarding state
2022-02-13T21:18:11.232737+03:00 MSK-HVX04 logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge online for vif10.0, bridge br0.
2022-02-13T21:18:11.237575+03:00 MSK-HVX04 logger: /etc/xen/scripts/vif-bridge: Writing backend/vif/10/0/hotplug-status connected to xenstore.
2022-02-13T21:18:11.290472+03:00 MSK-HVX04 logger: /etc/xen/scripts/vif-bridge: add type_if=tap XENBUS_PATH=backend/vif/10/0
2022-02-13T21:18:11.354081+03:00 MSK-HVX04 kernel: [732274.646735] device vif10.0-emu entered promiscuous mode
2022-02-13T21:18:11.358069+03:00 MSK-HVX04 kernel: [732274.649879] br0: port 3(vif10.0-emu) entered forwarding state
2022-02-13T21:18:11.358089+03:00 MSK-HVX04 kernel: [732274.649914] br0: port 3(vif10.0-emu) entered forwarding state
2022-02-13T21:18:11.360925+03:00 MSK-HVX04 logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge add for vif10.0-emu, bridge br0.
2022-02-13T21:18:13.042384+03:00 MSK-HVX04 avahi-daemon[11205]: Joining mDNS multicast group on interface vif10.0.IPv6 with address fe80::fcff:ffff:feff:ffff.