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: '{foo.bar}'
}
[...]
This mirrors the abillity of ExtJS's 'bind', which can do this also.
Simple
This is a WIP mock up of a possible cluster management component for
our WebUI. It's *not* final, and not intended for review - I mean if
you see something obvious wrong it won't hurt to tell.
I've plans to improve visuals still a bit, making a clear tab
separation between fully manual, and
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: '{foo.bar}'
}
[...]
This mirrors the ability of ExtJS's 'bind', which can do this also.
Simple
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
---
the only possible pitfall with this mode is that the
applied the other two of the series, but replaced this one with:
- description => "Whether the drive should be included when making
snapshots.",
+ description => "Controls qemu's snapshot mode feature."
+ . " If activated, changes made to the disk are temporary and will"
+
i forgot this fixes: #1662
On 02/08/2018 12:09 PM, Dominik Csapak wrote:
since qemu expects on|off (not 1|0),
we have to do it different
Signed-off-by: Dominik Csapak
---
PVE/QemuServer.pm | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git
since qemu expects on|off (not 1|0),
we have to do it different
Signed-off-by: Dominik Csapak
---
PVE/QemuServer.pm | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
index 4c04668..0011018 100644
---
if the value was '0', we did not append the option to the drive,
resulting in wrong command line if the qemu default of an option is not
'0'
Signed-off-by: Dominik Csapak
---
PVE/QemuServer.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
it has nothing to do with our snapshots, but with
the qemu snapshot mode of the disk (see the man page)
Signed-off-by: Dominik Csapak
---
PVE/QemuServer.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
index
Thanks Wolfgang !
>>I already rebased the patches but we didn't get around to doing much
>>testing yet. You can find the branches on my github if you want to get a
>>jump on it:
>>https://github.com/Blub/qemu pve-next (qemu-2.11 pve patch set on top)
>>https://github.com/Blub/qemu
I already rebased the patches but we didn't get around to doing much
testing yet. You can find the branches on my github if you want to get a
jump on it:
https://github.com/Blub/qemu pve-next (qemu-2.11 pve patch set on top)
https://github.com/Blub/qemu pve-next-patched (above with the extra/
applied, thanks
They could have cherry-picked the two function-rename & error handling
commits in between, then they wouldn't have had to resolve the conflicts
they had to resolve ;-) (wouldn't have saved them from auditing the
result though, so I guess it doesn't matter much, but for future
cherry pick from qemu-kvm-ev-2.9.0-16.el7_4.11.1
https://cbs.centos.org/koji/buildinfo?buildID=21003
Tue Jun 13 2017 Miroslav Rezanina - rhev-2.9.0-10.el7
- kvm-nbd-make-it-thread-safe-fix-qcow2-over-nbd.patch [bz#1454582]
Tue Aug 15 2017 Miroslav Rezanina
13 matches
Mail list logo