Search results

Installed the updates from pve-enterprise with active subscription but there's no checkbox for PCID anywhere to be seen. What did I do wrong?

Crashed my home testing server – well, prevented it from booting to be more precise. Guess I'll wait for some more testing before rolling it out in productive

Any news on when there's going to be an official update released? With all the info surfacing now, it seems to be a massive risk for all of us running VM environments.

Yes so did mine after a while but when I was watching it filling up the last few % then it suddenly hang (the UX / SSH) and I could either wait for like 1-3 hours for it to automatically reboot or reboot it forcefully. Either way, right after the system came back online, the RAM usage started...

As I said, I limited RAM usage already but it didn't change anything at all.

That was exactly my problem with ZFS as well though on a PX61 machine. Limited RAM usage but it went ahead, filled up all RAM and then just stalled. No recovery possible until the server was forcefully rebooted. Then decided to ditch ZFS as I can't have this uncontrolled behavior. Tested on...

Ran the update last night, so far no problems anymore..

Alright, just saw that line "Hit return to proceed..." and knew why :) Sorry for the dumb question :)

Why do I have to omit the description? Will this spam the log or why is it?

Have the latest kernel installed right now, did the reboot like 12 hours ago and so far, everything runs smoothly. Also, all VMs could be restartet several times without ending in lock up but since this is hard to reproduce anyway, I'll have to keep an eye on the situation if it ever locks up...

Wow great! Thank you so much :-) Will try this right now. Have a nice weekend!

Hm a spice viewer? Help me out here, does this software have some kind of backup feature?

Yes, I know that, but we're talking only about the backup of proxmox itself, not VMs as they're already backed up separately. As I said, I only need the main proxmox configuration to be backed up without any kind of VM backup.

Thank you so much :) This is perfect! Exactly what I was looking for! Only one question, why does everything has to be shut down? Is this necessary for each run?

That is nice but if you don't have an additional node available that's out of the question again. I basically only need a solution to backup proxmox itself, not the vms as they're already backed up anyway. I do use LVM by the way, no ZFS.

Please do :)

I don't know how you can do that but I'm not sure that's a good idea at all. Your host might come to a crawl with all backup processes running at the same time. Also, having multiple backups run at the same time, leeching from the same storage will have negative impact on I/O probably making the...

I was wondering the other day... Since I do backups of all my VMs every night, what the best practice would be to backup the main files of the proxmox host itself. Let's say there's a fatal failure on a single node where the drives crash and one has to rebuild the proxmox host on new hardware...

Have you considered running fstrim -av inside the vm? This should mark deleted blocks as free again, making the vmdisk image as large as it really is. I have fstrim run each night before backing up the vm itself to remote storage to only have the disk images as large as necessary. Give it a...

Alright, I tried the downgrade to 4.10 but it didn't help at all. The problem is, that there is no way to reliably reproduce the problem. Sometimes the machine just reboots as intended, sometimes it just hangs with 100% cpu load and a black console screen, no log output, no console output, no...