Hi,
Can you please check if the `net.ipv4.ip_forward=1` on the Proxmox VE node? you can run the following command to check:
sysctl net.ipv4.ip_forward
If not you may have to set it e.g.:
sysctl -w net.ipv4.ip_forward=1
Hello,
Proxmox VE is based on Debian, this means if your box can run the Ubuntu and Debian the Proxmox VE should run on it. As far as I know the `i5-4590T` supports Intel VT-x, this means the KVM should work as well.
Yes, we are looking for the issue. For a workaround you can create the user with its password in the same command e.g.:
proxmox-backup-manager user create <foo>@pbs --password <bar>
Hi,
pvestatd [0] daemon, this responsible for collecting and updating real-time infos on CPU, memory, disk and network usage.
[0] https://pve.proxmox.com/pve-docs/pvestatd.8.html
Maybe the reason of that, that host CPU ensures full compatibility with updates. and some CPUs works, but future updates could still fail due to missing CPU features. [0]
[0] https://pve.proxmox.com/pve-docs/chapter-qm.html#qm_meltdown_spectre
To narrow down the issue, I would ask:
- Only a specific VM have the issue mentioned?
- Did you double-check of the VM config specifically on the bandwidth?
-What kind of the network you use in your node SDN, or OVS?
- Did you test `iperf3`?
- Additionally, what version of Proxmox VE are you using?
Hi,
I guess there is a request for that in our Bugzilla [0] you can add CC to yourself to get update.
[0] https://bugzilla.proxmox.com/show_bug.cgi?id=2424
Hi,
I would check `/etc/hosts` file on both the new and existing nodes has consistent and correct entries. Each entry should map both the public IP to the FQDN and the private IP to the short hostname, additionally, could you run the following command from the both nodes?
curl -k...
Hi,
To avoid issues such as clock skew errors make sure that your nodes use chrony [0]. If the chrony is installed and up and running, I would check the syslog and ceph log for more details.
[0] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_time_synchronization
Great! Glad to hear that you solved the issue yourself!
I will go ahead and set your thread as [SOLVED] in order to help the other people who have the same issue.