You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Launchpad user Scott Moser(smoser) wrote on 2017-05-25T14:26:04.759266+00:00
On i386 and amd64, openstack puts 'OpenStack Nova', into the dmi platform
information. OpenStack using kvm on s390, does not identify itself to the guest in any way.
The result is that cloud-init cannot identify it is running on openstack.
We need two things
a.) change openstack to provide that information through libvirt on s390
in some way.
b.) possibly changes in qemu to pass information through that the guest
can see. Some options here might include putting information in
the device tree or possibly on the attached disk (model of the disk could be 'OpenStack disk XXXX').
This bug was originally filed in Launchpad as LP: #1693524
Launchpad details
Launchpad user Scott Moser(smoser) wrote on 2017-05-25T14:26:04.759266+00:00
On i386 and amd64, openstack puts 'OpenStack Nova', into the dmi platform
information. OpenStack using kvm on s390, does not identify itself to the guest in any way.
The result is that cloud-init cannot identify it is running on openstack.
We need two things
a.) change openstack to provide that information through libvirt on s390
in some way.
b.) possibly changes in qemu to pass information through that the guest
can see. Some options here might include putting information in
the device tree or possibly on the attached disk (model of the disk could be 'OpenStack disk XXXX').
Related bugs:
https://bugs.launchpad.net/cloud-init/+bugs?field.tag=dsid-nova
The text was updated successfully, but these errors were encountered: