Am 8/9/19 um 12:47 PM schrieb Dominik Csapak:
> this fixes the display and selection problem with countries that
> have non-ascii symbols in them, like "Côte d'Ivoire"
>
> Signed-off-by: Dominik Csapak
> ---
> proxinstall | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/
Am 7/29/19 um 10:59 AM schrieb Aaron Lauterer:
> This adds a new config option called `spice_enhancements` and two
> settings for it:
>
> * videostreaming
> * foldersharing
>
> Signed-off-by: Aaron Lauterer
> ---
>
> Feedback is appreciated, especially regarding:
>
> * naming of the new config
Am 8/8/19 um 3:12 PM schrieb Fabian Grünbichler:
> Signed-off-by: Fabian Grünbichler
> ---
>
> Notes:
> possibly a fix for
> https://forum.proxmox.com/threads/mount-zfs-when-directory-not-empty.29657
>
> ...llel-mount-s-thread-dispatching-algo.patch | 244 ++
> debian/patch
We are currently looking at a re-do of CPU models and flags in general,
including adding support for custom CPU models [0]. Feature flags like
aes would be automatically supported by this (i.e. you could create a
custom model derived from kvm64 and add aes to it).
Then again, I'm not sure what
i just benchmarked a cached stat version vs. not cached
code is the following:
8<
use strict;
use warnings;
use utf8;
use Benchmark qw(cmpthese);
use PVE::Tools qw(run_command);
my $kvm_cache;
my $kvm_timestamp;
sub get_kvm_version {
my $kvm_user_version = 'unknown';
my $code
Hi,
is there anything missing before this and the corresponding pve-manager patch
can be reviewed?
Regards,
Peter
___
pve-devel mailing list
pve-devel@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Iterate all (online) nodes client-side and call vzdump with the correct
parameters (according to the job selected) for each one.
Then, show a progress bar in a non-closeable modal-dialog, to ensure the
user stays on the Backup page during the /vzdump API calls. Any errors
that occurred will be dis
Thanks again to Fabian and Dominik for reviewing the series.
v2 -> v3:
* Change UI mask to modal with progress bar
* Show error for offline nodes
v1 -> v2:
* Remove API path, call /vzdump on all nodes from client directly
* Remove check for Sys.Modify permission (only regular VZDump backup perms
Whitespace removal and consolidating VZDump's job id format into a
local variable.
Signed-off-by: Stefan Reiter
---
PVE/API2/Backup.pm| 25 +
www/manager6/dc/Backup.js | 10 +-
2 files changed, 14 insertions(+), 21 deletions(-)
diff --git a/PVE/API2/Backu
This was previously gated to CLI only, but it causes a vzdump job
started with the newly introduced "Run Now" button to fail if it
includes VMIDs on other nodes.
Signed-off-by: Stefan Reiter
---
PVE/API2/VZDump.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/PVE/API2/VZDum
Am 8/12/19 um 12:06 PM schrieb Dominik Csapak:
> On 8/12/19 11:43 AM, Thomas Lamprecht wrote:
>> Am 8/12/19 um 10:37 AM schrieb Dominik Csapak:
>>> we want to notify the api that there is a new qemu-binary, since
>>> the version will be cached in qemu-server and instead of
>>> checking the version
On 8/9/19 2:02 PM, Fabian Grünbichler wrote:
it might be worth it to attempt to convince upstream to ship the
"gluster" binary in its own package or move it to glusterfs-common
(since it seems to be a general management CLI akin to Ceph's 'ceph',
and not the actual server part).
On Fedora, fo
Am 8/7/19 um 1:57 PM schrieb Fabian Grünbichler:
> On May 25, 2019 5:09 pm, Thomas Lamprecht wrote:
>> Once, this was used when transferring the VM state finsihed on a
>> migration to another node to resume the VM there again, it was called
>> through SSH using the 'qm resume' command, which bases
On 8/12/19 11:43 AM, Thomas Lamprecht wrote:
Am 8/12/19 um 10:37 AM schrieb Dominik Csapak:
we want to notify the api that there is a new qemu-binary, since
the version will be cached in qemu-server and instead of
checking the version every time, just restart pveproxy/pvedaemon
whenever there is
Am 8/12/19 um 10:37 AM schrieb Dominik Csapak:
> we want to notify the api that there is a new qemu-binary, since
> the version will be cached in qemu-server and instead of
> checking the version every time, just restart pveproxy/pvedaemon
> whenever there is a qemu update
>
> this fixes a rare th
Am 8/1/19 um 1:01 PM schrieb Stefan Reiter:
> As explained in [0], we can add a hook script that will be called after
> update-initramfs did its job (and thus, a new initrd has been created).
>
> We can use this to automatically sync the ESPs using 'pve-efiboot-tool
> refresh', if update-initramfs
we want to notify the api that there is a new qemu-binary, since
the version will be cached in qemu-server and instead of
checking the version every time, just restart pveproxy/pvedaemon
whenever there is a qemu update
this fixes a rare theoretical issue when only updating qemu, that
the pvedaemon
17 matches
Mail list logo
