Search results

What is the current status of support online migration VMs from Intel to AMD and AMD to Intel? I read in the manual: CPU type kvm64 is guaranteed to work everywhere. But I found in the forum the discussions about problems...

It's a path to your local storage. You have only 9.7GB there

You tried to save image 150Gb to the /var/lib/vz/dump where you have 9.7Gb Therefore you can see a message - No space left on device

No one knows what your error message looks like, no one knows anything about your system. You must to show the most detailed information about everything

Removing the script /etc/kernel/postinst.d/kdump-tools and the package kdump-tools solved the problem Thanks

apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be...

I changed the script a bit to bring the result closer to reality. I added the ability to compress data at the level of 30% (PERC="30") as on my production system That changed the results but quite a little bit.

recordsize=64k ashift=12 compression=lz4 atime=off

Unfortunately, my server configuration is not like yours. Supermicro X11DDW-NT BIOS 3.3 SATA controller: Intel Corporation Lewisburg SATA Controller [AHCI mode] (rev 09) RAIDZ 4 x Samsung SSD 860 PRO 4TB Firmware Version: RVM01B6Q write: IOPS=1143, BW=1143MiB/s (1199MB/s)(64.0GiB/57323msec)...

Do not attempt to perform pveperf with significant disk load on the production system. This process "echo 3 > /proc/sys/vm/drop_caches" will be run until the disk load be reduced. To reproduce the situation, run a long benchmark and run this command "echo 3 > /proc/sys/vm/drop_caches" in same...

Could you show the outputs this commands please? lshw -class disk -class storage or hwinfo --disk dmidecode -s baseboard-product-name I have a server with a similar configuration, we could compare the performance Try my script for the benchmark usage: ./fio.sh <Directory> <uniq name>

Try to disassemble the pool, and check the benchmark with a single disk and ext4 file system.

I'm not sure I got it right. Have you proposed to remove the CPU from the list of suspicions or is the CPU the main suspect? Could you recommend a way to clarify this hypothesis please ? Do you suspect that the CPU may be causing problems by intuition or is there something else? I’m...

The system upgrade didn't solve the problem. Yesterday this happened with last proxmox 6.1-7. It was after full reinstall. Symptoms of malfunction: 1. Problems begin with this message Feb 22 15:43:53 brk2-node2 kernel: [349758.004743] general protection fault: 0000 [#1] SMP NOPTI Feb 22...

It doesn't help. It seems the ZFS module error causes violations of other kernel functions. But I don't know how to determine what exactly. Probably it would help find a way to continue without rebooting. I hope the kernel update solves the problem.

From time to time I have to restart the servers due to loss of control. Sometimes I get such messages in the log Feb 17 02:38:29 kfn1-node4 pvedaemon[38846]: can't lock file '/var/lock/qemu-server/lock-141.conf' - got timeout Feb 17 02:38:29 kfn1-node4 pvedaemon[8817]: <root@pam> end task...

Hello, I need the online migrate all VE to the second node without downtime, but the migration failed. I use local storage. pve-manager/6.1-5/9bf06119 (running kernel: 5.3.13-2-pve) qm migrate 105 node2 --online --with-local-disks 2020-02-12 00:14:47 use dedicated network address for sending...

I found similar problem here https://github.com/zfsonlinux/spl/issues/388

I suspect it started after my trying to run pveperf /PoolZFS The pveperf worked too long and I killed him. But I can't to kill this process ps -Flww -p 34740 F S UID PID PPID C PRI NI ADDR SZ WCHAN RSS PSR STIME TTY TIME CMD 0 R root 34740 1 99 80 0 - 596 -...

Button "Take snapshot" is not working "snapshot feature is not available at /usr/share/perl5/PVE/QemuServer.pm line 4107." pveversion -v pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1) running kernel: 2.6.32-18-pve proxmox-ve-2.6.32: 2.3-88 pve-kernel-2.6.32-14-pve: 2.6.32-74...