Public bug reported:
For each started VM, Hyper-V creates on the local disk a memory file for
each VM. The memory file has the same size as the assigned VM memory.
For example, if an instance with 4 GB ram starts, a 4 GB file is
created.
This can cause scheduling issues, especially on hosts which have large
quantities of memory, but not a very large local disk, resulting in
instances failing to spawn due to "insufficient local disk".
** Affects: nova
Importance: Undecided
Assignee: Claudiu Belu (cbelu)
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1505681
Title:
Hyper-V creates VM memory file on the local disk for each VM
Status in OpenStack Compute (nova):
New
Bug description:
For each started VM, Hyper-V creates on the local disk a memory file
for each VM. The memory file has the same size as the assigned VM
memory. For example, if an instance with 4 GB ram starts, a 4 GB file
is created.
This can cause scheduling issues, especially on hosts which have large
quantities of memory, but not a very large local disk, resulting in
instances failing to spawn due to "insufficient local disk".
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1505681/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
