Ubuntu vmdk fails to boot with hardware virtualization version 11
Bug #1754030 reported by
John A Meinel
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
Triaged
|
Undecided
|
Unassigned |
Bug Description
We're running VMWare 6.0, but have always been launching instances in 5.5 compatibility mode (hardware version 10).
When we try Upgrading the Compatibility to 6.0 (version 11), the machines start failing to boot. This happened with both the Xenial image and the Artful image.
tags: | added: id-5ab130f3557aead7be00375f |
tags: | added: sts |
tags: | removed: sts |
To post a comment you must log in.
I tried going via the vsphere web UI (flash) and directly booting xenial- server- cloudimg- amd64-disk1. vmdk but its possible I had set up the configuration incorrectly. server- cloudimg- amd64.ova
I've since tried to just directly import the ova from the 'govc' commandline:
govc import.ova ./xenial-
One thing I noted was that if you "tar xf xenial- server- cloudimg- amd64.ova" you get xenial- 16.04-cloudimg. vmdk server- cloudimg- amd64-disk1. vmdk
... 284868608 ubuntu-
... 277238272 xenial-
Not only is it a very different filename, but its also a very different file size.
Note that the OVF that is embedded in the OVA is hard-coded to hardware version 10: stemType> vmx-10< /vssd:VirtualSy stemType>
<vssd:VirtualSy
When I first power on a newly imported OVA and watch the console, it tells me immediately:
no such device root
press any key to continue
Though eventually it moves forward on its own, without me interfering.
It does eventually boot to an "ubuntuguest login:" prompt.
Note that I don't currently know what/who to login as. (reading through the ovf file, seems to be setting a "Default User Password" to the empty string, but 'ubuntu' and 'ubuntuguest' don't seem to work.)
However, it does succeed in booting and getting to a login prompt.
If I then ask vsphere to upgrade the compatibility to ESXi 6.0 aka 11 (from 5.5 aka 10), then the boot process appears to stop at:
[ 6. ] usbhid: USB HID core driver
[ 26. ] random: nonblocking pool is initialized
however it does appear to hang in a similar way to the way that we were experiencing with Juju.