** Changed in: nova (Ubuntu)
Status: New => Invalid
** Changed in: libvirt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564831
Title:
s390x: error bo
This bug was fixed in the package lxcfs - 2.0.0-0ubuntu2
---
lxcfs (2.0.0-0ubuntu2) xenial; urgency=medium
* Cherrypick upstream patches to fix cpuinfo on s390x. (LP: #1564831)
-- Serge Hallyn Mon, 04 Apr 2016 11:11:27
-0500
** Changed in: lxcfs (Ubuntu)
Status: New => F
** Package changed: lxd (Ubuntu) => lxcfs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564831
Title:
s390x: error booting instance
To manage notifications about this bug go to:
https://b
FWIW, Devstack sets "cpu_mode = 'none'" in its default setup [1] of the
libvirt driver.
References:
[1]
https://github.com/openstack-dev/devstack/blob/096106184988f76bd091b131341379757e068bcd/lib/nova_plugins/hypervisor-libvirt#L42
--
You received this bug notification because you are a member
Regarding issue 2), this is most probably due to the cpu mode setting:
The nova.conf needs the setting "cpu_mode = none" in order to not have it set
to 'host-model'.
This setting has not been working on s390x - this is a statement as of Mitaka
and libvirt 1.2.21 at least
--
You
Also tried with the nova-compute node running directly on Ubuntu on an
LPAR but still see the same problem..
I think there are two distinct bugs here
1) lxcfs support for S390x looks a little incomplete
2) nova can't boot KVM instances with mitaka + libvirt 1.3.1
--
You received this bug notif
Mapped /proc/cpuinfo into the container from the host, but still seeing
the same issue...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564831
Title:
s390x: error booting instance
To manage notifi
Should have also mentioned that this is running in a LXD container;
/proc/cpuinfo is empty for some reason which I think is the root cause
of this problem.
** Also affects: lxd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564831
Title:
s390x: error booting instance
To manage notifications abou
Some pertinent logs from libvirt as well:
Apr 01 10:07:33 juju-e58e3f3f-abe1-4393-8212-5c6936c4d369-machine-11
libvirtd[21610]: End of file while reading data: Input/output error
Apr 01 10:07:35 juju-e58e3f3f-abe1-4393-8212-5c6936c4d369-machine-11
libvirtd[21610]: this function is not supported
10 matches
Mail list logo
