Search results

  1. F

    VirGL hardware accelerated h264/h265

    Hi, I'm trying to do the same things but failed. But I've noticed a things in guest VM: ferrets@LinuxMint:~$ lspci -nnk 00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] 00:01.0 VGA...
  2. F

    [SOLVED] Struggling with Proxmox EVPN with BGP

    As far as I know, Mikrotik RouterOS(v7.15) does not support EVPN.:oops:
  3. F

    VM CPU usage increased after proxmox upgrade from pve6.4 to pve7.0

    oh, if that is reason, I'm totally fine with it. I like lower power consumption( only if the max performance is the same as before).
  4. F

    VM CPU usage increased after proxmox upgrade from pve6.4 to pve7.0

    I've upgraded my proxmox ve from pve6.4 to pve7.0 last night and I found that the CPU usage of VMs had increased around 20%~40%, and I've total no idea what's the reason.
  5. F

    [SOLVED] SDN/VXLAN state "error" caused by ipv6 RA in vnet

    there is no ipv6 address configured in /etc/network/interfaces.d/sdn. the ipv6 address is assigned because theres is a vm running RouterOS sending RA, so maybe that's the problem. (btw, the 3 ipv6 addresses have different prefix that comes from my ISP that changes for a few times, sorry for...
  6. F

    [SOLVED] SDN/VXLAN state "error" caused by ipv6 RA in vnet

    you nail it! looks like it's some things wrong with ipv6 address. but it's still weird that ipv6 is working but report failed.
  7. F

    [SOLVED] SDN/VXLAN state "error" caused by ipv6 RA in vnet

    I've successfully installed SDN on my two Proxmox node and make it working. But I found that the SDN status on the GUI will becomes "avaliable" after I reload the network config for only a very short priorid of time, some time later, it becomes "error". The vm running on that vxlan is still be...
  8. F

    Error: parse_rfc_3339 failed - wrong length at line 1 column 60 (500)

    after upgrade to version 0.9, looks like the problem had been solved.
  9. F

    Error: parse_rfc_3339 failed - wrong length at line 1 column 60 (500)

    after remove encryption key and re added, no error seen.... maybe install a older package and upgrade to 0.8.21 can reproduce the problem?
  10. F

    Error: parse_rfc_3339 failed - wrong length at line 1 column 60 (500)

    nailed it! problem solved. thank you for the reply. and I think I have to redo all the backups.
  11. F

    Error: parse_rfc_3339 failed - wrong length at line 1 column 60 (500)

    root@pve2:~# pveversion -v proxmox-ve: 6.2-2 (running kernel: 5.4.60-1-pve) pve-manager: 6.2-12 (running version: 6.2-12/b287dd27) pve-kernel-5.4: 6.2-7 pve-kernel-helper: 6.2-7 pve-kernel-5.4.65-1-pve: 5.4.65-1 pve-kernel-5.4.60-1-pve: 5.4.60-2 pve-kernel-5.4.34-1-pve: 5.4.34-2 ceph-fuse...
  12. F

    Error: parse_rfc_3339 failed - wrong length at line 1 column 60 (500)

    I've met the same problem, backup task report error on pve cluster, like INFO: Finished Backup of VM 111 (00:00:05) INFO: Backup finished at 2020-10-02 01:45:08 ERROR: Backup job failed - upload log failed: Error: parse_rfc_3339 failed - wrong length at line 1 column 60 TASK ERROR: upload log...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!