Unable to reboot after trying to install KVM
 

Hi.

I'm running Ubuntu 17. Here is the output to uname -a. Linux hellodolly 4.13.0-36-generic #40-Ubuntu SMP Feb 16 20:07:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

I decided to switch to KVM from VirtualBox. So I first searched dpkg -l for Virtualbox* and purged it. After that, the package manager said I still had some unnecessary files and encouraged me to autoremove them, which I did. The programs were: virtualbox-dkms, dkms, libvnc server, and libgsoap-2.8.49

After that I rebooted and during the part of the boot where there are green [OK] notices, there was a [Failed] notice which said "Failed to start AppArmor initialization. See 'systemctl status apparmor.service' for details. Also, the screen flashed several times and then froze. If I didn't wait too long, Ctl-Alt-Delete would work, but if I wanted longer, the only way to get out of the situation was to push the power button.

I can still execute some commands from recovery mode. So, the relevant parts of that command's output is as follows:

Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor preset:
Active: inactive (dead)
...

At first I tried removing the apparmor file from /etc/init.d. That changed the nature of the boot, but in the end the same flashing and then freeze happened (maybe there was a different number of flashes).

Can anyone tell me the cause of this and how to get my system to boot again?

Thanks

Can you load prior kernel on boot?

Hi Jefro.

Please clarify what it means to load prior kernel on boot.

Did you change the kernel for the KVM install? Usually distro's keep various prior kernels available and you can sometimes catch it at boot or select it in grub.

No I didn't change the kernel. I'm not even sure that the KVM was the cause of the problem, it's just the last thing I did before I rebooted.

I accessed the recovery mode through, the grub menu. There I saw other options.

Do you know how I would try to debug this problem with AppArmor?

I'm not overly confident that that is the problem but you can chase it down. Consider looking at all logs too in /var for clues.

See this maybe should work. https://help.ubuntu.com/community/AppArmor