With the post-meltdown kernel (BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic) labvirt1018 can't connect to its network:
* Starting set console font [ OK ] * Stopping set console font [ OK ] * Starting userspace bootsplash [ OK ] * Starting Send an event to indicate plymouth is up [ OK ] * Stopping userspace bootsplash [ OK ] * Starting configure virtual network devices [ OK ] * Stopping Send an event to indicate plymouth is up [ OK ] Waiting for network configuration... Waiting up to 60 more seconds for network configuration... Booting system without full network configuration... * Stopping Failsafe Boot Delay [ OK ] * Starting System V initialisation compatibility
We've seen this before, which is why we pinned the lucky kernel version 4.4.0-81-generic. The networking issue occurred sometimes in kernels older and newer depending, although it seems like newer hardware in cases needed the extra package for drivers.
labtestvirt2002 as a guinea pig (3.13 variant too):
linux-image-generic-lts-xenial => linux-image-4.4.0-109-generic{a} linux-image-extra-4.4.0-109-generic{a} linux-image-generic-lts-xenial
apt-get install -y linux-image-4.4.0-109-generic linux-image-extra-4.4.0-109-generic linux-lts-xenial-tools-4.4.0-109 linux-tools-4.4.0-109-generic
...reboots into grub prompt...
grub>
I can get out of it by going back to older 4.4.0-81-generic
aptitude remove --purge linux-image-4.4.0-109-generic
...reboots fine...
I think linux-image-4.4.0-109-generic is right even though https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown?_ga=2.45330468.1075164870.1515518269-114292014.1505251686 notes linux-lts-xenial 4.4.0-108.131~14.04.1 Trusty 14.04 because https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741934/comments/17 was already filed and fixed bumping the correct version even though the docs are not updated?