vGPU instance is not reattached to guest on resume
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Gustavo Santos |
Bug Description
Description
===========
When suspending a guest with a vGPU instance attached to it, Nova asks libvirt to detach that device, since the guest can't be suspended otherwise. When resuming that guest, however, it comes back without the vGPU instance previously attached to it.
This happens because, at the time the feature was developed, libvirt did not support hot unplugging mediated devices [1]. That limitation has been lifted since then, and the resume operation needs to be modified in order to reattach the mediated device (vGPU instance) that was detached on suspend.
[1] https:/
Steps to reproduce
==================
1 - Set up the environment in order to provide vGPU capabilities to Nova;
2 - Spawn an instance using a flavor that asks for a vGPU;
3 - Suspend the instance;
4 - Resume the instance;
Expected result
===============
After resuming the instance, it should still have a vGPU instance attached.
Actual result
=============
The instance comes back without a vGPU attached.
Environment
===========
- Tested on StarlingX OpenStack - Ussuri; master code still does not provide a fix.
- Libvirt v4.7.0 + KVM.
Changed in nova: | |
assignee: | nobody → Gustavo Santos (gooshtavow) |
status: | New → In Progress |
tags: | added: vgpu |
Changed in nova: | |
importance: | Undecided → Low |
Fix proposed to branch: master /review. opendev. org/c/openstack /nova/+ /815373
Review: https:/