Hi Ben, first, thanks for your patience, very much appreciated. I know how hard debugging can be, I'm helping with Enigmail If I have time to do so. I tried to write clearly but now see that I did not succeed:
> Based on your original report, giving a kernel log from the guest > (which has also been upgraded), I thought you were reporting an issue > triggered by upgrading the guest kernel. Now I think what you're > actually reporting is that upgrading the host kernel casues guests > to crash. Is that correct? No. Host and guests received the (unattended) upgrade but downgrading the _host_ (only) turned the system in a stable state. You might have spotted "Guests still are on 3.16.43-1" in my original report and deducted that the host seems to be the culprit. Well hidden, I agree. Sorry for that! So maybe you want to rephrase the bug title (again). While investigating when my guests did not start, I tried to start them using virsh --console - and received (nothing) for some minutes. Just as I was about to kill the terminal, there was that kernel panic messages. So I saved them, not aware by that time that I was the host's console messages being shown. (At least I now think that it was.) > were reporting an issue triggered by upgrading the guest kernel To clearify: The crash only happened upon rebooting the whole system. Unattended upgrade installed the new kernel but did not reload it. I rebooted due to a PHP and mySQL upgrade, to make sure new versions being active and that THEY would come up correctly upon reboot. > If so, can you check whether the host kernel logs anything when this > happens, and send that? Now, as it seems necessary what I can do (on the host) is to remove the APT Pin, apt update and upgrade, then boot, open a terminal from my laptop to the host (how do I make sure to get console output there?) and start some VM guests to make the host crash. Copy the console output from the terminal and revert all changes (re-activate pin, downgrade, reboot, fire up guests). Since I want to avoid having to do this multiple times, what exactly do I need to capture? > But I can't fix a bug if I don't understand what the bug is or how to > reproduce it! Thought you'd say that. I just hoped that the stuff I reported answering your remark "you cut too much" might already have helped. Olav
signature.asc
Description: OpenPGP digital signature
