Search results

After stopping and restarting container, backup in suspend mode works fine....

Hi, tryng to backup (suspend) on local storage one of my container i noticed: INFO: suspend vm INFO: lxc-freeze: 121: freezer.c: do_freeze_thaw: 54 Failed to freeze 121 INFO: lxc-freeze: 121: tools/lxc_freeze.c: main: 89 Failed to freeze /var/lib/lxc:121 ERROR: Backup of VM 121 failed -...

if i use a common bridge on one node all works fine, it seems some misconfiguration on gre tunnel.... someone has tested some private lan for VM shared between several cluster nodes?

Hi, i'm trying to set a private network for some of my VM and i'm trying using an ovs gre tunnel i found this: https://documentation.online.net/en/dedicated-server/tutorials/network/rpn-proxmox-openvswitch auto vmbr1 iface vmbr1 inet manual ovs_type OVSBridge post-up...

Ok, my mistake is thinking in mbit and not in MB (megabytes)

[ 4] local 80.21.47.149 port 46036 connected to 80.21.47.146 port 5201 Starting Test: protocol: TCP, 1 streams, 131072 byte blocks, omitting 0 seconds, 50 second test [ ID] Interval Transfer Bandwidth Retr Cwnd [ 4] 0.00-2.00 sec 117 MBytes 492 Mbits/sec 4631...

HI, Proxmox VE 6.1-8 with new kernel 5.4 two linux container in two different cluster nodes Rate Limit tested with iperf3 doesn't work net0: name=eth0,bridge=vmbr0,firewall=1,gw=xx.xx.xx.xx,hwaddr=XX:XX:XX:XX:XX:XX,ip=xxx.xxx.xxx.xxx/25,rate=200,tag=1000,type=veth configuration file are...

yes, problem was default RAM selection.

:~# qm config 132 agent: 1 bootdisk: scsi0 cores: 1 ide2: local:iso/CentOS-8.1.1911-x86_64-boot.iso,media=cdrom memory: 512 name: centos8 net0: virtio=86:76:A0:20:7B:8B,bridge=vmbr0,firewall=1,tag=200 numa: 0 ostype: l26 scsi0: local:132/vm-132-disk-0.qcow2,size=32G scsihw: virtio-scsi-pci...

Hi, i'm trying to install Centos 8 VM in a proxmox ve environment but installation fail (with dvd iso and netinstall iso) Plymouth fail to start all end with "failed to start Switch Root"

No it seems all ok....and today disappeared...

i don't use GRE or PPTP but after upgrading to 6 syslog show that warning...

Hi, after upgrading to proxmox 6 from 5.4 i find in syslog: Aug 6 10:44:31 ********** lxcfs[1265]: bindings.c: 4526: cpuview_proc_stat: cpu7 from /lxc/116/ns has unexpected cpu time: 22174 in /proc/stat, 22450 in cpuacct.usage_all; unable to determine idle time Aug 6 10:44:31 **********...

Hi, after upgrading from 5.4 to 6 i find on syslog: kernel: [ 1226.689221] conntrack: generic helper won't handle protocol 47. Please consider loading the specific helper module. Why? some hints?

...ok....and why pve5to6 show "FAIL"? All my hostnames are resolvable.

a consideration about pve5to6: FAIL: ring0_addr 'srv3' of node 'srv3' is not an IP address, consider replacing it with the currently resolved IP address. is it correct? i always used hostname (resolved by system and dns) instead using private ip

OK i'll open an enhancement request for pvesr.service Other 3 servers use 1G interface and i'm pretty sure Huawei servers are update but i'll check Thanks

and one question: Is there a reason for not using systemd-networkd for proxmox network configuration?

just for information, my cluster is made by 5 server with the same configuration 3 HP and 2 Huawei only 2 huawei server have the same problem (huawei server have 10GBE ethernet card)

Hi, changing interfaces configuration doesn't solve the problem during boot i see: FAILED TO START PROXMOX VE REPLICATION RUNNER in my opinion pvesr.service start before network is ready: root@**********:~# journalctl | grep pvesr May 03 07:41:01 ********** pvesr[2076]: ipcc_send_rec[1]...