problems with pve-kernel-2.6.32-25-pve

[noPa$$word]

I use 2 proxmox server with linux and windows guests. After upgrade to pve-kernel-2.6.32-25-pve 2 guests (ipfire and zentyal) cant boot. After downgrade to pve-kernel-2.6.32-24-pve on one proxmox server the guest (ipfire an zentyal) starts normal on this server.

zentyal 3.2 with kernel: (uname -a)
Linux zentyal 3.8.0-30-generic #44~precise1-Ubuntu SMP Fri Aug 23 17:33:45 UTC 2013 i686 i686 i386 GNU/Linux

ipfire 2.13 with kernel: (uname -a)
Linux ipfire 3.2.48-ipfire-pae #1 SMP Sun Jun 30 10:29:03 GMT 2013 i686 pentium4 i386 GNU/Linux

Proxmox1:
pveversion -v
proxmox-ve-2.6.32: 3.1-113 (running kernel: 2.6.32-25-pve)
pve-manager: 3.1-17 (running version: 3.1-17/eb90521d)
pve-kernel-2.6.32-24-pve: 2.6.32-111
pve-kernel-2.6.32-25-pve: 2.6.32-113
pve-kernel-2.6.32-22-pve: 2.6.32-107
pve-kernel-2.6.32-23-pve: 2.6.32-109
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.0-2
pve-cluster: 3.0-7
qemu-server: 3.1-5
pve-firmware: 1.0-23
libpve-common-perl: 3.0-6
libpve-access-control: 3.0-6
libpve-storage-perl: 3.0-13
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.0-2

proxmox2:
pveversion -v
proxmox-ve-2.6.32: 3.1-113 (running kernel: 2.6.32-24-pve)
pve-manager: 3.1-17 (running version: 3.1-17/eb90521d)
pve-kernel-2.6.32-24-pve: 2.6.32-111
pve-kernel-2.6.32-25-pve: 2.6.32-113
pve-kernel-2.6.32-22-pve: 2.6.32-107
pve-kernel-2.6.32-23-pve: 2.6.32-109
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.0-2
pve-cluster: 3.0-7
qemu-server: 3.1-5
pve-firmware: 1.0-23
libpve-common-perl: 3.0-6
libpve-access-control: 3.0-6
libpve-storage-perl: 3.0-13
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.0-2

regards
K.W.

 

[noPa$$word]

The same with pve-kernel-2.6.32-26-pve

With pve-kernel-2.6.32-24-pve on the same server and with the same configs my zentyal server and ipfire starts normal.

K.W.

 

[tom]

what does "can´t boot" mean? any error messages?

also provide the VM config (qm config VMID).

I just installed latest zentyal and ipfire here, no issues.

 

[noPa$$word]

Config ipfire:

boot: cdn
bootdisk: virtio0
cores: 4
ide2: NFS:iso/ipfire-2.13.i586-full-core70-19-06-2013-Marx.iso,media=cdrom,size=106624K
memory: 1024
name: IPFIRETest
net0: virtio=5E:A9:94:EC:FC:A0,bridge=vmbr0
net1: virtio=B6:9E:CF:6A:AF:60,bridge=vmbr1
onboot: 1
ostype: l26
sockets: 1
virtio0: NFS:104/vm-104-disk-1.qcow2,format=qcow2,size=8G

config zentyal:

balloon: 1024
boot: cdn
bootdisk: virtio0
cores: 4
ide2: none,media=cdrom
memory: 2048
name: zentyal.intra.lokal
net0: virtio=4A:FF:76:49:CF:7C,bridge=vmbr0
onboot: 1
ostype: l26
sockets: 1
vga: qxl
virtio0: NFS:200/vm-200-disk-1.vmdk,format=vmdk,size=64G

With kernel xx25 and xx26 the boot process proceeded in slow motion and came to a standstill.
I will test it with this kernel xx25 and xx26 tomorrow. Where can I find log files?

regards
K.W.

 

[noPa$$word]

When I use 2 Cores (not 4 Cores) the guest booting also with kernel xx25 and xx26.

K.W.

 

[tom]

what physical cpu do you have?

 

[noPa$$word]

cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz
stepping : 11
cpu MHz : 2327.416
cache size : 4096 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dts tpr_shadow vnmi flexpriority
bogomips : 4654.83
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz
stepping : 11
cpu MHz : 2327.416
cache size : 4096 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dts tpr_shadow vnmi flexpriority
bogomips : 4654.83
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:


K.W.

 

[tom]

as your CPU just have two cores, you can only assign two CPUs to a VM.

 

[noPa$$word]

bingo..........
thanks

K.W.

last question: Why did it take until kernel x24 works with 4 cores and the same configs? I thought the socket and cores are virtual. I use always 1 socket and 2 or 4 cores.......