On 10/10/2012 11:23 AM, Noam Slomianko wrote:
Regarding qemu-kvm memory allocation behaviour, this is the clearest
explanation I found:
Unless using explicit hugepages for the guest, KVM will
*not* initially allocate all RAM from the host OS. Each
page of RAM is only allocated when the guest
On 06/19/2012 08:12 PM, Saggi Mizrahi wrote:
- Original Message -
From: Deepak C Shetty deepa...@linux.vnet.ibm.com
To: Ryan Harper ry...@us.ibm.com
Cc: Saggi Mizrahi smizr...@redhat.com, Anthony Liguori aligu...@redhat.com,
VDSM Project Development
vdsm-devel@lists.fedorahosted.org
On 04/30/2012 07:30 PM, Itamar Heim wrote:
On 04/29/2012 04:19 PM, Dan Kenigsberg wrote:
On Sun, Apr 29, 2012 at 07:24:52AM -0400, Andrew Cathrow wrote:
- Original Message -
From: Dan Kenigsbergdan...@redhat.com
To: Gal Hammergham...@redhat.com
Cc: vdsm-devel@lists.fedorahosted.org
Hi,
I read the design here and I like to make sure that the future road map
will expand beyond the current scope.
The current design totally rely on libvirt and does not parse the
content of the PCI addressing. That's really really basic. The user
should be able to specify pci slot allocation
On 12/08/2011 12:33 PM, Ayal Baron wrote:
- Original Message -
On Tue, Dec 06, 2011 at 12:42:24PM +0200, Dor Laor wrote:
On 12/05/2011 03:55 PM, Adam Litke wrote:
On Sun, Dec 04, 2011 at 11:07:43PM +0200, Dor Laor wrote:
On 12/02/2011 04:15 PM, Adam Litke wrote:
On Fri, Dec 02
On 11/29/2011 06:29 PM, Adam Litke wrote:
After discussing MOM / VDSM integration at length, two different strategies
have
emerged. I will call them Plan A and Plan B:
Plan A: MOM integration at the OS/Packaging level
Plan B: MOM integration as a new VDSM thread
I think a form of plan B
