Recent content by Thomas Plant

Hi, here is the config of the VM: root@pve4:~# qm config 175 agent: 1 bootdisk: scsi0 cores: 2 cpu: Broadwell description: CentOS Template no Software%0ARepos MariaDB/PHP/CodeIT aktiviert.%0A%0ALetztes Update%3A 27.05.2020 17%3A30 ide2: NFS2:iso/CentOS-7-x86_64-Minimal-1908.iso,media=cdrom...

Hi, we have added a new server to our cluster. When we try to migrate a VM from the old (Intel Xeon 5120) to the new server (Xeon 6240) we get the following error: 020-11-16 10:08:32 starting migration of VM 175 to node 'pve8' (10.10.2.94) 2020-11-16 10:08:33 starting VM 175 on remote node...

Stupid me ..... we are not using QCow2 on this particular server. It's using lvm-thin on local disks. So a 10 TB logical volume should not be a problem I asume.

Same problem here......never found a solution, other than migrating VMs regularly back and forth to another host. Forum Post

Hello, what is the maximum size of a single QCow2 Image for a KVM VM? Have a client who wants a VM with 10 TB diskspace. Can/should I assign a single QCow2 file with 10 TB or assemble with LVM p.e. 5 x 2 TB Images? Thanks and greetings, Thomas

Warranty of the entire server is up to 3 years, depends how much we are willing to pay. In the techspecs there is a line "Drive writes per day" for 5 years with 1 dwpd. Should be an indication that it should last longer than the normal warranty of the rest of the server, shouldn't it?

The SATA-DOM Specs are in the attached screenshot. Do not know the brand of the DOMs. We buy from a known german company, do not know if I can post the name here. But they have the option to buy 'Proxmox' compatible hardware, which they have tested and approved.

Hello, installing Proxmox on SATA-DOMs is a valid option? I saw older threads where it was not recommended. I thought to use two SATA-DOMs in mirrored configuration, which are 64 GB in size and rated at 1 DWPD, shouldn't they be reliable enough only for the OS? Regards, Thomas

Ah, no we are not backing up with Proxmox. We do a backup internal on the VM at this time. Sorry for the confusion.

Installed the latest updates for PVE as I have seen that qemu was updated, hoped that it helped. Added a little script which wrote the 'rss' column of the 'ps -eo rss,command' output to a file, every second. I made a primitive graph attached to this post where we see clearly that around 4 or 5...

Could it be some remains from XenServer where the VMs where imported from? But other VMs which are working normally where also imported from XenServer.....

Sorry, wrote to fast about local storage, it is not possible, not enough space on local disks for the VMs, are all to big. The VM from the screenshot has 4 GB RAM configured. Now it raised to 7,3 GB used RAM, still raising slowly. The VM i migrated to another host, hast risen to 8,6 GB used RAM...

The VM we had to restart on last friday now has again 6,4 GB of RAM in use, see attached screenshot. Are all those threads normal that show up in the screenshot (made with htop)?

Live migrated two VMs with very high memory consumption to another host, now (obviously) RAM usage is in balance with the configured RAM. Will keep an eye on them. How much overhead of memory is normal?

All our VMs are on NFS. And all are in production, so fiddling a lot around is problem. I could clone it to local storage and start it without network, is this sufficient for a test?