Re: [Xen-devel] memory hotplug for domUs

2017-02-03 Thread Juergen Gross
On 03/02/17 14:23, Ian Jackson wrote: > Juergen Gross writes ("Re: [Xen-devel] memory hotplug for domUs"): >> As user interface we are starting with "xl mem-set" which will use >> memory hotplug if necessary and supported by the guest (guest indicates >>

Re: [Xen-devel] memory hotplug for domUs

2017-02-03 Thread Ian Jackson
Juergen Gross writes ("Re: [Xen-devel] memory hotplug for domUs"): > As user interface we are starting with "xl mem-set" which will use > memory hotplug if necessary and supported by the guest (guest indicates > support via a Xenstore entry). A "force" param

Re: [Xen-devel] memory hotplug for domUs

2017-02-03 Thread Juergen Gross
On 03/02/17 13:19, Ian Jackson wrote: > Juergen Gross writes ("Re: [Xen-devel] memory hotplug for domUs"): >> While the syntax for "xl mem-add" (or however we would call it) could >> be rather clear and simple: >> >> xl mem-add [--host-node ] [--g

Re: [Xen-devel] memory hotplug for domUs

2017-02-03 Thread Ian Jackson
Juergen Gross writes ("Re: [Xen-devel] memory hotplug for domUs"): > While the syntax for "xl mem-add" (or however we would call it) could > be rather clear and simple: > > xl mem-add [--host-node ] [--guest-node ] > > I don't see how this would

Re: [Xen-devel] memory hotplug for domUs

2017-02-03 Thread Juergen Gross
On 25/01/17 14:02, Dario Faggioli wrote: > On Tue, 2017-01-24 at 16:03 -0700, Jim Fehlig wrote: >> On 01/20/2017 09:06 AM, Juergen Gross wrote: >>> On 20/01/17 16:54, Ian Jackson wrote: Juergen Gross writes ("memory hotplug for domUs"): > We first thought to enhance "xl mem-set", but after

Re: [Xen-devel] memory hotplug for domUs

2017-01-25 Thread Dario Faggioli
On Tue, 2017-01-24 at 16:03 -0700, Jim Fehlig wrote: > On 01/20/2017 09:06 AM, Juergen Gross wrote: > > On 20/01/17 16:54, Ian Jackson wrote: > > > Juergen Gross writes ("memory hotplug for domUs"): > > > > We first thought to enhance "xl mem-set", but after some more > > > > thinking > > > > about

Re: [Xen-devel] memory hotplug for domUs

2017-01-24 Thread Jim Fehlig
On 01/20/2017 09:06 AM, Juergen Gross wrote: On 20/01/17 16:54, Ian Jackson wrote: Juergen Gross writes ("memory hotplug for domUs"): We first thought to enhance "xl mem-set", but after some more thinking about it I'd rather add a new xl command, e.g. "mem-add" (we could later even add "mem-rem

Re: [Xen-devel] memory hotplug for domUs

2017-01-20 Thread Juergen Gross
On 20/01/17 17:37, Ian Jackson wrote: > Juergen Gross writes ("Re: memory hotplug for domUs"): >> On 20/01/17 16:54, Ian Jackson wrote: >>> Why ? Why would xl mem-set not automatically do the right thing ? >> >> How would you specify the numa node to add the memory to? > > You don't have to speci

Re: [Xen-devel] memory hotplug for domUs

2017-01-20 Thread Ian Jackson
Juergen Gross writes ("Re: memory hotplug for domUs"): > On 20/01/17 16:54, Ian Jackson wrote: > > Why ? Why would xl mem-set not automatically do the right thing ? > > How would you specify the numa node to add the memory to? You don't have to specify a numa node when you create a domain. Ian.

Re: [Xen-devel] memory hotplug for domUs

2017-01-20 Thread Juergen Gross
On 20/01/17 16:54, Ian Jackson wrote: > Juergen Gross writes ("memory hotplug for domUs"): >> We first thought to enhance "xl mem-set", but after some more thinking >> about it I'd rather add a new xl command, e.g. "mem-add" (we could later >> even add "mem-remove" to support memory unplug). > > W

Re: [Xen-devel] memory hotplug for domUs

2017-01-20 Thread Ian Jackson
Juergen Gross writes ("memory hotplug for domUs"): > We first thought to enhance "xl mem-set", but after some more thinking > about it I'd rather add a new xl command, e.g. "mem-add" (we could later > even add "mem-remove" to support memory unplug). Why ? Why would xl mem-set not automatically do

Re: [Xen-devel] memory hotplug for domUs

2017-01-20 Thread Boris Ostrovsky
On 01/20/2017 09:27 AM, Roger Pau Monné wrote: > On Fri, Jan 20, 2017 at 09:19:48AM -0500, Boris Ostrovsky wrote: For HVM/PVH guests however, ACPI Memory Hotplug. That way it will work for all operating systems, not just Linux. (Lets please not waste time building a somewhat-square

Re: [Xen-devel] memory hotplug for domUs

2017-01-20 Thread Juergen Gross
On 20/01/17 15:27, Roger Pau Monné wrote: > On Fri, Jan 20, 2017 at 09:19:48AM -0500, Boris Ostrovsky wrote: >> For HVM/PVH guests however, ACPI Memory Hotplug. That way it will work for all operating systems, not just Linux. (Lets please not waste time building a somewhat-square w

Re: [Xen-devel] memory hotplug for domUs

2017-01-20 Thread Roger Pau Monné
On Fri, Jan 20, 2017 at 09:19:48AM -0500, Boris Ostrovsky wrote: > > >> For HVM/PVH guests however, ACPI Memory Hotplug. That way it will work > >> for all operating systems, not just Linux. (Lets please not waste time > >> building a somewhat-square wheel which only fits on a Linux shaped axle

Re: [Xen-devel] memory hotplug for domUs

2017-01-20 Thread Boris Ostrovsky
>> For HVM/PVH guests however, ACPI Memory Hotplug. That way it will work >> for all operating systems, not just Linux. (Lets please not waste time >> building a somewhat-square wheel which only fits on a Linux shaped axle :) ) What about PVH dom0? I suspect we will have the same problem with A

Re: [Xen-devel] memory hotplug for domUs

2017-01-20 Thread Konrad Rzeszutek Wilk
On Fri, Jan 20, 2017 at 11:08:54AM +, Andrew Cooper wrote: > On 20/01/17 09:26, Juergen Gross wrote: Cc-ing Daniel as he wrote the Xen Balloon memory hotplug code. > > Recently Jim asked me why he can use "xl mem-max" to raise the allowed > > memory size of a domain in the hypervisor above th

Re: [Xen-devel] memory hotplug for domUs

2017-01-20 Thread Andrew Cooper
On 20/01/17 09:26, Juergen Gross wrote: > Recently Jim asked me why he can use "xl mem-max" to raise the allowed > memory size of a domain in the hypervisor above the configured maxmem > limit of the domain, but not use "xl mem-set" to balloon the domain up > to this value later. > > I thought libx

[Xen-devel] memory hotplug for domUs

2017-01-20 Thread Juergen Gross
Recently Jim asked me why he can use "xl mem-max" to raise the allowed memory size of a domain in the hypervisor above the configured maxmem limit of the domain, but not use "xl mem-set" to balloon the domain up to this value later. I thought libxl_domain_setmaxmem() being buggy as it doesn't modi