#16671 closed defect (fixed)
Ubuntu 16.04 Cloud Image (OVF) not working
| Reported by: | Seafire | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.1.18 |
| Keywords: | ubuntu, cloud, | Cc: | |
| Guest type: | Linux | Host type: | Windows |
Description
The standard OVA provided by the Official Ubuntu Cloud image repository (https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64.ova) doesn't fully boot after being imported into the latest VirtualBox version (5.1.18). I'm preeseding the user-data to cloud-init via a cdrom (iso) but the VM still doesn't show any login prompt. The same image boots successfully on VMWare and KVM.
To reproduce the problem simply download and import the image.
Attachments (2)
Change History (6)
by , 8 years ago
| Attachment: | ubuntuCloudImage_vboxlog.txt added |
|---|
comment:1 by , 8 years ago
It helps to enable the first serial port, set it to COM1 and use a file as output. Looks like the guest is trying to connect to 169.254.169.254 which isn't reachable for some reason.
follow-up: 4 comment:2 by , 8 years ago
Ah, thank you for your answer. Yes that's normal behavior, the OS is trying to reach the metadata server since this is a Cloud image. To avoid that one can provide a pre-seeded ISO which contains the required metadata.
So, with the serial port enabled I could finally debug the problem. The image now boots successfully so I guess you can close the ticket.
comment:4 by , 7 years ago
Replying to Seafire:
So, with the serial port enabled I could finally debug the problem. The image now boots successfully so I guess you can close the ticket.
How did you debug and finally solve the problem? I enabled COM1 and have it write to a file. I see the requests to 169.254.169.254 in the log looking like:
[ 35.101118] cloud-init[944]: 2017-12-30 22:13:42,144 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [1/120s]: request error [HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded with url: /2009-04-04/meta-data/instance-id (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x7f9329465fd0>: Failed to establish a new connection: [Errno 113] No route to host',))]
The console however reads something like: blk_update_request: I/O error, dev fd0, sector 0
The very first screen in the console reads: error: no such device: root.
Log of the VM