Reviewed: https://review.openstack.org/246307
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=f3ad794bf75ac4b4251bcbbcbdb5ec7791fbea2e
Submitter: Jenkins
Branch: master
commit f3ad794bf75ac4b4251bcbbcbdb5ec7791fbea2e
Author: Claudiu Belu <cb...@cloudbasesolutions.com>
Date: Tue Oct 13 18:03:41 2015 +0300
Hyper-V: Fixes disk overhead claim issue
For each started VM, Hyper-V creates a VM memory file on the local
disk. The size of the file is the same as the size of the VM's
memory amount.
Implements the mentioned method in HyperVDriver.
Change-Id: Id40219dae96c0f7e60a86c0ed76fa08cea608aec
Closes-Bug: #1505681
** Changed in: nova
Status: In Progress => Fix Released
--
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):
Fix Released
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
