Search results

I'm looking for a way to execute commands in a container on a remote node. If I try "pct exec 100" I get: Configuration file 'nodes/pve-cl01/lxc/100.conf' does not exist Maybe it is possible to specify the path to the configuration file via extra-args? Or is it not possible using pct?

I'll just leave it here https://security.googleblog.com/2023/06/learnings-from-kctf-vrps-42-linux.html https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/4228112

The current version has SDN functionality in which you can configure vxlan connectivity. But still no support for OVSTunnel ports in webui...

I used scripts from this repository and built a client v1.0.11 in a Centos 6 environment with the glibc 2.12 library. The resulting client is successfully installed on the Centos 6.10 system, but when trying to perform a backup, the following error occurs: The error occurs when there are indeed...

You should use a range of values for "cpus" less than the value for "cores". For example: cores: 4 numa: 1 numa1: cpus=0-3,hostnodes=1,memory=4096,policy=bind

Good afternoon. I'm using PE 6.4 and I'm still getting 5.4 kernel updates, but not for 5.11 It is interesting to know: what is the status of the 5.11 kernel for pve 6.4 now?

I remember exactly that this question was discussed: https://forum.proxmox.com/threads/what-open-source-solutions-are-available-to-use-zfs-over-iscsi-with-proxmox.42461/post-228503 Well, yes, it may not have been sent to the mailing list...

Why is this patch not accepted in the upstream? This istgt has long been deprecated.

In this case, there is a similar implementation - this is portgroups (in bridge context). https://libvirt.org/formatnetwork.html#elementsPortgroup It would be nice to implement this functionality in PVE.

It seems to me that the problem may be in the iscsi configuration. Question is how iscsi is configured - via webgui or in the console with the iscsiadm command. I have this problem with the network shutting down before the iSCSI backend syncs when shutting down.

I am currently testing PBS (1.0 release) in my testing environment. Lights went off while backup job was running. When power supply was restored and servers were up again, I tried to delete incomplete backup from the list in storage. So the backup was deleted from the list, but chunks were not...

I guess you have to manually edit file /etc/proxmox-backup/datastore.cfg

I encountered this problem using regular and unprivileged containers. Is this related to apparmor job? If so, how can I configure the apparmor so that the elapsed time of processes is updated inside containers?

Just this week I encountered a similar problem on a single virtual machine (linux). In the course of finding out the reasons, it was found that the problem occurred due to the enabled memory option "ballooning device". This option is enabled by default and I just forgot to disable it.

At hetzner on the server, you can go to the bios (using kvm) and configure cstates.

All that has changed in pve6: is the blk-mq framework by default.

I tried disabling the blk-mq framework and it worked fine at first. This problem occurred again last night and this time I was able to track in zabbix exactly when it happened. After checking the logs, I found the event: Jul 16 04: 11:23 pve02 kernel: INFO: task md126_raid10:742 blocked for more...

For those who have these problems - do you use hardware raid?

Good afternoon. I encounter similar problems usually on old hardware (for example: intel xeon x3400 LGA1156). Most recently with kernel 5.4 I have never encountered such problems on more modern equipment.

what about ovs inport?