Search results

@moeff , after some researching I've created one more Windows Server 2019 VM from scratch and this time used the following hardware options: SCSI Controller: VirtIO SCSI Hard disk: VirtIO Block Network: e1000 (kept like in previous setup) And it seems to perform much better.

FYI: pve-manager/6.1-5/9bf06119 By default Windows Server 2019 (OS type is set to Windows 10/2016/2019) starts with no-hpet and hv_relaxed,hv_synic,hv_stimer and the host's load while VM is idling is high. Disabling no-hpet...

Looks like there's a patch: https://github.com/novnc/noVNC/issues/509

Thanks for the detailed explanation! You're right.

Hi, fabian. This is actually what Syncthing does: it sends only deltas and runs on demand (default is hourly, but can easily be changed in the config) or when a file (dis)appears.

Hi, It would be awesome to have Syncthing integrated into Proxmox VE as a VM replication backend. Currently, replication works only for ZFS file systems, while Syncthing will work on any mountable fs. A lot of other benefits exist: only changed blocks are transferred, unlimited replicas, rate...

If somebody curious, here's the instruction how to build up a GFS2 clustered file system in Proxmox 6 on top of shared iSCSI LUN: https://gist.github.com/jazzl0ver/8959215eaed6e8367f9a4486a5690809 I haven't thoroughly tested it yet, but seems to be working. Would be happy if Proxmox team...

OS is CentOS 6 i386 (with latest system updates installed), "unpriviledged container" is set to "No". There indeed was a devpts line in the fstab, I've removed it and unmounted /dev/pts from shell. Now the issue's gone (no container restart required). Thanks for your prompt help!

faced same issue. any suggestions?

Hi. I've dumped an existing unprivileged LXC container to NFS storage and then tried to restore it on the same Proxmox server with unprivileged box ticked. The restoration has failed with the following error: ... extracting archive...

Just found out that the i/o scheduler had been reset to noop: [root@filer-1 ~]# cat /sys/block/sd{a,b}/queue/scheduler [noop] deadline cfq [noop] deadline cfq Wondering how that's possible.. The only suggestion it was tuned - its profile was set to "balanced". Changed to "latency-performance"...

Well.. Actually I don't complain for backup speeds :) INFO: transferred 85899 MB in 480 seconds (178 MB/s) INFO: archive file size: 260MB INFO: Finished Backup of VM 107 (00:08:02) The other day/time: INFO: transferred 311385 MB in 5490 seconds (56 MB/s) INFO: archive file size: 27.85GB INFO...

Just for the records. I forgot that the NFS server had a running Syncthing service, which started to sync the folder I used for fio (my bad). Here are the results after turning it off: root@vm-box-1:/mnt/pve/filer-1-images# fio --size=9G --bs=64k --rw=write --direct=1 --runtime=60...

Sorry for the delay. Yeah, it does not look speedy. It might be due to ZFS dedup and compression enabled. But this must not affect the latency when deadline scheduler is selected (if I'm not mistaken). Do you have any ideas how to make the NFS server to respond fast?

Here are the results when the cache is off (with and without directio): Proxmox host: root@vm-box-1:/mnt/pve/filer-1-images# fio --size=9G --bs=64k --rw=write --direct=1 --runtime=60 --name=64kwrite --group_reporting | grep bw write: io=2352.7MB, bw=40141KB/s, iops=627, runt= 60016msec bw...

Hi @manu. Thanks for your response. The point is that NFS server is online it just seems to get frozen due to high i/o during backup and thus stops responding to nfs client's fsstat RPC command. So I'm wondering if there's a tweak that could tune up the server's responsiveness. This is not a...

@carles89, thanks for you reply and wishing to help me! I don't think it's a networking issue. The switch port is loaded for less than 100 Mbit/s during the backup (while it's 1Gb port). This indeed might be the NFS server issue. I haven't tried with mdadm, since ZFS seemed to me more preferred...

No, I don't use OVH. My NFS server is CentOS 7 box with data storage on two drives managed by ZFS mirror. Proxmox and CentOS boxes are in the same 1Gb LAN. NFS server: [root@filer-1 ~]# exportfs -v /zmir/backup/images...

Still facing such NFS issues with Proxmox VE 4.4.. :( Jun 17 01:40:05 vm-box-1 kernel: INFO: task lzop:1093 blocked for more than 120 seconds. Jun 17 01:40:05 vm-box-1 kernel: Tainted: P W O 4.4.49-1-pve #1 Jun 17 01:40:05 vm-box-1 kernel: "echo 0 >...

Hi all. I'd like to share some issues I faced after migration CentOS 6 containers from OpenVZ (Proxmox VE 3.4) to LXC (Proxmox VE 4.1) using https://pve.proxmox.com/wiki/Convert_OpenVZ_to_LXC. I had a CentOS 6 CT installed from a standard template. After migrating it to LXC there were two...