Signed-off-by: Dominik Csapak
---
www/manager6/window/LoginWindow.js | 1 -
1 file changed, 1 deletion(-)
diff --git a/www/manager6/window/LoginWindow.js
b/www/manager6/window/LoginWindow.js
index 521f2db..ac354a7 100644
--- a/www/manager6/window/LoginWindow.js
+++ b/www/manager6/window/LoginWi
This add a default filter which is executed on store initial load,
so we display only the backups matching our ID.
---
www/manager6/grid/BackupView.js | 23 ---
1 file changed, 16 insertions(+), 7 deletions(-)
diff --git a/www/manager6/grid/BackupView.js b/www/manager6/grid/Ba
since we have now two filters defined it makes sense to use
a separate name here
---
www/manager6/grid/BackupView.js | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/www/manager6/grid/BackupView.js b/www/manager6/grid/BackupView.js
index 1de5323..a924c0a 100644
---
For detecting a CT templates architecture we used the `file -b -L`
output from the PVE host side.
If the container has a link:
/bin/sh -> /bin/bash
(Alpine Linux does that) the '-L' flag from file resolves the
$rootfs/bin/sh to /bin/bash and thus checks the architecture of
bash on the PVE system, w
RFC because IMHO this behaviour is not optimal (for both containers and
VMs). If a VMUser has more than one VM but no VM.Config.Options
permission, they can effectively copy the configuration of one guest
system (e.g. the one with the most powerful HW) to the other ones with
Backup & Restore. I
this makes the behaviour similar to VM restore operations
Signed-off-by: Fabian Grünbichler
---
src/PVE/API2/LXC.pm | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/PVE/API2/LXC.pm b/src/PVE/API2/LXC.pm
index 423c90e..cb8df4a 100644
--- a/src/PVE/API2/LXC.pm
+++ b/sr
On Thu, Dec 15, 2016 at 04:10:55PM +0100, Fabian Grünbichler wrote:
> this makes the behaviour similar to VM restore operations
>
> Signed-off-by: Fabian Grünbichler
> ---
> src/PVE/API2/LXC.pm | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/src/PVE/API2/LXC.pm b/
First a general remark about dying in forks:
Since it is a fork it will use the same path out as the parent process
would, doing the same kind of exception handling etc. This means it'll
end up doing the same cleanup. Eg. when creating a container fails to
use this function, the child process alrea
we moved the lxc cgroup settings in a sub namespace, but did not use the
total_cache value for subtracting so we showed a wrong used amount
Signed-off-by: Dominik Csapak
---
src/PVE/LXC.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/PVE/LXC.pm b/src/PVE/LXC.pm
index 8
For detecting a CT templates architecture we used the `file -b -L`
output from the PVE host side.
If the container has a link:
/bin/sh -> /bin/bash
(Alpine Linux does that) the '-L' flag from file resolves the
$rootfs/bin/sh to /bin/bash and thus checks the architecture of
bash on the PVE system, w
> a lot of people asking about arbitrary crashes of the kernel in the
> forums and maybe there should be something "out-of-the-box" for that.
> Integrating crashdump into Debian is very easy and should be - at
> least - discussed in detail. I normally active crashdump on all my
> servers (not only
> When you add a HardDisk to a not running VM, it gets simply written to the
> *.conf file. But when you EDIT a HardDisk, someone executes the storage plugin
> function "activate_volume", even if the VM is deactivated.
> Is this a bug or a feature?
> At least the state of the volume is different af
On Wed, Dec 14, 2016 at 04:44:03PM +0100, Jasmin J. wrote:
> > No, you need to set that yourself if you want to test that.
> If there is no command to force it, is there an action to trigger it somehow?
> If not, why does it exist?
looks like dead code, unless I missed something:
- only called wit
13 matches
Mail list logo
