Failed to boot when install ubuntu16.04 beta2 desktop64 with EFI boot in Vmware ESXi

[vmware-gos-Yuhua]

I insatlled Ubuntu16.04 beta2 desktop (64bit) with EFI boot on VMware ESXi 6.0.0 build 2494585, ESXi 5.5.0 build 3029944, and the on-going develop branch vsphere2016. When finish installation and reboot, I notice this on boot:

/dev/sda2: recovering journal
/dev/sda2: clean, 184027/950272 files, 1023281/3801088 blocks

And then it hangs right there. It happens every time I reboot the VM.

WORKAROUND: Change boot mode from EFI to BIOS.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1566708/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1566708

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[vmware-gos-Yuhua (yhzou)]

The system can not boot up. So I can't use the command to collect logs in terminal.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.6 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc4-wily/

[Joseph Salisbury (jsalisbury)]

To test the mainline kernel, you may need to first boot in legacy mode. Then install the kernel and see if it can reboot in EFI mode.

[vmware-gos-Yuhua (yhzou)]

After insatlled Ubuntu16.04 beta2 desktop (64bit) with EFI boot on a VMware ESXi, I change it to boot with legacy bios and encouter
the same issue as follows:

/dev/sda2: recovering journal
/dev/sda2: clean, 184027/950272 files, 1023281/3801088 blocks

And then it hangs right there.

So I can not login to the system and replace the kernel as your suggestion.

[vmware-gos-Yuhua (yhzou)]

Ubuntu 16.04 GA use kernel 4.4.0-21-generic. Any plan for updating kernel to latest version for Ubuntu 16.04 LTS ?

best regards
Yuhua Zou

[Michael Shi (mklnz)]

I'm having the same issue, with the release build of 16.04 LTS as well. I'm using it on vSphere 6.0 U2, 14.04 LTS has always worked fine using EFI.

[vmware-gos-Yuhua (yhzou)]

I insatlled Ubuntu16.04 beta2/GA Server (64bit) with EFI boot on a VMware ESXi. This issue doesn't exist.
So I encounter this issue only with desktop version. It seems like it's not caused by kernel.

[penalvch (penalvch)]

Yuhua Zou, could you please advise to the following:
1) What version of ESXi are you using precisely?
2) Is the BIOS set for the VM to be EFI or BIOS mode?

[Michael Shi (mklnz)]

@penalvch

Not sure about Yuhua, but I'm using ESXi 6.0.0, build 3620759.

Boot mode set to EFI. Bios mode works, this only affects booting under EFI mode.

[vmware-gos-Yuhua (yhzou)]

1) What version of ESXi are you using precisely?

   I encounter this issue in ESXi 6.0.0 build 2494585, ESXi 5.5.0 build 3029944 and the on-going develop branch vsphere2016.

2) Is the BIOS set for the VM to be EFI or BIOS mode?

   Boot mode set to EFI.
   It works fine when boot mode set to BIOS.

best regards
Yuhua Zou

[vmware-gos-Yuhua (yhzou)]

It still exists for Ubuntu16.04.1 desktop64 when test in ESXi 6.5.0 4158008

[vmware-gos-Yuhua (yhzou)]

This issue disappear for Ubuntu16.10-desktop64 when test ESX6.0GA and ESXi6.5 build 4491798.

[vmware-gos-Yuhua (yhzou)]

This issue disappear for Ubuntu16.10-desktop64-beta2 when test ESX6.0GA and ESXi6.5 build 4491798.

[penalvch (penalvch)]

Yuhua Zou, would you need a backport to a release prior to 16.10 or may this report be closed?

[vmware-gos-Yuhua (yhzou)]

It'will be better to have a backport to ubuntu16.04 updates.

best regards
Yuhua Zou

[penalvch (penalvch)]

Yuhua Zou, I am closing this report because the bug has been fixed in the latest development version of Ubuntu.

This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure