Comment 27 for bug 570542

I had written: "How do you get the workaround above to work when the host won't boot?"

Duh! I just had to scroll down to the generics that were just off screen, so now I can install the workaround.

Selecting the package "linux-virtual" fortunately does not de-install linux-generic, but it does cause the host system's grub config to be updated to boot linux-virtual by default.

Was the current linux-virtual released without first trying to boot a host system? If someone had tried a simple "reboot" after installing linux-virtual, they would have noticed that the host could no longer boot! Unless they had manually installed the "workaround" as well, simply "knowing" that it was needed rather than relying on the dependency mwechanism.

Someone will probably respond that you are not supposed to install linux-virtual on a host machine. And it's probably even documented somewhere. But if that's the case, shouldn't there be some check performed to prevent (or at least warn about) it's installation on a host machine?