Search results

Great to hear! You can now also try to set iso_download_pve to true. This allows the PVE node to handle the ISO download itself and avoids re-downloading the ISO if a file with matching checksum and filename is already present...

You're using the plugin built into Packer itself, which doesn't contain the fixes of version 1.1.2 (yet). 1. You have to specify the builder type. In your case you have to use proxmox-iso instead of proxmox. Using only proxmox will always load the plugin built into Packer and not the specified...

Please post your Packer template, including the packer {...} block.

With the latest Packer plugin release this issue should finally be fixed: https://github.com/hashicorp/packer-plugin-proxmox/releases/tag/v1.1.2

The mentioned patches seem to be in the Ubuntu Disco kernel already: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840750 So this has to be something else.

I ran memtest86+ twice without errors. I searched a bit and and found the following lkml thread: https://lkml.org/lkml/2019/6/5/274 Since I can't interpret kernel traces, I don't know if this is related. I did a quick test, however. I set up two VWs: vanilla Debian Buster (Kernel: #1 SMP...

Thanks for your reply - I'll run memtest86 on the board tomorrow.

I got another one today, this time it said kernel tried to execute NX-protected page - exploit attempt? (uid: 0) before the crash any idea what that means? I found this thread, but the link there doesn't work for me. the complete syslog of the event: I don't think that it's related to the...

pveversion -v : proxmox-ve: 6.0-2 (running kernel: 5.0.21-2-pve) pve-manager: 6.0-7 (running version: 6.0-7/28984024) pve-kernel-5.0: 6.0-8 pve-kernel-helper: 6.0-8 pve-kernel-5.0.21-2-pve: 5.0.21-3 pve-kernel-5.0.21-1-pve: 5.0.21-2 pve-kernel-5.0.18-1-pve: 5.0.18-3 ceph-fuse...

I run Proxmox on a PCEngines APU2C4 (Firmware v4.10.0.1) and get kernel crashes every few days. Sometimes the system gets unresponsive and all that helps is a hard reset, sometimes I can still ssh into it or log in via serial console. Here is a stack trace I was able to get: [29606.593925] kvm...