Happened to me today after stopping a manual snapshot task because I forgot to uncheck RAM while it was writing RAM to disk.
The vm remained killed and locked. The snapshot also remained in snapshot list but NOW was not shown as child.
After `qm...
Thank you @fiona for your interest.
lscpu of source machine:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 46 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s)...
I've learned "the hard way" why the "host" type is not always the best solution. QEMU states this also in their documentation that "host pass through" may cause issues with live migration.
That could come from using type host, it sometimes exposes a bit more CPU state than KVM can control, so a migration gets some state, like the Machine-Specific Register (MSR) values in your case, that then cannot be set on the target. Could also...
I've checked the log at the destination host:
mar 11 12:50:58 [target_node] QEMU[723971]: kvm: error: failed to set MSR 0x38f to 0x7000000ff
mar 11 12:50:58 [target_node] QEMU[723971]: kvm: ../target/i386/kvm/kvm.c:3213: kvm_buf_set_msrs...
I've experienced the same scenario again. I'm also using the "host" processor type. Both nodes have identical CPU.
I've updated the destination host before migration. So it went from old to the new one.
I've tried also to upgrade both nodes...
Restart the server itself?
You can either do that via the GUI (top right if the server itself is selected in the tree list on the left) or with reboot or systemctl reboot
Thank you so much for this. I've registered on this forum specifically to thank you @primetechguides for this excellent guide.
I have had a little trouble getting the 'debianboot' boot option to stick/be persistent, but that is a small price to...
The "issue" of the autoscaler not being able to calculate the optimal number of PGs is as soon as you have at least one pool using a device specific rule, while there is another pool using a rule that does not select a device class.
So once you...