Recent content by ferrets

How about doing dd with partition? Or can you run the software in LXC container that you need?

You've found the final piece of the puzzle! Maybe we'll see this feature in Proxmox VE 8.4!

There is a patch written by huang rui, but it's not merge by qemu, or there is no pull request at all. Can proxmox add this patch to proxmox-qemu?

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...

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

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).

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.

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...

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.

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...

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

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?

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

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...

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...