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

ixgbe diver with high max_vfs prevents pve 2.2 from booting.

$
0
0
After installing i82599 10-gigabit adapter and setting
cat /etc/modprobe.d/intel.conf
Code:

options ixgbe max_vfs=63 LRO=0 FCoE=0
blacklist ixgbevf

server with pve 2.2 stopped booting (freezing at NFS statd starting). After some investigation I found that ip utility showed only first three interfaces (this port should be fourth and all bridges, vlans, etc next). Updating driver to last did no effect. After lowering max_vfs to 42 it seems work fine.

Looks like current pve kernel (2.6.32-17-pve) is affected by https://bugs.launchpad.net/ubuntu/+s...ux/+bug/960497

Would you please fix this?

I can give more info. Say, statd whle freezed, eated 100% CPU with continously doing something via rtnetlink.

$ pveversion -v
pve-manager: 2.2-32 (pve-manager/2.2/3089a616)
running kernel: 2.6.32-17-pve
proxmox-ve-2.6.32: 2.2-83
pve-kernel-2.6.32-17-pve: 2.6.32-83
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-34
qemu-server: 2.0-72
pve-firmware: 1.0-21
libpve-common-perl: 1.0-41
libpve-access-control: 1.0-25
libpve-storage-perl: 2.0-36
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.3-10
ksm-control-daemon: 1.1-1

Viewing all articles
Browse latest Browse all 170565

Trending Articles



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