CloudInit no bootable device Proxmox 6.1-3

fenpaws

New Member
Feb 18, 2020
7
1
1
23
Deutschland
fenpa.ws
This is an english version of an existing german topic, you can find it here.

So here is my problem, I have a fresh Proxmox 6.1-3 VE Server and I wanted to make a template with Cloud-Init.
I followed the instructions 1:1 provided by the Wiki and created my first template.

Here is what i did:
I downloaded the bionic-server-cloudimg-amd64.img and imported it to my local-vm. That worked out without a problem, but I noticed that the name of the drive was a bit different from what I expected.

The Wiki entry told me to import vm-9000-disk-1, but the import created vm-9000-disk-0. So I adapted it to vm-9000-disk-0 and ran the command.

Everything else worked out fine.
Well, besides the creation of a clone. That is where I'm stuck now.

I created two kinds of clones, a Linked one, and a Full Clone. I started both and got the same result for both Clones.
no bootable device found

I'm new to Proxmox and KVM/QEMU in general, so please excuse my lack of knowledge.
 
Last edited:

dcsapak

Proxmox Staff Member
Staff member
Feb 1, 2016
5,045
507
133
32
Vienna
can you post the vm config ? (qm config ID)
 

fenpaws

New Member
Feb 18, 2020
7
1
1
23
Deutschland
fenpa.ws
Here you go, I dint know which one you want so I copied the config for all. Template, Linked and Full

Template:

Code:
boot: d
ide2: local-lvm:vm-9000-cloudinit,media=cdrom
memory: 2048
net0: virtio=BE:CF:A3:22:68:DA,bridge=vmbr0
scsi0: local-lvm:base-9000-disk-0,size=2252M
scsihw: virtio-scsi-pci
serial0: socket
smbios1: uuid=cbf91d3d-1cf0-4ebc-a37d-d4dc1e79f16f
template: 1
vga: serial0
vmgenid: 72c8f58a-5bb2-4151-bf4b-3fba76fc4a95

Linked Clone:
Code:
boot: d
ide2: local-lvm:vm-101-cloudinit,media=cdrom,size=4M
memory: 2048
name: Docker01
net0: virtio=02:1E:9B:43:D9:41,bridge=vmbr0
scsi0: local-lvm:vm-101-disk-0,size=2252M
scsihw: virtio-scsi-pci
serial0: socket
smbios1: uuid=a61ea138-7358-4cc6-86fb-756d80161d86
vga: serial0
vmgenid: 0cfc3019-8bc5-401d-ad3b-ce187d585337

Full Clone
Code:
boot: d
ide2: local-lvm:vm-102-cloudinit,media=cdrom,size=4M
memory: 2048
name: Docker02
net0: virtio=AE:16:B0:CD:E2:D8,bridge=vmbr0
scsi0: local-lvm:vm-102-disk-0,size=2252M
scsihw: virtio-scsi-pci
serial0: socket
smbios1: uuid=0ca6443a-ffd9-4c67-ad6b-9f66ab527d57
vga: serial0
vmgenid: c5722d02-5f80-4785-855f-931a83ca8645
 

dcsapak

Proxmox Staff Member
Staff member
Feb 1, 2016
5,045
507
133
32
Vienna
you did not set the 'bootdisk' parameter

eg.
Code:
qm set 9000 -bootdisk scsi0

edit:
also you only boot from the cd image, not from the harddisk:

Code:
qm set 9000 -boot c
 

fenpaws

New Member
Feb 18, 2020
7
1
1
23
Deutschland
fenpa.ws
Hm, the only entry I could find in the wiki about the bootdisk is qm set 9000 --boot c --bootdisk scsi0. But I tried your addition and this is the config now. (I do these command for all VMs and the Template.)
Still nothing.
Code:
boot: c
bootdisk: scsi0
ide2: local-lvm:vm-101-cloudinit,media=cdrom,size=4M
memory: 2048
name: Docker
net0: virtio=0A:02:44:02:82:D1,bridge=vmbr0
scsi0: local-lvm:vm-101-disk-0,size=2252M
scsihw: virtio-scsi-pci
serial0: socket
smbios1: uuid=6e211ce9-b420-434e-93da-6883a1fc8f01
vga: serial0
vmgenid: c731350a-9f1a-4b18-b668-94641bb57d37

but it still wont boot. Same error message.
 
Last edited:

dcsapak

Proxmox Staff Member
Staff member
Feb 1, 2016
5,045
507
133
32
Vienna
just tested here, works without problems:

Code:
wget bionic-.....
qm create 20000
qm importdisk 20000 bionic-..... local
qm set 20000 -bootdisk scsi0 -boot c -scsi0 local:20000/vm-20000-disk-0.raw
qm start
 

fenpaws

New Member
Feb 18, 2020
7
1
1
23
Deutschland
fenpa.ws
I tried this again, this time without converting it to a Template. Still, nothing.
This is the config for the VM
Code:
boot: c
bootdisk: scsi0
memory: 2048
net0: virtio=36:A8:5B:9F:E5:77,bridge=vmbr0
scsi0: local-lvm:vm-9000-disk-0,size=2252M
scsihw: virtio-scsi-pci
smbios1: uuid=75ec2510-a1f3-42fc-b19b-ebe607cf289e
vmgenid: cffcf5bc-fa37-4c46-975c-e83f01b669a4
 
Last edited:

fenpaws

New Member
Feb 18, 2020
7
1
1
23
Deutschland
fenpa.ws
Okay, so I did a bit of testing, after a few days of frustration and I found a solution.

It seems like something goes wrong when I try to use .img images. So I tried something else, I looked if there were any other disk files I could use and found .vmdk files. I tried it out and it worked without any problems.

Now I still don't know what the issue really is, but for now i go with that solution.
 
Last edited:

HeikoBe

New Member
Apr 8, 2020
1
0
1
50
I had a similar issue while trying to import old versions of qcow2 (0.1.0) Images, which where named xxx.img.
As long as I tried to import them the way the were, I ended up with the message: not a bootable device.

After reading your post I simply renamed the images giving them the ending .qcow2 and guess what, it works.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!