Search results

Thank you!

I have a Proxmox VE 7.2-7 setup. I have setup NFS storage and added a new backup plan. I found two retention settings in both Storage and in the Backup I created. I wonder what's the relationship will be between them? Thanks.

This happened again. I have to downgraded systemd to 246.6-1 for the network in the LXC container to work.

Thank you @Alwin, adding `lxc.mount.auto: sys` to /etc/pve/lxc/vmid.conf works!!

@moonman I'm surprised no one else seems to be complaining this issue, not even anyone is talking about it. Are we the only two users of LXC on the whole internet? This in my opinion should be a major issue and everyone should jump and shout, I expected.

Not sure, but hopefully and likely next few versions, if not next one version. I have filed bug in both the systemd Github project and systemd package in Arch Linux website.

You might want to remove the IgnorePkg after the next version of these packages are released.

Of course this is not a long term solution. Yeah, I'm the last one to know it.

I'm using Arch as containers and problem solved by: yay -U /var/cache/pacman/pkg/systemd-libs-244-1-x86\_64.pkg.tar.xz /var/cache/pacman/pkg/systemd-244-1-x86\_64.pkg.tar.xz

I use pvesh get /nodes/us000/openvz and pvesh get /nodes/us000/qemu to get OpenVZ and KVM vm status. It seems 0 is always returned for the KVM CPU usage, while reasonable values are returned for OpenVZ. So do I need to do anything to turn on KVM CPU usage for the pvesh command? Thanks.

It works!!! Thank you!!!

I have the same problem. Even if no rule is added, and everything set to ACCEPT. Enabling firewall still blocks pptp and gre traffic.

The version of Proxmox in concern is 3.4.11. I want to setup some IPv6 only OpenVZ containers where IPv4 is not available for CTs. I found it's not possible to put in IPv6 address as name server in the Proxmox web ui. Is there any way I can use IPv6 addresses as the CT's name servers?

Thanks for the reply Mr.Holmes.I have a routable /48. I want to assign each of my virtual machines with a /64 from my /48.

I'm playing with Hurricane Electric's IPv6 tunnelbroker and am running Proxmox with a hardware node and multiple vms. Now I managed to allocate IPv6 addresses from my /64 pool to the vms. Here is how I did it: On Hardware Node: auto he-ipv6 iface he-ipv6 inet6 v4tunnel...

Problem solved by removing the underscore. Not sure how that underscore ended up in that file.

Now I can reproduce the problem. It turned out when there is an underscore in the hostname, it guarantees to fail.

I found the problem, but not resolved yet. I found an error message from the GUI when I select a container: Error unable to parse config line: HOSTNAME="vpn_cn.yoctobox.com" (500) Then I temporarily removed that line from /etc/pve/nodes/pve/openvz/130.conf, then refresh the GUI, all nodes were...

Problem found, but not solved yet. I found one of the container shows: Error unable to parse config line: HOSTNAME="vpn_cn.yoctobox.com" (500) Then I temporarily removed that line from /etc/pve/nodes/pve/openvz/130.conf. All OpenVZ containers were shown correctly. It seems this file is broken.

Apparently the API failed to fetch more details about the OpenVZ containers. So where does the API get the running status info of the OpenVZ containers? From database? Or from files? I believe the OpenVZ running status info is frequently updated as it contains CPU, disk and memory usage info...