Search results

@sb-jw Thank you for your feedback. I'm gonna check checkmk, did not know it existed. Can you also check for bad memory stick (ECC errors) and Predictive disk failure through it ?

Thanks guys for keeping this thread alive. @sb-jw : Why do i use OMSA ? OMSA use smuxpeer to fill SNMP. Then i use https://github.com/trondham/check_openmanage with Centreon monitoring. I'm like @CTCcloud. Long time using those system and no need to teach the new recruit. Ease of use.

Hi all, I cannot edit the 1st post to update the steps anymore. Thank you for your feedback.

Thank you. I've planned to migrate one of my cluster to 8.0 this Monday. Please, I would love your feedback on 8.0 if you succeed. Edit: I did the upgrade but was stuck at boot with Service Networking/starting (xxx minutes / nolimit). The problem was ntp that was replaced by ntpsec and block...

Never tried it. Because it's OME and not OMSA (OpenManage Server Administrator).

Same here. I've upgraded to pve-qemu-kvm_6.1.0-3 and no more IO issue on VirtIO disk.

Thank you everyone for your feedback. I've updated the main post with them.

In that case, enp129s0f1(node3), enp129s0f0(node2) should be slave of vmbr1 and the ip should be configured on the vmbr1. Right now, your bridge vmbr1 is not connected to any network interface. How could it communicate with the outside of your server ? in this situation VMa(on node2) and VMb(on...

I've got Proxmox on multiple Dell servers (from 2950 to R740) H700 will work without problem. H310 wont work. You have 2 choices : Either do not use RAID or use mdadm software raid. In my opinion, if you have a shared storage (iSCSI, NFS, Ceph) you dont need raid for the system. I've been...

I've done it differently. On the switch : - the port where the box is connected is UNTAG on VLAN 42. - the port where the proxmox is connected is switchport mode trunk allowed vlan 1,42 with vlan 1 untag. On proxmox : - vmbr0 is not vlan aware - the pfsense has 2 interface virtio : the first...

Maybe you are affected by the same problem as me. I had to edit VM config to set aio=native on all VM disk and switch virtio disk to scsi. check : https://forum.proxmox.com/threads/sporadic-buffer-i-o-error-on-device-vda1-inside-guest-raw-on-lvm-on-top-of-drbd.21051/page-2 You can validate...

agent: 1 balloon: 0 boot: order=scsi0;ide2 cores: 4 cpu: host ide2: none,media=cdrom memory: 20480 name: MED-BDD-5 net0: virtio=46:58:91:52:2A:F7,bridge=vmbr0 net1: virtio=3E:30:4B:D0:17:29,bridge=vmbr0,link_down=1,tag=21 numa: 0 ostype: l26 scsi0...

pveversion -v proxmox-ve: 7.1-1 (running kernel: 5.13.19-1-pve) pve-manager: 7.1-5 (running version: 7.1-5/6fe299a0) pve-kernel-5.13: 7.1-4 pve-kernel-helper: 7.1-4 pve-kernel-5.11: 7.0-10 pve-kernel-5.4: 6.4-7 pve-kernel-5.13.19-1-pve: 5.13.19-2 pve-kernel-5.11.22-7-pve: 5.11.22-12...

On it ! Thank you. Would you like any other information ? You are right, VM are configured like that : #172.X.Y.Z agent: 1 balloon: 0 boot: cd bootdisk: virtio0 cores: 4 cpu: host ide2: none,media=cdrom memory: 20480 name: MED-BDD-5 net0: virtio=XX:XX:XX:XX:XX:XX,bridge=vmbr0 numa: 0 ostype...

Hello everyone, I'm sorry to dig up an old thread but i'm exactly in this situation after upgrading from 6.4 (everything was fine) to 7.0 (last week) and 7.1 (yesterday). Nothing in the log of the host. Network/Disk/CPU/RAM all ok. But inside the VM (KVM) it's another story. It's independant...

The gpg error is usually an ipv6 problem.

I just did a new install on a R740 and a R430 with proxmox 6.2-1 iso and OMSA 930. Works perfectly. I also have 930 on R730, NF500 and PE2950 following this tutorial. For the PE2950 i have the problem that the CMOS battery is not found ... who cares ? :p Sorry i don't have R710 to test.

Thanks a lot for you feedback. I'll update the tutorial to add ncurses

You're welcome. I received so much from the community. It was my time to share ;)

my 2 cents after upgrading my cluster from 5.4 to 6, do update fast. Node by node i followed the tutorial for proxmox upgrade as well as ceph. When i was in a mixed versions, corosync was losing synchronization. I had to stop corosync and restart it in foreground "corosync -f" on all node until...