Search results

You mean Dell PowerEdge SC1425? I think I have one of these in my storage. Will try to launch PVE 4.2 install today, to see if it's related to SC1425.

Do you have a firewall on the NFS server or PVE node enabled? Please disable both and try again. What's the output if you run "showmount -e nsxxxxx.ip-xxx-xx-xxx.eu" on the other (non-PVE) server?

On my PVE 4.2-5/7cf09667 cluster NFS is working fine, so don't seems to be a 4.2-5 issue. Can you please post output of: # cat /etc/pve/storage.cfg # showmount -e IP.OF.NFS.SERVER

If you use a private network for your PVE traffic, you can add "migration_unsecure: 1" to /etc/pve/datacenter.cfg to solve this issue (only works for PVE 4.2 and above).

Okay, what I did today: 1. Upgrade to PVE 4.2-5/7cf09667 and rebooted all nodes. Just to be sure this isn't solved already in a upgraded version of PVE. 2. After rebootes finished I've migrated some VM's, same issues. So I'm sure the problem is still there and not solved in new version. 3...

2016-05-19 20:23:15.298146 osd.1 192.168.111.131:6800/4120 183 : cluster [INF] 1.a9 scrub starts 2016-05-19 20:23:15.429815 osd.1 192.168.111.131:6800/4120 184 : cluster [INF] 1.a9 scrub ok 2016-05-19 20:38:42.435549 osd.1 192.168.111.131:6800/4120 185 : cluster [INF] 1.0 scrub starts 2016-05-19...

Are you sure about that? I doubt that since when I migrate (2) VM's at the same time (on all of my clusters, even on my 10 Gbit cluster) sometimes I see a "migration aborted" for one of the VM's. Looks like if 2 processes are exactly alike/meet each other somewhere, something fails. If I restart...

After I changed to "Max Performance" power profile and removed the "hpet=disable" from GRUB config the hpet logs came back May 19 22:22:05 node01 kernel: [ 2727.779396] CE: hpet3 increased min_delta_ns to 20115 nsec May 20 00:20:25 node03 kernel: [ 7720.535187] CE: hpet3 increased min_delta_ns...

First of all, thank you for all your help, greatly appreciated! After some more testing today I have a workaround and I know where the problem is. To answer your question: yes, I can confirm the problem also exists without a node restart or ceph daemon reload. Normally I always migrate 2-3...

Last year I've tested on PVE 3.x with IDE as driver (while testing some performance differences with different drivers), but that maked the Elastix VM boot very slow (+/- 5 mins, with virtio +/- 1 mins), so don't know if that's a good option. But isn't it strange I didn't have this problem on...

Okay, I'm changing them to "Max Performance" now on all nodes on all clusters (time-consuming job ;)). Will also remove the hpet=disable, just to see if the error messages come back. Will let you know soon. Thanks!

Hi Alexandre, Yes, I always use virtio as disk driver and cache=none. Thanks.

I just checked 3 nodes, one R310 with the "problem", one R610 without the problem and one R710 without the problem. On all 3 nodes I use the same settings for power management (Active Power Controller), which is the default, and I can choose between: - Active Power Controller - Maximum...

Unfortunately this problem isn't solved. I just again had the same issue with 2 VM disk images. But it came to my attention now that when I moved this 2 VM's not a single ping was lost. Normally with an online migration you lose 1-3 packets for each VM, so it seems to be an issue with the...

I just asked the PVE staff to say goodbye to systemd-timesyncd at Bugzilla (https://bugzilla.proxmox.com/show_bug.cgi?id=998). Let's see what they are thinking.

Nope, no special bios settings. We only use Dell-servers and I only see this issue on Dell PowerEdge R310 servers with X3450 CPU, not on any other Dell server (R610, R710, R320 and R420 tested). Don't know for sure if others CPU's are also affected, since I only have R310's with X3450's. But...

Yes, datacenter firewall rules are applied to all nodes in the cluster. You can check with "iptables -L" on each node. I don't use containers, so I can't tell you for sure, but datacenter firewall rules aren't applied to KVM VM's and I think also not to containers. Also check with "iptables -L"...

What are you using as gateway in the VM's? Whatever you do, you need to have a gateway/router in the 10.10.10.xxx range, since your subnetmask is 255.255.255.0 (/24). You can add routing/gateway functionality to your PVE node, since it's based on Debian Linux (use Google). After that you can use...

Not sure what the ID's are, I'm not at a computer right now, but maybe you can get the ID's from /boot/grub/grub.cfg? (BTW, don't edit this file, as it will be overwritten by a "update-grub"). But, If I was you I boot into the required kernel and then purge other kernels.

No, first boot in the kernel you want to keep using and then purge the other kernels.