Search results

Hi! I'm trying to recreate one of my windows templates which used the OVMF bios with a set resolution of 1920x1080. The problem I'm having with this new VM is after I set the resolution to 1920x1080 from within the bios it resets back to 800x600 on boot. If I check the bios the resolution says...

That could work. I have enough disk space. Theoretically, I shouldn't have any more problems with new templates right? It would be great to not have to redo my templates, but I wouldn't mind it if that fixed the issue. I did a little test and created a new VM template much like the other ones...

Hi! Sorry for the long gap in between responses. Thanks for the blocksize tip for windows by the way! For your first question, yes. I could delete the old templates and use the working cloned ones. However, I have a few linked clones using the templates. Is there a way I could switch which...

Sure. Here's the output Link: Pastebin (It was too long to put in a spoiler)

Hm. It seems I'm not able to reproduce the error with VMs, however, I'm still getting the old error message with my current VM templates. I created a new vm and converted that to a template and tried to back it up a few times and still couldn't reproduce the error. I also made a full clone of a...

Thanks for applying the patch for me! This makes my life easier. I installed it and overwrote the previous version by doing: dpkg -i --force-overwrite ./pve-qemu-kvm_4.1.1-4_amd64.deb and restarted. However, when I backup and encounter the error I don't receive any extra output (I also looked...

I tried working with the pve-qemu repository to patch it and build it myself, although that didn't work out too well. Do you know when the pve-qemu package in the test repository will be updated with the patch?

Thanks so much! I’ll let you know what happens with the extra output. Hopefully that will help solve this issue

UPDATE: I successfully updated to Proxmxo VE 6, although I still get the error :/ Also here is the output from syslog. Not sure if it really adds anything else. The problem also seems to have gotten worse. When I do an automated backup I used to get 2 or 3 VMs erroring out because of this...

My last reboot has been 9 days ago. I'll try what you suggested and see how it goes. It's probably a good idea to at least start planning an upgrade to version 6 before 5 reaches end of life

I could look at upgrading to version 6. How stable is the upgrade process? One concern I have is the use of a new Linux kernel. I'm currently on kernel version 5.4-5 (4.15.18-25) and whenever I try to upgrade to 5.4-13 (4.15.18-53) I run into a few problems with GPU-Passthrough and a few other...

Here's the output from dmesg -w after experiencing the error. Let me know if you want the output from before as well [573759.620615] traps: vma[28290] trap int3 ip:7f8ce1db3261 sp:7ffe8c129c90 error:0 in libglib-2.0.so.0.5000.3[7f8ce1d63000+112000] I should probably also specify that this...

Yes. Backing up to my local disk works fine

Hi! I'm also getting this error as well. Did you ever find a fix for it?

Hi! I set up automated backups for my VM templates and during the backup, several templates encountered this error. I tried backing them up manually and also received the same error. For the backup mode, I'm using stop and for the compression, I'm using GZIP. When I switch the mode to snapshot...

Managed to solve the issue. Not gonna lie, it was a pretty dumb mistake on my part. I use Proxmox as a home server and I forgot to port forward port 80 on my router and hook it up to the internal ip of Proxmox. Hence why an outside connection couldn’t connect to it on port 80.

Still running into the same issues. I'm not really sure what could be causing this to happen. Any ideas?

Hi. I'm trying to order a certificate using the ACME GUI and I keep running into an error when validating the challenge. Loading ACME account details Placing ACME order Order URL: [REDACTED] Getting authorization details from '[REDACTED]' ... pending! Setting up webserver Triggering validation...

Alright, so that sounds about what should be expected then. I guess it must have to do something with the config of the container since all other containers don't seem to be having that problem. I guess that wraps it up. Thanks for the help!

Here's with the container running: 000000003ec2d6b2: 00000002 00000000 00010000 0001 01 1549226 @/var/lib/lxc/122/command 000000004b1b8e2c: 00000003 00000000 00000000 0001 03 1540558 @/var/lib/lxc/122/command and here's right after I press stop: 000000004b1b8e2c: 00000002 00000000 00000000...