VM resize does not use the max_virt_slot from the existing VM
Bug #1691762 reported by
Manas Mandlekar
This bug report is a duplicate of:
Bug #1722923: max virtio slots value for instances aren't maintained on resize.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| nova-powervm |
Confirmed
|
High
|
Matt Rabe | ||
Bug Description
If a VM is having a custom slot higher than 64 then the resize operation (e.g. a change in change CPU configuration) fails. It looks like the resize flow is attempting to set the max_virtual_slots to something smaller (64) than the currently in-use virtual device slot numbers and it fails at hypervisor layer.
| Changed in nova-powervm: | |
| assignee: | nobody → Matt Rabe (mdrabe) |
| importance: | Undecided → High |
| status: | New → Confirmed |
To post a comment you must log in.
