Recent content by David Harvey

Superstar: 139674975354944:error:0906D06C:PEM routines:PEM_read_bio:no start line:../crypto/pem/pem_lib.c:686:Expecting: TRUSTED CERTIFICATE for /etc/pve/local/pve-ssl.pem I had only been monkeying with the per node ones pveproxy-ssl.pem which gives good/sane output from your openssl command...

One of the nodes in my cluster (5.4) has recently started spamming daemon.log and syslog with "unexpected SAN type encountered: 0" I updated the certs for the pveproxy several weeks ago across the 4 nodes, which worked, certs accepted, in date etc, but then today the spam commenced on a node. I...

The new packages have landed and looking good so far. My reboots are behaving again, so I've tentatively killed my watcher script which was force stopping and starting hung instances :)

Thanks for the update Fabian. If you have any test packages I'm happy to dpkg -i them on and try it out. I was moments away from paving my 5beta install and rolling back to 4.4, so if there are any other workarounds I could try to avoid nuking my install that would be most useful!

Hi zedicus, all, Do you know if LVM underneath a filesystem (as opposed to it accessed directly by proxmox) also causes this? I think i have observed the same with a Ubuntu VM after reinstalling to 5beta and changing storage setup as below. Basically, changing too many things at once to easily...

For giggles I tried the seabios-256 version from my working 4.something proxmox install (didn't work), and even the entire /usr/share/kvm directory from there in case of dependencies, and it still didn't behave, similar behaviour but more hanging on the proxmox splash boot screen..

Testing the SeaBIOS theory: I tried compiling a new version of SeaBIOS from git clone git://git.seabios.org/seabios.git seabios Dropped it into place at /usr/share/kvm/bios-256k.bin And it didn't fix the behaviour - although dmidecode on the guests did show it using the new BIOS 1.10 something...

I should also clarify, that going to single CPU, single core works reliably without making any ACPI changes for me...

Encouraged to hear I'm not the only one bitten by this. I get the same symptoms on a Dell poweredge r730 with BIOS Version: 2.0.1. Charles - disabling ACPI on the kernel line of grub, or in the proxmox VM options don't seem to help for me. In fact disabling ACPI through proxmox on a ubuntu test...