Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CPU model and live migration problem #1688

Closed
feldsam opened this issue Jan 27, 2018 · 2 comments

Comments

@feldsam
Copy link
Contributor

commented Jan 27, 2018

Bug Report

Version of OpenNebula

  • 5.4.6
  • Development build

Component

  • Authorization (LDAP, x509 certs...)
  • Command Line Interface (CLI)
  • Contextualization
  • Documentation
  • Federation and HA
  • Host, Clusters and Monitorization
  • KVM
  • Networking
  • Orchestration (OpenNebula Flow)
  • Packages
  • Scheduler
  • Storage & Images
  • Sunstone
  • Upgrades
  • User, Groups, VDCs and ACL
  • vCenter

Description

Hello, I updated to 5.4.6 right now and tested new cpu model selection. I have one server with Ivy-Bridge, second with Westmere.

So I selected Westmere, start VM on Ivy-Bridge server and try live migration.

Command "virsh --connect qemu+tcp://localhost/system migrate --live --compressed one-13595 
qemu+tcp://node2.feldhost.cz/system" failed: error: operation failed: guest CPU doesn't match
specification: missing features: xsave,avx,f16c,rdrand,fsgsbase,smep,erms,xsaveopt

Problem is, that exposed CPU to guest is Ivy-Bridge and not Westmere.

Working setting is

<cpu match='exact'> <model fallback='allow'>Westmere</model> </cpu>
@feldsam

This comment has been minimized.

Copy link
Contributor Author

commented Apr 1, 2018

Hello, I tested it today again, but it still doesn't work. We have to use <cpu match='exact'> instead of <cpu mode='host-model'>.

When I run VM on newer cpu model, it can not be live migrated to older one.

@vholer

This comment has been minimized.

Copy link
Member

commented May 3, 2018

Current State

For the particular CPU model, we have:

<cpu mode='host-model'>
    <model fallback='allow'>core2duo</model>
</cpu>

Proposed change

It's enough to only update the mode to custom (and also better set a fallback mode to forbid):

<cpu mode='custom'>
    <model fallback='forbid'>core2duo</model>
</cpu>

@vholer vholer closed this May 3, 2018

@vholer vholer reopened this May 3, 2018

juanmont pushed a commit to juanmont/one that referenced this issue May 3, 2018

rsmontero added a commit that referenced this issue May 10, 2018

@rsmontero rsmontero closed this May 10, 2018

rsmontero added a commit that referenced this issue Oct 2, 2018

F #1688: Fix bug with custom cpu mode
(cherry picked from commit b226b829a87828d6eba93eced5a9455305995352)

rsmontero added a commit that referenced this issue Oct 2, 2018

F #1688: Fix bug with custom cpu mode
(cherry picked from commit b226b829a87828d6eba93eced5a9455305995352)

rsmontero added a commit that referenced this issue Oct 5, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.