Quantcast
Channel: Proxmox Support Forum
Viewing all articles
Browse latest Browse all 170705

pveproxy worker segfault

$
0
0
Hello, everybody! I'm using kernel 3.10.0-2-pve and saw logs segmentation today one of the workers pveproxy.
Code:

[534952.224767] pveproxy worker[18844]: segfault at 4 ip 00007f0d3e465493 sp 00007ffff7885378 error 4 in libqb.so.0.11.1[7f0d3e44e000+1f000]
I also meet periodically such records:
  • [461799.759793] kvm: zapping shadow pages for mmio generation wraparound
  • [461799.760945] kvm: zapping shadow pages for mmio generation wraparound
  • [470419.454367] kvm: zapping shadow pages for mmio generation wraparound
  • [470419.455371] kvm: zapping shadow pages for mmio generation wraparound


  • pveversion -v
  • proxmox-ve-2.6.32: 3.2-126 (running kernel: 3.10.0-2-pve)
  • pve-manager: 3.2-4 (running version: 3.2-4/e24a91c1)
  • pve-kernel-3.10.0-2-pve: 3.10.0-10
  • pve-kernel-2.6.32-29-pve: 2.6.32-126
  • lvm2: 2.02.98-pve4
  • clvm: 2.02.98-pve4
  • corosync-pve: 1.4.5-1
  • openais-pve: 1.1.4-3
  • libqb0: 0.11.1-2
  • redhat-cluster-pve: 3.2.0-2
  • resource-agents-pve: 3.9.2-4
  • fence-agents-pve: 4.0.5-1
  • pve-cluster: 3.0-12
  • qemu-server: 3.1-16
  • pve-firmware: 1.1-3
  • libpve-common-perl: 3.0-18
  • libpve-access-control: 3.0-11
  • libpve-storage-perl: 3.0-19
  • pve-libspice-server1: 0.12.4-3
  • vncterm: 1.1-6
  • vzctl: 4.0-1pve5
  • vzprocps: 2.0.11-2
  • vzquota: 3.1-2
  • pve-qemu-kvm: 1.7-8
  • ksm-control-daemon: 1.1-1
  • glusterfs-client: 3.4.2-1

Than it could face in the virtual machines?

Viewing all articles
Browse latest Browse all 170705

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>