libvirt: Allow specification of default machine type
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-manuals |
Fix Released
|
High
|
Gauvain Pocentek |
Bug Description
https:/
commit 5b27fe7de22aef5
Author: Russell Bryant <email address hidden>
Date: Tue Jun 17 19:51:40 2014 +0000
libvirt: Allow specification of default machine type
The libvirt driver currently does not set the machine type for a KVM
guest by default. When not specified, libvirt will use the newest one
it knows about. Unfortunately, that can result in live migrations
failing if your environment is using different versions of the host OS
on compute nodes as the destination node may not be able to support the
machine type used when the VM was originally started.
A simple solution to this is to provide a new option which allows you
to specify the default machine type on a per compute node basis
(nova.conf option). By using this option, you can ensure that VMs are
started with a machine type that will allow it to be live migrated to
other nodes in the deployment.
This patch implements that solution by adding the hw_machine_type
option to the [libvirt] group of nova.conf.
DocImpact
Closes-bug: #1331170
Change-Id: I223c70c729315b
Changed in openstack-manuals: | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Gauvain Pocentek (gpocentek) |
tags: | added: config-reference |
Fix proposed to branch: master /review. openstack. org/115256
Review: https:/