Hi, The node is supported:
# uname -m armv7l As you can see I've used this value to specify a specific architecture for my image. Libvirt is happy as well, as it supports the machine Nova is hardcoded to use: <machine maxCpus='4'>vexpress-a15</machine> -Harm Op 16-11-14 om 20:23 schreef Anne Gentle: > > > On Sun, Nov 16, 2014 at 1:00 PM, Harm Weites <[email protected] > <mailto:[email protected]>> wrote: > > Hi, > > My cloud recently got extended with some simple ARM hosts so now I'd > like Glance to offer ARM images next to x86_64. However, I'm unsure on > how to do just that. > > I've added Cirros 0.3.3 using the following glance commands: > > glance image-create --name='Cirros 0.3.3 ARM (kernel)' > --disk-format=aki --container-format=aki < cirros-0.3.3-arm-kernel > glance image-create --name='Cirros 0.3.3 ARM (ramdisk)' > --disk-format=ari --container-format=ari < cirros-0.3.3-arm-initramfs > glance image-create --name="Cirros 0.3.3 ARM" --disk-format=ami > --container-format=ami --property architecture=armv7l --property > kernel_id=\$KUUID --property ramdisk_id=\$RUUID < > cirros-0.3.3-arm-rootfs.img > > But this results in an unusable image, from which I can't create a new > volume to use for boot. The image is stuck in a queued-state: > > | ce98688b-35ab-4b0b-b8d0-1396631e82d9 | Cirros 0.3.0 > ARM | ami | ami | | > queued | > | 1c371d20-656d-42fb-9b2d-0ee129bedf91 | Cirros 0.3.0 ARM > kernel | aki | aki | 3741276 | > active | > | 2bf96321-7986-4b09-a9b5-2b8c47463b4a | Cirros 0.3.0 ARM > ramdisk | ari | ari | 2023036 | > active | > > Next I tried importing the ubuntu cloud image > (utopic-server-cloudimg-armhf-disk1) but booting a new instance from > that results in nothing - console.log stays empty so it presumably > fails. > > How should I add ARM images to Glance to make Nova happily boot > new ARM > instances? Are there any specifics I need to take into account in an > ARM-scenario? > > > Check > out > http://docs.openstack.org/cli-reference/content/chapter_cli-glance-property.html > > Can you find the architecture of the underlying node? > architecture: The CPU architecture that must be supported by the > hypervisor. Run *uname -m* to get the architecture of a machine. > > You may also need to find the Libvirt machine type. Valid types can be > viewed by using the virsh capabilities command (machine types are > displayed in the machine tag). > > Please log a doc bug if you see anything outdated on that page. > Thanks, > Anne > > > > Regards, > Harm > > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : [email protected] > <mailto:[email protected]> > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > >
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
