[SOLVED] VM very slow after restored in new Cluster

V

volleasy

Renowned Member
Nov 27, 2015
24
0
66
Hello,

I restored two VM in a new Cluster. After boot up all operations are very slow.

I copied the backup from 4.4 Proxmox to 5.3 cluster
First step was to create a VM with same ID: and same Boot disk size
next was to restore from Backup to this VM

After boot the VM is very slow


old .conf
balloon: 1
bootdisk: ide0
cores: 4
ide0: ceph_disks_01:vm-114-disk-1,size=100G
ide2: none,media=cdrom
memory: 16384
name: isp31deb8601
net0: e1000=02:13:7A:42:3A:09,bridge=vmbr1
numa: 0
onboot: 1
ostype: l26
smbios1: uuid=70d13183-68af-46e1-b586-93d4810a93c2
sockets: 2


new .conf
agent: 1,fstrim_cloned_disks=1
balloon: 1
bootdisk: ide0
cores: 4
ide0: Disks:vm-114-disk-2,cache=writethrough,size=100G,ssd=1
ide2: none,media=cdrom
memory: 16384
name: isp31deb8601
net0: virtio=02:13:7A:42:3A:09,bridge=vmbr0,tag=100
numa: 0
onboot: 1
ostype: l26
smbios1: uuid=70d13183-68af-46e1-b586-93d4810a93c2
sockets: 2


Old Node Proxmox - Virtual Environment 4.4-5/c43015a5

CPUs
32 x Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz (2 Sockets)
Kernel Version
Linux 4.4.35-1-pve #1 SMP Thu Dec 22 14:58:39 CET 2016

New Node Proxmox 5.3 -Virtual Environment 5.3-8
CPU(s)
48 x Intel(R) Xeon(R) CPU E5-2651 v2 @ 1.80GHz (2 Sockets)
Kernelversion
Linux 4.15.18-10-pve #1 SMP PVE 4.15.18-32 (Sat, 19 Jan 2019 10:09:37 +0100)
PVE Manager Version
pve-manager/5.3-8/2929af8e

Old Proxmox is one Node with Ceph 12 OSD

New Proxmox is a 12 Node Cluster with 36 OSD
10GB SPF+ for cluster 10GB SPF+ for Ceph

All VM´s directly build on the nodes are running with good performance.

only the restored from 4.4 backups have poor speed.

here a very slow hdparm test from this restored VM:
Timing cached reads: 2 MB in 2.75 seconds = 746.00 kB/sec
Timing buffered disk reads: 2 MB in 4.86 seconds = 421.00 kB/sec

other VM
Timing cached reads: 10000 MB in 2.75 seconds = 5003.60 MB/sec
Timing buffered disk reads: 2 MB in 4.86 seconds = 6.77 MB/sec

I´ve no idea why this disk speed is poor.
 
Hi,

ide is only for legacy use and should not be used.
Is your Linux VM not able to use virtio?
 
Hello Wolfgang,

thx for reply. that are old VM´s running in Proxmox since years. when I use the internal shell, I have a lot of kernel issues like below.

root@xxxxxxxxxxx :~# [1800.160113] INFO: task cleanup:7262 blocked for more than 120 seconds.
[1800.160112] Not tainted 3.16.0-7amd54 #1
[1800.160162] "echo" 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[1800.160120] INFO: task bounce 7295 blocked for more than 120 seconds.
[1800.160151] Not tainted 3.16.0-7amd54 #1

So I think it has to do with kvm specific things.
that are some Mail an webservers with failover and replicated databases.
It will be a lot of work to rebuild from scratch.
I turned back to the old proxmox until I solve the problem or have to decide to make it new
 
This errors are related to the cpu so change the cpu type.

Have you installed the meltdown and specter firmware packages?
https://wiki.debian.org/Microcode
Or better does your bios has the fixes included?

With Linux there is no need to reinstall it new when you change storage bus.
You can try with a clone of the VM.
Just remove the disk and add it in again with scsi and virtio controller.
then change in the options tab the boot disk.
And normally a Linux with a 3.16 kernel will boot without problems.
 
Thx, this is what I´ve tried today, I seems it works only when I change to virtio and back to ide. Yesterday I tried without sucsess to switch from scsi back to IDE. Now VM is running as expected. I do this workaroundnow on the other restored VM´s too. No I´ve not updated the bios of all nodes.
The hardware is my Datacenter in Tallinn, I´m in Berlin. It is to much risk with the remote BMC, but in March I will renew the bios. Is there any Problem with running Proxmox after the meltdown fix?
 
volleasy said:
Is there any Problem with running Proxmox after the meltdown fix?
Click to expand...
Yes, the security and I also see kernel crashes.
I would use the Intel microcode package. This only needs a reboot and you use the latest firmware.
 
You must log in or register to reply here.
Top Bottom