Comment 1 for bug 1449084

hi Dane
I tested and reproduce your problem, but I this is an issue.

when build an instance with an volume , nova will fetch the volume meat from that volume.
if you create an volume from an base image. all meta will be saved in the volume in cinder.
nova will get them and set them as

| volume_image_metadata | {u'kernel_id': u'712e417f-16ec-42fb-b2cb-ef8c316d9903', u'container_format': u'ami', u'min_ram': u'0', u'ramdisk_id': u'd73b7b35-b89b-4e92-98fc-dc5a7929f214', u'disk_format': u'ami', u'image_name': u'cirros-0.3.2-x86_64-uec', u'image_id': u'93169d18-1bb2-45f7-861c-6735ef687db9', u'checksum': u'4eada48c2843d2a262c814ddc92ecf2c', u'min_disk': u'0', u'size': u'25165824'} |

and libvirt found kernel_id and ramdisk_id from glance, it can boot up without issue.

I suggest that you try using another image as base to create a boot volume, then dd it.
the result is nova can boot it up , but after you try to logging it from vnc, failed due to this is not an bootable disk.