Hi guys
Any change to migrate from LXC to LXD??
It's seem to me that LXD is more advance than LXC! What do you, guys, thing
about it???
Thanks a lot!
Cheers
---
Gilberto Nunes Ferreira
(47) 3025-5907
(47) 99676-7530 - Whatsapp / Telegram
Skype: gilberto.nunes36
___
qemu 2.11 need a power of 2 cache size.
"
Parameter 'xbzrle_cache_size' expects is invalid,
it should be bigger than target page size and a power of two
"
Divide the memory size by 8 instead 10
Alexandre Derumier (1):
migrate cache-size : power of 2
PVE/QemuMigrate.pm | 4 ++--
1 file change
qemu 2.11 need a power of 2 cache size.
"
Parameter 'xbzrle_cache_size' expects is invalid,
it should be bigger than target page size and a power of two
"
Divide the memory size by 8 instead 10
---
PVE/QemuMigrate.pm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/PVE/Qem
On 02/09/2018 03:23 PM, Dietmar Maurer wrote:
with my patch as it is, only root can change the option
afaics there is no option to set the target file (at least not on the
commandline) only 'TMPDIR' via an environment variable (but i guess this
is not what we want since it changes the location o
> with my patch as it is, only root can change the option
>
> afaics there is no option to set the target file (at least not on the
> commandline) only 'TMPDIR' via an environment variable (but i guess this
> is not what we want since it changes the location of all tmpfiles of qemu)
I always re
applied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
applied all 3 patches
___
pve-devel mailing list
pve-devel@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
DisplayEdit did not get a cleanup during our ExtJS 4 to ExtJS 6
cleanup, in fact it was really touched in the last 5 years.
So refactor it to a declarative syntax, at least almost, we keep the
me.load in initComponent, just to much hassle to adress this for now.
Also purge DisplaySelector. It was
DisplayEdit did not get a cleanup during our ExtJS 4 to ExtJS 6
cleanup, in fact it was really touched in the last 5 years.
So refactor it to a declarative syntax, at least almost, we keep the
me.load in initComponent, just to much hassle to adress this for now.
Also purge DisplaySelector. It was
applied
On Fri, Feb 09, 2018 at 08:28:34AM +0100, Thomas Lamprecht wrote:
> allow to access sub elements of configuration items for binding.
>
> E.g., if the following configuration is present:
>
> foo: {
> bar: true
> }
>
> one could do:
>
> xtype: 'displayfield',
> cbind {
> value: '
On 02/09/2018 09:57 AM, Fabian Grünbichler wrote:
On Thu, Feb 08, 2018 at 03:39:36PM +0100, Dominik Csapak wrote:
this adds a 'kiosk' option, which enables qemus snapshot
mode, which redirects all writes to a temporary file, so
that if you stop the qemu process, the disks are in their original s
On Thu, Feb 08, 2018 at 03:39:36PM +0100, Dominik Csapak wrote:
> this adds a 'kiosk' option, which enables qemus snapshot
> mode, which redirects all writes to a temporary file, so
> that if you stop the qemu process, the disks are in their original state
>
> Signed-off-by: Dominik Csapak
> ---
small nit(s) inside
On Tue, Feb 06, 2018 at 02:00:46PM +0100, Wolfgang Bumiller wrote:
> Signed-off-by: Wolfgang Bumiller
> ---
> src/PVE/API2/LXC.pm | 16 +++-
> src/PVE/LXC/Create.pm | 12 +++-
> 2 files changed, 26 insertions(+), 2 deletions(-)
>
> diff --git a/src/PVE/
Before, 'undef' was equivalent to unlimited, but '0' is the
"explicitly unlimited" value, so if the user doesn't request
an override, apply limits as if the user was unprivileged
(otherwise there's no way for privileged users to explicitly
ask to not override the configured limits).
Signed-off-by:
14 matches
Mail list logo
