Re: [pve-devel] [PATCH v2] check_vmid_unused message change

applied, but simplified the code: my $vmtypestr = $d->{type} eq 'qemu' ? 'VM' : 'CT'; die "$vmtypestr $vmid already exists on node '$d->{node}'"; On 09/22/2015 04:21 PM, Alen Grizonic wrote: changed message if vmid used on a different cluster node --- data/PVE/Cluster.pm | 14 ++

[pve-devel] Fwd: [Qemu-devel] [ANNOUNCE] QEMU 2.4.0.1 CVE update released

Seem that qemu will release CVE fixed releases :) - Mail transféré - De: "mdroth" À: "qemu-devel" Cc: "qemu-stable" Envoyé: Mercredi 23 Septembre 2015 01:36:23 Objet: [Qemu-devel] [ANNOUNCE] QEMU 2.4.0.1 CVE update released Hi everyone, As part of recent planning around stable releas

[pve-devel] PVE 4 - No Display

Hi I am running PVE4 beta 2 in a HP Proliant and I cannot start the display... I get the error: "Guest has not initialized the display (yet)." Any help?? -- Gilberto Ferreira +55 (47) 9676-7530 Skype: gilberto.nunes36 ___ pve-devel mailing list pve-

[pve-devel] PVE 4: How can I remove/destroy entire Cluster??

Hi... If I am not wrong, in Pve 2/3 to remove the entire cluster, just need remove /var/lib/pve-cluster/* and /etc/cluster. However, I couldn't found /etc/cluster... Is there any other procure to follow? Thanks -- Gilberto Ferreira +55 (47) 9676-7530 Skype: gilberto.nunes36

[pve-devel] [PATCH v2] check_vmid_unused message change

changed message if vmid used on a different cluster node --- data/PVE/Cluster.pm | 14 +++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/data/PVE/Cluster.pm b/data/PVE/Cluster.pm index 63780ac..5860ed9 100644 --- a/data/PVE/Cluster.pm +++ b/data/PVE/Cluster.pm @@ -977,1

[pve-devel] [PATCH] check_vmid_unused message change

changed message if vmid used on a different cluster node --- data/PVE/Cluster.pm | 13 ++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/data/PVE/Cluster.pm b/data/PVE/Cluster.pm index 63780ac..880d91a 100644 --- a/data/PVE/Cluster.pm +++ b/data/PVE/Cluster.pm @@ -977,15

[pve-devel] [PATCH pve-container 1/2] Use format hashes in schemas

Use full schemas and generate_typetext for -net* and -mp* properties. --- src/PVE/LXC.pm | 143 - 1 file changed, 112 insertions(+), 31 deletions(-) diff --git a/src/PVE/LXC.pm b/src/PVE/LXC.pm index 3c77c5b..f5b3a5b 100644 --- a/src/PVE/LXC

[pve-devel] [PATCH pve-container 2/2] Replace parsing code for -net* and -mp*

Use the new JSONSchema provided parser which also verifies the parameters with their schemas. --- src/PVE/LXC.pm | 33 + 1 file changed, 9 insertions(+), 24 deletions(-) diff --git a/src/PVE/LXC.pm b/src/PVE/LXC.pm index f5b3a5b..7a6803e 100644 --- a/src/PVE/LXC.pm

[pve-devel] [PATCH pve-container 0/2] format-hash usage

These two patches add a format-schema for -rootfs, -mp* and -net* and replace the string parsing code with the new JSONSchema::parse_property_string. The typetext is now autogenerated and doesn't need to be included manually. The long descriptions aren't currently used but could be incorporated i

[pve-devel] [PATCH pve-common 2/6] generate_typetext: better handling of only-optional cases

--- src/PVE/JSONSchema.pm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/PVE/JSONSchema.pm b/src/PVE/JSONSchema.pm index f36ee42..45ce5ba 100644 --- a/src/PVE/JSONSchema.pm +++ b/src/PVE/JSONSchema.pm @@ -1317,11 +1317,11 @@ sub generate_typetext { &$add($key);

[pve-devel] [PATCH pve-common 0/6] typetext updates

First patch is a re-send - did I miss something or did you forget to apply it? This now adds a parse_property_string function which should be usable as a replacement for where we parse comma-separated lists of key-value pairs. That way we have one generic parser with schema based verification, by

[pve-devel] [PATCH pve-common 3/6] Added JSONSchema::parse_property_string

--- src/PVE/JSONSchema.pm | 50 ++ 1 file changed, 50 insertions(+) diff --git a/src/PVE/JSONSchema.pm b/src/PVE/JSONSchema.pm index 45ce5ba..d900a69 100644 --- a/src/PVE/JSONSchema.pm +++ b/src/PVE/JSONSchema.pm @@ -431,6 +431,51 @@ sub check_forma

[pve-devel] [PATCH pve-common 5/6] JSONSchema::generate_typetext: default_key support

--- src/PVE/JSONSchema.pm | 12 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/src/PVE/JSONSchema.pm b/src/PVE/JSONSchema.pm index 0d68608..3afc37a 100644 --- a/src/PVE/JSONSchema.pm +++ b/src/PVE/JSONSchema.pm @@ -1357,13 +1357,17 @@ sub generate_typetext { my ($p

[pve-devel] [PATCH pve-common 4/6] JSONSchema: verify comma-separated property strings

--- src/PVE/JSONSchema.pm | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/src/PVE/JSONSchema.pm b/src/PVE/JSONSchema.pm index d900a69..0d68608 100644 --- a/src/PVE/JSONSchema.pm +++ b/src/PVE/JSONSchema.pm @@ -396,8 +396,9 @@ PVE::JSONSchema::register_standard_option('

[pve-devel] [PATCH pve-common 1/6] JSONSchema::generate_typetext: raw typetext support

Instead of a format_description which ends up in the documentation as 'key=<$desc>', a typetext can now be used for an as-is string. (Eg. for when the key isn't required, like for volumes in mountpoints, typetext can be set to [volume=]volume) --- src/PVE/JSONSchema.pm | 19 ++- 1

[pve-devel] [PATCH pve-common 6/6] PodParser: use generate_typetext

--- src/PVE/PodParser.pm | 5 + 1 file changed, 5 insertions(+) diff --git a/src/PVE/PodParser.pm b/src/PVE/PodParser.pm index 7e31e19..3cb3c56 100644 --- a/src/PVE/PodParser.pm +++ b/src/PVE/PodParser.pm @@ -61,6 +61,11 @@ sub schema_get_type_text { } elsif (defined($phash->{maximum}

Re: [pve-devel] [PATCH v2] CT protection mode

applied, thanks! ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] [PATCH] extend functionality to (de)activate_volumes with snapshots

applied, but changed parameter ordering (use $cache as last parameter). ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] [PATCH pve-container] When destroying a container, remove bind mounts and block devices from the list of volumes to delete.

--- src/PVE/LXC.pm | 6 ++ 1 file changed, 6 insertions(+) diff --git a/src/PVE/LXC.pm b/src/PVE/LXC.pm index 3c77c5b..afff9fe 100644 --- a/src/PVE/LXC.pm +++ b/src/PVE/LXC.pm @@ -1294,6 +1294,12 @@ sub destroy_lxc_container { foreach_mountpoint($conf, sub { my ($ms, $mountpoin

[pve-devel] [PATCH v2] CT protection mode

[PATCH 2] changes: - added common check_protection subroutine - disk removal or update operation - restore over protected CT prevention - changed man page message --- src/PVE/API2/LXC.pm | 6 -- src/PVE/LXC.pm | 15 --- 2 files changed, 16 insertions(+), 5 deletions(-) dif

Re: [pve-devel] [RFC pve-common 0/4] Typetext generation

> I wonder though if it makes sense to then cache the parsed object somewhere > to avoid parsing the string twice? IMHO this makes code unnecessarily complex. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/li

[pve-devel] [PATCH] boot order permissions change

to change to boot order it is needed to assign a user the VM.Config.Disk privilege set with the add/modify/delete disk permissions -> now the patch allows the boot order to be (re)defined with the VM.Config.Options set - the modify any other VM configuration --- PVE/API2/Qemu.pm | 2 -- 1 file ch

Re: [pve-devel] [RFC pve-common 0/4] Typetext generation

> On September 22, 2015 at 8:03 AM Dietmar Maurer wrote: > > Should we maybe add general support for hash-refs as `format` for > > string types? > > Yes, I think that is a great idea. I wonder though if it makes sense to then cache the parsed object somewhere to avoid parsing the string twice? J

Re: [pve-devel] [PATCH pve-container] vzdump: tar: disable warnings about ignored files

applied On 09/22/2015 09:45 AM, Wolfgang Bumiller wrote: --- src/PVE/VZDump/LXC.pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/PVE/VZDump/LXC.pm b/src/PVE/VZDump/LXC.pm index 2d4b85a..858db8f 100644 --- a/src/PVE/VZDump/LXC.pm +++ b/src/PVE/VZDump/LXC.pm @@ -280,7

[pve-devel] [PATCH pve-container] vzdump: tar: disable warnings about ignored files

--- src/PVE/VZDump/LXC.pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/PVE/VZDump/LXC.pm b/src/PVE/VZDump/LXC.pm index 2d4b85a..858db8f 100644 --- a/src/PVE/VZDump/LXC.pm +++ b/src/PVE/VZDump/LXC.pm @@ -280,7 +280,7 @@ sub archive { my $tar = ['tar', 'cpf', '-',

[pve-devel] [PATCH pve-container] CT protection mode

changes: - added common check_protection subroutine - disk removal prevention - restore over protected CT prevention --- src/PVE/API2/LXC.pm| 6 -- src/PVE/API2/LXC/Config.pm | 4 src/PVE/LXC.pm | 8 3 files changed, 16 insertions(+), 2 deletions(-) diff --g