> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmo/how-to/how-to-resize-instance-on-same-host.md).

# How To Resize Instance on Same host?

## Problem

VM migrates to another host during VM resize even though `allow_resize_to_same_host=true` is set in the nova configuration file.

## Environment

* Platform9 Managed OpenStack - v4.0 and Higher
* Nova

## Cause

The config parameter `allow_resize_to_same_host=true` set in */etc/nova/nova.conf* on the Management Plane does not guarantee that the VM will be resized on the same host. If the scheduler selects a different host as a destination based on the calculation of the load then the instance will be moved out to a different host at the time of resizing.

## Resolution

The workaround is to create a host aggregate containing only the source hypervisor host to resize the instance. Detailed steps are available in the article [Resize Instance to the Same Host.](https://docs.platform9.com/openstack/virtual-machines/resize-vm/)

## Additional Information

You can refer to the article [Resize and cold migrate](https://docs.openstack.org/nova/latest/contributor/resize-and-cold-migrate.html) for more details.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://platform9.com/kb/pmo/how-to/how-to-resize-instance-on-same-host.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.