lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAN8oO4A+_WyvtitEG75tQR3otfEq6zoou+Ve-OjkEg59agFYVg@mail.gmail.com>
Date:	Thu, 27 Nov 2014 17:39:59 +0530
From:	mad Engineer <themadengin33r@...il.com>
To:	Wanpeng Li <wanpeng.li@...ux.intel.com>
Cc:	kvm@...r.kernel.org, Paolo Bonzini <pbonzini@...hat.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Allocating dedicated RAM to host that guest can not use

never tried that.
can we do that transparently ie with out setting cgroups for each
virtul machines?.
A global group such that all combined virtual machines RAM utilization
to be with in a specific value ?

On Thu, Nov 27, 2014 at 4:59 PM, Wanpeng Li <wanpeng.li@...ux.intel.com> wrote:
> On Thu, Nov 27, 2014 at 05:12:52PM +0530, mad Engineer wrote:
>>Hi,
>>    Is there any way to set some RAM dedicated to host that guest can
>>not access?
>>Similar to setting RAM to Dom0 in Xen.
>>
>>I am over committing RAM for the instances but don't want host to swap.
>>
>>i understand that virtual machines are process,but can we achieve this
>
> How about limit the memory of which guest can access through memory cgroup?
>
> Regards,
> Wanpeng Li
>
>>
>>Thanks
>>--
>>To unsubscribe from this list: send the line "unsubscribe kvm" in
>>the body of a message to majordomo@...r.kernel.org
>>More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ