I tried cloud-init with ubuntu-18.04-minimal-cloudimg-amd64.img from official link, ubuntu-18.04-server-cloudimg-amd64.img from this link and bionic-server-cloudimg-amd64.img from this link. They were all failed to boot with "No bootable disk" messages alike. I had followed Cloud-Init_Support section of proxmox wiki and reviewed Cloud-Init_FAQ also. My proxmox VE version is 6.0-15. What can I do to find the key to solve this situation?
Proxmox VE 6 does not boot ubuntu cloud images with cloud-init for VM.
- Thread starter kakao73
- Start date
@Pravednik I've used latest qemu-server: 6.1-1. It does not solve the problem. Anyway, as a workaround I've used an old created ubuntu cloud image based template with cloud-init. It has no problems until now. I want to switch old images with new latest one safely. Is there a way to investigate this situation? Any logs related?
Same issue here.
I am using the instructions from here: https://pve.proxmox.com/wiki/Cloud-Init_Support
I am using proxmox 6.1-3
When it boots, it says "No bootable device"
My exact commands are as follows:
All of those commands complete successfully.
Then, I click Start on the GUI and open the Console, and it loops over and over with no bootable disk.
I am using the instructions from here: https://pve.proxmox.com/wiki/Cloud-Init_Support
I am using proxmox 6.1-3
When it boots, it says "No bootable device"
My exact commands are as follows:
Code:
wget https://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-amd64.img
qm create 9000 --memory 2048 --net0 virtio,bridge=vmbr0
qm importdisk 9000 bionic-server-cloudimg-amd64.img vmstorage
qm set 9000 --scsihw virtio-scsi-pci --scsi0 vmstorage:vm-9000-disk-0
qm set 9000 --ide2 vmstorage:cloudinit
qm set 9000 --boot c --bootdisk scsi0
qm set 9000 --serial0 socket --vga serial0All of those commands complete successfully.
Then, I click Start on the GUI and open the Console, and it loops over and over with no bootable disk.
That fixed it!!! Renaming .img to .qcow2 and it works fine now. Thanks!
I have the same issue: seabios repots:
boot failed: not a bootable disk
bionic-server-cloudimg-amd64.img is not a qcow2 image, converting it manually `convert -f qcow2 -O raw bionic-server-cloudimg-amd64.img bionic-server-cloudimg-amd64.raw` also does not work
I tried downloading .vmdk image - and it worked!
boot failed: not a bootable disk
Unfortunately it didn't work for me, adding disk via command line gives error:
Code:
copy failed: command '/usr/bin/qemu-img convert -p -n -f qcow2 -O raw bionic-server-cloudimg-amd64.qcow2 'zeroinit:rbd:ceph1/vm-185-disk-0:conf=/etc/pve/ceph.conf'' failed: exit code 1bionic-server-cloudimg-amd64.img is not a qcow2 image, converting it manually `convert -f qcow2 -O raw bionic-server-cloudimg-amd64.img bionic-server-cloudimg-amd64.raw` also does not work
I tried downloading .vmdk image - and it worked!
Last edited:
Hi, @saalih416, I actually did it wrong, I used .img from .tar.gz file. Names and sizes was the same, as I can remember, I thought that it was the same image. README in currently available .tar.gz archives points out that the image in archive is a raw ext4 partition. Probably I missed README before, but current .img files (not archived) are imported well, even without renaming to qcow2.
So I think the problem is solved.
So I think the problem is solved.
Last edited:
I'm the OP. It turns out that the tip linked and confirmed by @ujiam, @stfl is right to me. In my case, I confirmed ubuntu minimal cloud image .img file is a qcow2 image. Just rename its file extension:
And use that .qcow2 without additional converting operations.
Code:
mv <ubuntu-minimal-cloud-image>.img <ubuntu-minimal-cloud-image>.qcow2I can cofirm this has worked for me too (on proxmox 7.1-7) - the exact same problem with Ubuntu focal downloaded today (https://cloud-images.ubuntu.com/focal/current/)