Search results

Moin, was war hier die Lösung? Habe vmtl exakt das gleiche Problem https://forum.proxmox.com/threads/smb-cifs-backup-job-stuck.142066/

Hey, we have an interesting problem in our proxmox cluster. Two nodes have a backup job set up, which does back up to a Windows Veeam server in a remote datacenter every night. On the proxmox4 node the backup does run just fine, but on the proxmox2 node we sometimes face a problem during the...

root@proxmox2:~# umount -f -l /mnt/pve/<<mount point>> && vzdump --stop stopping backup process 2428713 failed Doesnt work for me. Its a SMB/CIFS share too :(

The closest common ancestor for EPYC 7352 and 9XXX would be EPYC-Rome. What would it be for EPYC 7352 and Ryzen 9 7950X?

We are planning to add a new hypervisor to our cluster. Three existing nodes have an AMD EPYC 7352 CPU and now we are unsure if we should go with the latest EPYC 9XXX processor or if we should stick with EPYC 7352 for the new server. I have already tested the migration from EPYC 7352 to Ryzen 9...

Hey, I get these errors staring a vm on Proxmox Virtual Environment 7.1-6, after upgrading fedora server from 30 to 32: ERROR: for <container X> Cannot start service <container X>: Unknown runtime specified oci ERROR: for <container X> Cannot start service <container X>: OCI runtime create...

No im not live migrating. Im currently using kvm64. Which cpu type would you recommend for ryzen? EPYC, host or kvm64?

The same crash happend again on the fedora server vm. It had to be anywhere between 19:15 and 21:30, after running fine for ~7 hours. I almost thought i fixed the problem because i disabled cool'n'quiet in bios (ryzen), but it seemed to not cause these issues. I ran memtest ~1 month ago when i...

This time a fedora server vm crashed, after running fine for ~2 days

And my VM crashed again this night....

Yeah, had to set breaks manually, the orignial file looks fine. Sry

root@pve:~# qm config 200 agent: 1 boot: cdn bootdisk: virtio1 cores: 4 memory: 2048 name: UbuntuPlex net0: virtio=C6:A3:8B:9A:23:BD,bridge=vmbr0,firewall=1 numa: 0 ostype: l26 scsihw: virtio-scsi-pci smbios1: uuid=e0ea3f3e-4b9b-4407-9126-08686294cd86 sockets: 1 unused0...

This error occured on the vm yesterday yesterday evening

First, the bios is on the newest version. I took my time and tried 3 kernels. F 4.15.18-13-pve with custom debian installation and proxmox on top (like described in the wiki). Then i installed a custom kernel 4.19, but the problem continued. After testing both kernels for 2+ days, i reinstalled...

No idea?

Hey all, im having big problems on my proxmox (single node) box. I run 2 ubuntu 18 server vms, with a few docker container inside. On these vms i often get these kind of errors. Then the whole vm stops and needs to be restartet. Sometimes my proxmox host stops resonding too. Any idea what...

Wow, thanks. I have been trying to fix this for way to long on my ryzen 2200g. Thanks!