Search results

Booted install iso and switch to tty1 w/Ctrl-Alt-F1 and to a prompt w/Ctrl-C and find my logical volume but no device nodes for them, so impossible to mount them :( see attach image n3_lvs.jpg, n3_bootfailure.jpg shows the failure to mount boot after getting a NMI during grub install of a new...

Only when selected and boot debug mode from install iso, my USB keyboard doesn't work at all :(

Just lost one of my pve4.1 HP DL360 G9 hypervisor nodes as it got shot by HP' ASR/NMI during apt-get dist-upgrade when installing a new kernel/running grub (which takes too long most properly due to tasting all our iSCSI devices). Booting it now just makes the kernel crash. This is so annoying...

Normally hashed out under /var/log/pve/tasks

Bugger, saw this too late, already patched all hypervisor nodes by migrating my VMs offline :/ Hopefully a fix/path for others ending up in this senario. Currently live migration seems to work again with all nodes patched & rebooted. But any potential value of this patch compared w/currentl...

Maybe a bug in qemu-kvm 2.4.4, as sometimes it also lock-ups on any connection to a VM running in this version, thus only remediation seems to shut it with a stop OP...

From oldhost 2 oldhost, it worked fine as w/secure migration: Feb 18 13:51:05 starting migration of VM 204 to node 'n5' (10.45.71.5) Feb 18 13:51:05 copying disk images Feb 18 13:51:05 starting VM 204 on remote node 'n5' Feb 18 13:51:10 starting ssh migration tunnel Feb 18 13:51:11 starting...

with datacenter.migration_unsecure:1 it still fails from oldhost to newhost: task started by HA resource agent Feb 18 13:48:13 starting migration of VM 204 to node 'n2' (10.45.71.2) Feb 18 13:48:13 copying disk images Feb 18 13:48:13 starting VM 204 on remote node 'n2' Feb 18 13:48:19 starting...

This has 'always' been issued in pve 4.x, see other posts about this, migration still works :) Not using ssh will it try rsh, which properly doesn't work between my nodes? I still see the migration failure between 'old' hosts as of last patch yesterday (qemu-kvm 2.4.4), before not.

I also see it randomly (not every time) between oldhosts (patched yesterday with glibc issue) so it's not tied to qemu-kvm 2.5 vs 2.4... alone root@n2:~# pveversion -verbose proxmox-ve: 4.1-34 (running kernel: 4.2.6-1-pve) pve-manager: 4.1-5 (running version: 4.1-5/f910ef5c)...