[Yahoo-eng-team] [Bug 1673467] Re: [ocata] unsupported configuration: CPU mode 'host-model' for aarch64 kvm domain on aarch64 host is not supported by hypervisor

2017-09-12 Thread James Page
** Changed in: charm-nova-compute Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1673467 Title: [ocata] unsupported

[Yahoo-eng-team] [Bug 1673467] Re: [ocata] unsupported configuration: CPU mode 'host-model' for aarch64 kvm domain on aarch64 host is not supported by hypervisor

2017-07-26 Thread James Page
OK - some updates I've tested with 2.5.0 and 3.5.0 of libvirt using OpenStack Ocata. 2.5.0 libvirt/qemu does not support host-model - only host-passthrough so I agree that we should just being doing the right thing either in the charm (as we've done for other non-x86 arch) or the nova codebase -

[Yahoo-eng-team] [Bug 1673467] Re: [ocata] unsupported configuration: CPU mode 'host-model' for aarch64 kvm domain on aarch64 host is not supported by hypervisor

2017-07-14 Thread Launchpad Bug Tracker
This bug was fixed in the package libvirt - 3.5.0-1ubuntu1 --- libvirt (3.5.0-1ubuntu1) artful; urgency=medium * Merged with Debian unstable (3.5) This closes several bugs: - improved handling of host-model since libvirt 3.2 (LP: #1673467) - Adding POWER9 cpu model to

[Yahoo-eng-team] [Bug 1673467] Re: [ocata] unsupported configuration: CPU mode 'host-model' for aarch64 kvm domain on aarch64 host is not supported by hypervisor

2017-07-05 Thread ChristianEhrhardt
Hi trying to get the status right here. AFAIK these things are changed in libvirt 3.2 to be good - at least for x86, not sure if/how arm followed but since there were major changes we should consider it fixed and re-analyze from there for the development release. So the coming merge of a newer

[Yahoo-eng-team] [Bug 1673467] Re: [ocata] unsupported configuration: CPU mode 'host-model' for aarch64 kvm domain on aarch64 host is not supported by hypervisor

2017-04-03 Thread Ryan Beisner
** Also affects: charm-nova-compute Importance: Undecided Status: New ** Changed in: charm-nova-compute Status: New => Confirmed ** Changed in: charm-nova-compute Importance: Undecided => High ** Changed in: charm-nova-compute Assignee: (unassigned) => Ryan Beisner

[Yahoo-eng-team] [Bug 1673467] Re: [ocata] unsupported configuration: CPU mode 'host-model' for aarch64 kvm domain on aarch64 host is not supported by hypervisor

2017-03-23 Thread Corey Bryant
Switching the status back to New for upstream nova since there may be a need to switch from host-model to host-passthrough in nova. ** Changed in: nova Status: Opinion => New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to

[Yahoo-eng-team] [Bug 1673467] Re: [ocata] unsupported configuration: CPU mode 'host-model' for aarch64 kvm domain on aarch64 host is not supported by hypervisor

2017-03-17 Thread Sean Dague
This looks like an upstream libvirt/qemu issue that got exposed with the version bump in Ubuntu. Closing the upstream Nova side. ** Changed in: nova Status: New => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to