Setting nested virt breaks WS 2012 support
Bug #1698771 reported by
Lucian Petrut
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| compute-hyperv |
Fix Released
|
High
|
Unassigned | ||
Bug Description
We're always attempting to set the nested virtualization flag, be it enabled or not. The according os-win method will just raise a NotImplementedError on WS versions prior to 2016.
The result is that we can no longer spawn instances on previous Windows versions, such as 2012 R2.
| summary: |
- Setting nested virt breaks WS 2012 + Setting nested virt breaks WS 2012 support |
| Changed in compute-hyperv: | |
| importance: | Undecided → High |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to compute-hyperv (master) | #1 |
| Changed in compute-hyperv: | |
| status: | New → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 5d9b23af9ef083c
Author: Claudiu Belu <email address hidden>
Date: Mon Apr 10 11:50:27 2017 +0300
Fixes "always enable nested virt" issue
When creating an instance, the driver doesn't check if nested
virtualization is required. This fixes this issue.
Closes-Bug: #1698771
Change-Id: Ia30942dfcd0a4a