我跑apt-get dist-upgrade如下：
Calculating upgrade... Done
The following NEW packages will be installed:
linux-headers-3.19.0-51 linux-headers-3.19.0-51-generic
linux-image-3.19.0-51-generic linux-image-extra-3.19.0-51-generic
The following packages will be upgraded:
linux-generic-lts-vivid linux-headers-generic-lts-vivid
linux-image-generic-lts-vivid
3 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 65.1 MB of archives.
After this operation, 288 MB of additional disk space will be used.
Setting up linux-image-generic-lts-vivid (3.19.0.51.36) ...
Setting up linux-headers-3.19.0-51 (3.19.0-51.57~14.04.1) ...
Setting up linux-headers-3.19.0-51-generic (3.19.0-51.57~14.04.1) ...
Setting up linux-headers-generic-lts-vivid (3.19.0.51.36) ...
Setting up linux-generic-lts-vivid (3.19.0.51.36) ...
在此之后，Ubuntu 14.04.4 x64 LTS 无法正确启动并在此屏幕上挂起：
这发生在我正在尝试的所有虚拟机上。我可以通过创建/还原快照来重现它。
更新：这是/var/log/boot.log通过 GRUB 中的高级引导选项使用以前的内核引导后的内容：
* Stopping Read required files in advance [ OK ]
* Starting Mount filesystems on boot [ OK ]
* Starting Populate /dev filesystem [ OK ]
* Starting Populate and link to /run filesystem [ OK ]
* Stopping Populate /dev filesystem [ OK ]
* Stopping Populate and link to /run filesystem [ OK ]
* Stopping Track if upstart is running in a container [ OK ]
* Starting Initialize or finalize resolvconf [ OK ]
* Starting Signal sysvinit that the rootfs is mounted [ OK ]
* Starting mount available cgroup filesystems [ OK ]
* Starting set console keymap [ OK ]
* Starting Signal sysvinit that virtual filesystems are mounted [ OK ]
* Starting Signal sysvinit that virtual filesystems are mounted [ OK ]
* Starting Bridge udev events into upstart [ OK ]
* Starting Signal sysvinit that remote filesystems are mounted [ OK ]
* Stopping set console keymap [ OK ]
* Starting Clean /tmp directory [ OK ]
* Stopping Clean /tmp directory [ OK ]
* Starting Signal sysvinit that local filesystems are mounted [ OK ]
* Starting device node and kernel event manager [ OK ]
* Starting D-Bus system message bus [ OK ]
* Starting flush early job output to logs [ OK ]
* Stopping Mount filesystems on boot [ OK ]
* Stopping flush early job output to logs [ OK ]
* Starting load modules from /etc/modules [ OK ]
* Starting cold plug devices [ OK ]
* Starting log initial device creation [ OK ]
* Starting SystemD login management service [ OK ]
* Stopping load modules from /etc/modules [ OK ]
* Starting system logging daemon [ OK ]
* Starting mDNS/DNS-SD daemon [ OK ]
* Starting bluetooth daemon [ OK ]
* Starting Reload cups, upon starting avahi-daemon to make sure remote q[ OK ]are populated
* Stopping Reload cups, upon starting avahi-daemon to make sure remote q[ OK ]are populated
* Starting Bridge file events into upstart [ OK ]
* Starting Uncomplicated firewall [ OK ]
* Starting configure network device security [ OK ]
* Starting configure network device [ OK ]
* Starting configure network device security [ OK ]
* Starting Mount network filesystems [ OK ]
* Starting Failsafe Boot Delay [ OK ]
* Stopping Failsafe Boot Delay [ OK ]
* Stopping Mount network filesystems [ OK ]
* Starting System V initialisation compatibility [ OK ]
* Starting modem connection manager [ OK ]
* Starting configure network device security [ OK ]
* Starting configure network device [ OK ]
* Starting userspace bootsplash [ OK ]
* Starting network connection manager [ OK ]
* Stopping userspace bootsplash [ OK ]
* Starting Send an event to indicate plymouth is up [ OK ]
* Stopping Send an event to indicate plymouth is up [ OK ]
* Starting Bridge socket events into upstart [ OK ]
Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
* Starting AppArmor profiles [ OK ]
* Setting up X socket directories... [ OK ]
* Stopping System V initialisation compatibility [ OK ]
* speech-dispatcher disabled; edit /etc/default/speech-dispatcher
* Starting System V runlevel compatibility [ OK ]
* Starting Restore Sound Card State [ OK ]
* Starting regular background program processing daemon [ OK ]
* Starting anac(h)ronistic cron [ OK ]
* Starting save kernel messages [ OK ]
* Starting configure network device security [ OK ]
* Starting CPU interrupts balancing daemon [ OK ]
* Starting Restore Sound Card State [fail]
* Starting crash report submission daemon [ OK ]
* Stopping save kernel messages [ OK ]
* Stopping anac(h)ronistic cron [ OK ]
* Stopping Restore Sound Card State [ OK ]
* Starting automatic crash report generation [ OK ]
* Starting cups-browsed - Bonjour remote printer browsing daemon [ OK ]
* Starting configure virtual network devices [ OK ]
Starting VirtualBox kernel modules * Stopping cold plug devices [ OK ]
* Stopping log initial device creation [ OK ]
* Starting save udev log and update rules [ OK ]
* Stopping save udev log and update rules [ OK ]
...done.
在 Ubuntu 论坛上，至少有一个线程显示我的问题是由最新的 Ubuntu 内核更新（linux-image-extra-3.19.0-51-generic）引起的：
http://ubuntuforums.org/showthread.php?t=2314723
更新：
@alexmurray 在https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1550090提交了一个错误（已经确认）
如果您受到影响，请在那里投票（请不要在这里创建“我也是”的答案）。
更新：
由固定
3.19.0-51.58~14.04.1我有同样的问题并恢复到旧内核。
按住Shift启动并选择高级选项，然后选择较旧的内核（注意最新的内核是什么）。这将允许您进入 Ubuntu 桌面。
从那里打开突触包管理器。找到
linux-image-3.19.0-51-generic（或您安装的最新内核）。右键单击并选择“标记为删除”。
应用并重新启动。
我没有记录启动文本信息，但遇到了类似的问题（Windows 7 64 位主机 VMware Workstation 12 Player），最初是我使用了一段时间的 15.10 Wily Werewolf VM。几天前安装最新更新后，我的虚拟机无法启动并卡在黑屏上。我试图通过从我之前使用的 .iso 创建一个新的 14.04.3 LTS VM 来解决这个问题。这个来宾虚拟机工作正常，直到我更新它，然后它也无法启动。因此，我再次尝试了新安装的 15.10 来宾 VM，果然，这似乎是最新更新中的原因（因为我尝试的 2 个 VM 具有不同的内核 - 我需要更高版本的内核来支持 USB 3.0 功能）。