Recent content by FingerlessGloves

That's for sure the issue, hopefully that'll get fixed in the driver at some point, so whole computer doesn't start to lockup when there's no ethernet plugged in. It may already be fixed in a later kernel, but since it'll be in use 99% of the time, I've just excluded it from getting power managed.

Many hours of trial and error, I think I found the issue. Powertop was putting the i226 card in to a different power control mode to allow better power saving, but clearly when nothing is connected to the i226, the driver locks up. So I've now stopped it doing that and so far it's been stable as...

Example kernel reported hangs Oct 17 23:06:07 pve-1 kernel: INFO: task kworker/11:1:201 blocked for more than 122 seconds. Oct 17 23:06:07 pve-1 kernel: Tainted: P O 6.8.12-15-pve #1 Oct 17 23:06:07 pve-1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables...

strace of `ip address` execve("/usr/sbin/ip", ["ip", "address"], 0x7ffdf8653928 /* 17 vars */) = 0 brk(NULL) = 0x649ac8d2e000 mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x76d5b1a22000 access("/etc/ld.so.preload", R_OK) = -1...

I also did some strace's to hopefully hope show where the issue happens. strace of `ping google.com` strace ping google.com execve("/usr/bin/ping", ["ping", "google.com"], 0x7ffdeff82248 /* 17 vars */) = 0 brk(NULL) = 0x576275af1000 mmap(NULL, 8192...

I have a 2 node proxmox cluster running version 8.4.14, with a Raspberry Pi acting a as a qdevice for quorum. Kernel 6.8.12-15-pve I've taken pve-2 out of the datacentre to do some hardware work on it, and pve-1 had all the VMs running on it prior to powering it off. I then noticed my...

When I bulk migrate VMs from host to host, I always set Parallel Jobs to 1, due to only having 2.5gbit networking for the migration network. Sometimes I will catch Proxmox scheduling two migration jobs at once from the master bulk task. I think it might be due to having some VMs having HA and...

Hi, sorry I did mean "now". I have a bad habbit of typing not when I mean now. Below the task migrating the VM, it's saying cloudinit disk already exists for this VM. Which it might of done at the ZFS dataset level, since I had a host die and the HA started the replicated VM on the other host...

Err now it's created a new disk-1 and now thinks it's a normal disk image not cloudinit. Edit: Editing `102.conf` and hard changing it back to `local-zfs:vm-102-cloudinit,media=cdrom,size=4M` has allowed me to live migrate the VM again. After it migrated still showed `vm-102-cloudinit`

Indeed they all do. Ah if it'll get regenerated when it HA's across that'll be fine then.

Hi, I have two VMs which have cloudinit drives, which are failing to replicate over that drive, when a replication task is created, other VMs with cloudinit drives are replicating over fine but these two aren't. Granted those other VMs replication tasks were created months n months ago. Trying...

Update on this, I did try that and also been trying it on a Minisforum MS-A1, both replace and append. No luck either

I was hoping this would fix it on my Lenovo M920Q, but sadly even after appending it to my Lenovo it didn't make UEFI SecureBoot work. So I just disabled Secure Boot. Hopefully it'll help others. Proxmox: 8.2

Issue is upstream

Hi Mach, Disable the QEMU agent on the VM options, that'll allow the backup to run. I'm not sure if the issue is Debian or the MariaDB builds. If you could kindly report upstream links here that would be great, as I would love to get this fixed.