Search results

The 8.2.6 update fixed the issue for me. No problem with the backups running early this morning.

I also have this problem. I think I'm just going to do manual backups for a few days to see if the fix comes out. I only have 2 machines running the latest patches, so only a handful of backups need to be done.

You might try the latest 6.5 kernel. I think problems started in 6.8, but search and check. I am not using thunderbolt so my problems with 6.8 were different. The latest 6.8 is working for my issues, but I had to stick with 6.5 for a while due to issues in 6.8.

I believe there was at least one or two other threads related to thunderbolt issues on the 6.8 kernel. It's not something that affects me so I'm not up on it, but you might want to search for the other threads to see if there is anything useful there. I think downgrading the kernel and waiting...

There have been other reports of problems with the newest kernels. Just reinstalling you might end up with the same issue. You can google how to remove kernels in proxmox and find out how to remove it using dpkg and apt. Then you might want to search the forum and read about what issues people...

About a week. My intel mac mini is already updated to 6.8.8-2 with QEMU 9, also with no issues so far. My Ryzen machine is still on 6.8.8-1 with no issues. I plan on updating it to 6.8.8-2 with QEMU 9 in another day or two as long as I don't see any problems on the mini. I definitely had...

I have updated both my test server and my main server to the latest updates, 8.2.4 and 6.8.8-1 kernel, and so far no crashing or other issues noticed.

I had a freeze on a mac mini 2012 I run test vms on. I did the iommu=off fix on that machine and it has been fine since, but today I had a random reboot on my main server we use for our email and storage vms and it's not an intel. It's an AMD Ryzen that has been solid for a good while. I do...

I'm finding the new formatting of the backup notification emails to be less readable than what I get from version 7. The table formatting has the cell borders more flat and they seem to have no margin with the text. It looks better if I blow up the font size a bit, but it's definitely takes more...

IIRC the error on the screen at the time was systemd-journald.service failed to start or something like that. I'll have to check logs more thoroughly when I have some time and report back.

It's usually the result of a drive failing or beginning to fail. In this latest case there is an IO failure on the backup drive that was logged. SMART shows OK though and rerunning the backups worked fine. I suspect that the drive will flat out fail in the next few weeks or months so I am going...

Proxmox has been quite reliable for me but I have had issues from time to time. It's seems the most common issue I have is a backup failing for some reason. In some cases the backup fails because of a drive problem, and in other cases the issue is unknown. My latest failure I reboot and rerun...

Try manually importing the cert into the keychain and setting it to always trusted. It fixed it for me in Safari. I think my server updated it's cert or something recently and Safari wouldn't automatically trust the new certificate. I don't think this would be an issue with a non-self signed cert.

I believe my server updated it's ssl cert. Bypassing the warning and viewing the site anyway was apparently not enough to get Safari to allow the shell and console connections. I tried manually updating the certs on the server based on another thread but that didn't fix the issue either. After...

I just started getting this on one of my test servers, but not the other. I think it has something to do with the SSL certs, but running the update command I found from elsewhere on this forum did not help. I experience the message in Safari, but not Firefox. Not sure what is causing it yet.

I have not had any problems with my opnsense or freenas VMs other than the failure to boot as described in this thread and the problem with the qemu update and the q35 machine type. I'm now running i440fx with pci passthrough instead of pcie and everything is back to working fine as far as I can...

Ran the updates today which included the 5.3 kernel and it did indeed fix the issue for me as well.

Ditto. Just ran an update tonight and both my FreeBSD machines would hang on boot. kernel 5.0.21-5-pve and pve-qemu-kvm 4.1.1-1 I was able to get them to boot again by changing from host cpu type to kvm64. They both seem to be working now, but it remains to be seen if performance is affected...

I was under the impression that PCIE passthrough had to use q35 and it wouldn't work with i440fx.

I also could benefit from an ignore disk in the VM config so I could take a snapshot of a boot volume. I currently also exclude my passthrough disk from backup as it is itself a backup disk inside the VM. Luckily my boot volume is small and it's not that big of a deal to back it up before trying...