virsh is reporting ppc64le and not ppc64

Bug #1523674 reported by Mike Rushton on 2015-12-07
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mike Rushton
Mike Rushton
Mike Rushton

Bug Description

MAAS version 1.8.2+bzr4041-0ubuntu1~trusty1 from maas-maintainers stable PPA
IBM_PowerKVM release 3.1.0 gold build 41.0 (pkvm3_1_0)

Upon trying to enlist & commission a kvm VM on PowerKVM host, virsh is reporting ppc64le to MAAS as opposed to ppc64el.

This is tripping up probe-and-enlist-hardware:

leftyfb@lucuma[0]:~$ ssh root@
Last failed login: Mon Dec 7 20:00:08 EST 2015 from on ssh:notty
There were 4 failed login attempts since the last successful login.
Last login: Mon Dec 7 19:52:40 2015 from
[root@gulpin ~]# virsh dumpxml powerkvm
<domain type='kvm'>
  <memory unit='KiB'>2097152</memory>
  <currentMemory unit='KiB'>2097152</currentMemory>
  <vcpu placement='static'>4</vcpu>
    <type arch='ppc64le' machine='pseries-2.4'>hvm</type>
    <boot dev='hd'/>
  <clock offset='utc'/>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw'/>
      <source file='/var/lib/libvirt/images/powerkvm.img'/>
      <target dev='sda' bus='scsi'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    <controller type='usb' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    <controller type='pci' index='0' model='pci-root'/>
    <controller type='scsi' index='0'>
      <address type='spapr-vio' reg='0x2000'/>
    <interface type='bridge'>
      <mac address='52:54:00:61:0b:ac'/>
      <source bridge='bridge1'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    <serial type='pty'>
      <target port='0'/>
      <address type='spapr-vio' reg='0x30000000'/>
    <console type='pty'>
      <target type='serial' port='0'/>
      <address type='spapr-vio' reg='0x30000000'/>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>

Related branches

Mike Rushton (leftyfb) wrote :

The manual fix is to add the following line to /usr/lib/python2.7/dist-packages/provisioningserver/drivers/hardware/ under ARCH_FIX

'ppc64le': 'ppc64el',

Changed in maas:
milestone: none → next
status: New → In Progress
importance: Undecided → High
Changed in maas:
status: In Progress → Fix Committed
assignee: nobody → Mike Rushton (leftyfb)
Changed in maas:
milestone: next → none
status: Fix Committed → Fix Released
Jeff Lane (bladernr) wrote :

Mike, when you're testing 1.9, if you can verify that 1.9 resolves this issue, we can remove the blocker tag for this bug.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers