Hi all,
Something of a plea for help here, as this has been driving me mad and I can't seem to find the solution. It's probably something really silly and simple too!
So we've just setup a two node cluster of PMVE 3.4.
We've a number of Centos 6.7 VMs running at present, and from time to time they just randomly hang.
Symptoms are that the CPU use reported in Proxmox drops to 0.00%, and the VM will not respond via either the network or the console.
The VMs have to be stopped at the CLI with the "qm stop" command and started again, where they will then run happy until the next seemingly random occurence.
To give you a rundown on our environment:
Nodes:
DL365 with 2 x Opteron 2379. 32GB RAM per node. Local SAS storage, P400i with 512MB cache. Onboard NIC plus HP NC380T.
Two network bridges, an Internal one and an External one. Two NICs each, via a bond.
VMs:
CentOS 6.7. Setup as KVM with hardware virt, 1 CPU (host), fixed RAM. VIRTIO NIC and storage controller, VMDK. Tried with QCOW2 format, and also with the LSI NIC and E1000 driver, but this has no effect.
Configurations of two of the VMs included below:
Any help or thoughts anyone has on what the root cause of this may be would be much appreciated!
Thanks,
Jon
Something of a plea for help here, as this has been driving me mad and I can't seem to find the solution. It's probably something really silly and simple too!
So we've just setup a two node cluster of PMVE 3.4.
We've a number of Centos 6.7 VMs running at present, and from time to time they just randomly hang.
Symptoms are that the CPU use reported in Proxmox drops to 0.00%, and the VM will not respond via either the network or the console.
The VMs have to be stopped at the CLI with the "qm stop" command and started again, where they will then run happy until the next seemingly random occurence.
To give you a rundown on our environment:
Nodes:
DL365 with 2 x Opteron 2379. 32GB RAM per node. Local SAS storage, P400i with 512MB cache. Onboard NIC plus HP NC380T.
Code:
root:~# pveversion -v
proxmox-ve-2.6.32: 3.4-156 (running kernel: 2.6.32-39-pve)
pve-manager: 3.4-6 (running version: 3.4-6/102d4547)
pve-kernel-2.6.32-39-pve: 2.6.32-156
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-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.10-2
pve-cluster: 3.0-17
qemu-server: 3.4-6
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-33
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-10
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
Two network bridges, an Internal one and an External one. Two NICs each, via a bond.
VMs:
CentOS 6.7. Setup as KVM with hardware virt, 1 CPU (host), fixed RAM. VIRTIO NIC and storage controller, VMDK. Tried with QCOW2 format, and also with the LSI NIC and E1000 driver, but this has no effect.
Configurations of two of the VMs included below:
Code:
root:~# qm config 101
bootdisk: ide0
cores: 1
cpu: host
description: Observium monitoring VM. %0A
hotplug: network,usb
ide0: VMStore:101/vm-101-disk-2.vmdk,format=vmdk,cache=writeback,size=76G
memory: 4608
name: OPS
net0: virtio=46:C3:5A:24:8F:B5,bridge=vmbr0
numa: 0
onboot: 1
ostype: l24
scsihw: virtio-scsi-pci
smbios1: uuid=f30620b4-0c81-40bf-bfd6-4f2608eac7bf
sockets: 1
vga: std
root:~# qm config 102
bootdisk: ide0
cores: 1
cpu: host
ide0: VMStore:102/vm-102-disk-2.vmdk,format=vmdk,cache=writethrough,size=26G
memory: 2048
name: NS1
net0: virtio=E6:A4:F3:2E:F2:AD,bridge=vmbr1
numa: 0
onboot: 1
ostype: l26
smbios1: uuid=a4bf5775-f5d2-473f-9c74-c427f2a41002
sockets: 1
vga: std
root:~#
Any help or thoughts anyone has on what the root cause of this may be would be much appreciated!
Thanks,
Jon