Recent content by thheo

Did you sort this out? I experience the same thing

Indeed vmbr0 with dhcp config messes up SNAT. Any idea why? Is the dhclient process doing something special?

Is this still needed in 6.3? I am just testing proxmox on a new server and trying to follow your steps I see the partition layout built by the installer is not the one described in your post and it seems that it just works out-of-the-box (I mean raid1 zfs). I am using some 2x SATA DOMs which are...

Hi, I have a similar problem, the pvestatd only reports the storages to influxdb: > show series key --- system,host=NFS1,nodename=proxmox,object=storages,type=nfs system,host=local,nodename=proxmox,object=storages,type=dir system,host=slow6,nodename=proxmox,object=storages,type=dir...

Hi, I face the same thing on an Intel server

I have this problem as well, I only have series from the storage part (some dirs and a nfs one). It used to work ok, but it stopped a few months ago. I have completely deleted and reinstalled influxdb and with a fresh database (proxmox) and I only get the series for the storage. I have made...

I was confused about the term "HA" at the beginning. I usually handle the networking part and I am used with technologies from Cisco: HA with NSF and SSO, which means a full controller is actively replicated to the standby one and it can do stateful-switch-over if it crashes. In Proxmox/RHCS...

Yup.. good finding. As far as I tested with a guest VM only writethrough and writeback avoids those messages. With directsync for example I still have them.. You have to stop the VM so that the new caching kicks in.. Let me know what are your test results..

Hello, Once in a while I was getting this warning in dmesg ( kern.log ): block drbd0: kvm[433746] Concurrent local write detected! [DISCARD L] new: 623356039s +8192; pending: 623356039s +8192 So I decided to study it more and I was able to trigger message whenever I was running sqlio benchmark...

Thank you, that solved it :)

Hello, I have this version up and running: proxmox-ve-2.6.32: 3.2-124 (running kernel: 2.6.32-28-pve) pve-manager: 3.2-2 (running version: 3.2-2/82599a65) pve-kernel-2.6.32-28-pve: 2.6.32-124 pve-kernel-2.6.32-26-pve: 2.6.32-114 lvm2: 2.02.98-pve4 clvm: 2.02.98-pve4 corosync-pve: 1.4.5-1...

Look for pci passthrough

You have to resize the filesystem as well.. you just resized the underlying layer.

https://pve.proxmox.com/wiki/Debugging_Installation

You need to have fencing and quorum. Either with qdisk or with a 3rd not that can be used only for quorum.