[arm64] bad cpu-cores detection

[Junien F]

Hi,

I just created a 4-vcpu arm64 instance on OpenStack, and added it to a juju environment. On this instance, I get :
$ cat /proc/cpuinfo
Processor : AArch64 Processor rev 1 (aarch64)
processor : 0
BogoMIPS : 100.00
processor : 1
BogoMIPS : 100.00
processor : 2
BogoMIPS : 100.00
processor : 3
BogoMIPS : 100.00
Features : fp asimd evtstrm
CPU implementer : 0x50
CPU architecture: AArch64
CPU variant : 0x0
CPU part : 0x000
CPU revision : 1

Hardware : linux,dummy-virt

However, juju reports only one core :

8 started 1.25.6 XX.YY.ZZ.TT manual:XX.YY.ZZ.TT trusty arch=arm64 cpu-cores=1 mem=3958M

I know 1.25.x only accepts critical bugs, and this probably isn't a critical bug, that's fine. However, juju 2.0 may be impacted as well, but I can't easily create an arm64 environment with juju 2.0. Could you verify this ?

Thanks

[Curtis Hovey (sinzui)]

Could the openstack be in need of a patch?

<sfeole>
sinzui: mmmmm that's rather old, any may not be a problem anymore
sinzui: do you have access to an arm64 host?
sinzui: many path improvements were passed into nova re: arm64

[Junien F (axino)]

Versions :

$ dpkg -l|egrep 'nova|libvirt|qemu'
ii ipxe-qemu 1.0.0+git-20131111.c3d1e78-2ubuntu1.1 all PXE boot firmware - ROM images for qemu
hi libvirt-bin 1.2.12-0ubuntu14.4+ppa1 arm64 programs for the libvirt library
hi libvirt0 1.2.12-0ubuntu14.4+ppa1 arm64 library for interfacing with different virtualization systems
hi nova-common 1:2015.1.1-0ubuntu2+ppa1 all OpenStack Compute - common files
hi nova-compute 1:2015.1.1-0ubuntu2+ppa1 all OpenStack Compute - compute node base
hi nova-compute-kvm 1:2015.1.1-0ubuntu2+ppa1 all OpenStack Compute - compute node (KVM)
hi nova-compute-libvirt 1:2015.1.1-0ubuntu2+ppa1 all OpenStack Compute - compute node libvirt support
ii python-libvirt 1.2.12-0ubuntu1~cloud0 arm64 libvirt Python bindings
hi python-nova 1:2015.1.1-0ubuntu2+ppa1 all OpenStack Compute Python libraries
ii python-novaclient 1:2.22.0-0ubuntu2~cloud0 all client library for OpenStack Compute API
ii qemu-block-extra:arm64 1:2.3+dfsg-5ubuntu9~ubuntu14.04.1 arm64 extra block backend modules for qemu-system and qemu-utils
ii qemu-efi 0~20150106.5c2d456b-2~14.04~ppa1 all UEFI firmware for virtual machines
ii qemu-kvm 1:2.3+dfsg-5ubuntu9~ubuntu14.04.1 arm64 QEMU Full virtualization
ii qemu-slof 20140630+dfsg-1ubuntu1~14.04 all Slimline Open Firmware -- QEMU PowerPC version
ii qemu-system 1:2.3+dfsg-5ubuntu9~ubuntu14.04.1 arm64 QEMU full system emulation binaries
ii qemu-system-arm 1:2.3+dfsg-5ubuntu9~ubuntu14.04.1 arm64 QEMU full system emulation binaries (arm)
ii qemu-system-common 1:2.3+dfsg-5ubuntu9~ubuntu14.04.1 arm64 QEMU full system emulation binaries (common files)
ii qemu-system-mips 1:2.3+dfsg-5ubuntu9~ubuntu14.04.1 arm64 QEMU full system emulation binaries (mips)
ii qemu-system-misc 1:2.3+dfsg-5ubuntu9~ubuntu14.04.1 arm64 QEMU full system emulation binaries (miscelaneous)
ii qemu-system-ppc 1:2.3+dfsg-5ubuntu9~ubuntu14.04.1 arm64 QEMU full system emulation binaries (ppc)
ii qemu-system-sparc 1:2.3+dfsg-5ubuntu9~ubuntu14.04.1 arm64 QEMU full system emulation binaries (sparc)
ii qemu-system-x86 1:2.3+dfsg-5ubuntu9~ubuntu14.04.1 arm64 QEMU full system emulation binaries (x86)
ii qemu-utils 1:2.3+dfsg-5ubuntu9~ubuntu14.04.1 arm64 QEMU utilities

[Anastasia (anastasia-macmood)]

@Curtis, @Aaron

Have we seen this in CI against Juju 2?

[Sean Feole (sfeole)]

In Bug# https://bugs.launchpad.net/juju/+bug/1592613

I posed data to show that cpu core detection is working properly in JuJu 2.0

I don't know the specifics of how the original description data was collected. On What Host? Was it a VM? etc...

Do you want me to verify this against and arm64 vm generated via NOVA? last I checked Nova was properly building VM's with the correct cpu information with the Latest Openstack,( Mitaka)

Patches were recently applied to provied UEFI support as well.

[Anastasia (anastasia-macmood)]

@Sean
I think it's a duplicate of the bug you've pointed at. Marking it as such.

[Junien F (axino)]

For the record, this was a nova VM, created manually (nova boot ...) and then added to the juju environment with juju add-machine.