Re: [pve-devel] use our own format for LXC containers

In future, we can now also add additional mount entries like: rootfs: local:101/subvol-101-disk-1.raw,size=4 mount0: faststore:101/subvol-101-disk-1.raw,size=1,mp=/mnt/faststore mount1: slowbigstore:101/subvol-101-disk-1.raw,size=1024,mp=/mnt/slowbigstore I wonder if we could use something

Re: [pve-devel] coreboot support

1) Does the new fix something currently broken? 2) Does the new provide something useful to us which is currently not available? I the coreboot case the answers to the above to questions is: 1) No 2) No OK ;-) Thanks for testing! ___ pve-devel

[pve-devel] [RFC PATCH pve-container] don't set proxy_arp and forwarding on lxc veths

Setting these doesn't make much sense as the interfaces are attached to bridges (this is old cruft from VZ venet). (Hotplugging already leaves them be at their default.) --- src/lxcnetaddbr | 2 -- 1 file changed, 2 deletions(-) diff --git a/src/lxcnetaddbr b/src/lxcnetaddbr index

[pve-devel] [PATCH pve-access-control] fix access of possibly undefined variable

--- PVE/AccessControl.pm | 1 + 1 file changed, 1 insertion(+) diff --git a/PVE/AccessControl.pm b/PVE/AccessControl.pm index 955e143..bfee816 100644 --- a/PVE/AccessControl.pm +++ b/PVE/AccessControl.pm @@ -708,6 +708,7 @@ sub parse_user_config { userconfig_force_defaults($cfg); +

[pve-devel] [PATCH 1/2] fix LXC backup after changing lxc to pct conf

--- src/PVE/API2/LXC.pm | 2 +- src/PVE/LXCCreate.pm | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/PVE/API2/LXC.pm b/src/PVE/API2/LXC.pm index 17cb0a6..93ab537 100644 --- a/src/PVE/API2/LXC.pm +++ b/src/PVE/API2/LXC.pm @@ -309,7 +309,7 @@

[pve-devel] [PATCH 2/2] Fix in PVE::LXC parse_ct_mountpoint

there was the allocation missed --- src/PVE/LXC.pm | 1 + 1 file changed, 1 insertion(+) diff --git a/src/PVE/LXC.pm b/src/PVE/LXC.pm index 21f03a4..bf084ba 100644 --- a/src/PVE/LXC.pm +++ b/src/PVE/LXC.pm @@ -643,6 +643,7 @@ sub parse_ct_mountpoint { if ($p =~

Re: [pve-devel] coreboot support

On Fri, 7 Aug 2015 07:23:53 +0200 (CEST) Dietmar Maurer diet...@proxmox.com wrote: I have successfully make a boot rom with coreboot using seabios as payload;-) So what is the advantage if that still uses seabios? I have asked myself the same question;-) The other possible payloads, as

Re: [pve-devel] use our own format for LXC containers

I wonder if we could use something generic like hdd0: local:101/subvol-101-disk-1.raw,size=4,mp=/ I prefer 'rootfs' instead, because 'rootfs' has fixed mp '/', and is a required option. hdd1: faststore:101/subvol-101-disk-1.raw,size=1,mp=/mnt/faststore hdd2:

Re: [pve-devel] coreboot support

I have successfully make a boot rom with coreboot using seabios as payload;-) So what is the advantage if that still uses seabios? I have asked myself the same question;-) The other possible payloads, as I see it, will not be sufficient for proxmox since they all miss iscsi and

Re: [pve-devel] use our own format for LXC containers

Ok. I'll try to work on mountpoints next week. - Mail original - De: dietmar diet...@proxmox.com À: aderumier aderum...@odiso.com Cc: pve-devel pve-devel@pve.proxmox.com Envoyé: Vendredi 7 Août 2015 10:40:22 Objet: Re: [pve-devel] use our own format for LXC containers I wonder if we

[pve-devel] [PATCH] Add extra optional list to pveversion

if the packet on the opt list is not installed, it will not shown. --- PVE/API2/APT.pm | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/PVE/API2/APT.pm b/PVE/API2/APT.pm index 2eac330..b665a5b 100644 --- a/PVE/API2/APT.pm +++ b/PVE/API2/APT.pm @@ -536,9 +536,12 @@

[pve-devel] [PATCH] Fix mem ans swap size when converted from OpenVz.

--- src/PVE/VZDump/ConvertOVZ.pm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/PVE/VZDump/ConvertOVZ.pm b/src/PVE/VZDump/ConvertOVZ.pm index 72f1c0d..dedd640 100644 --- a/src/PVE/VZDump/ConvertOVZ.pm +++ b/src/PVE/VZDump/ConvertOVZ.pm @@ -304,9 +304,9 @@ sub

Re: [pve-devel] [PATCH] activate|deactivates volumes on ct start/stop.

I applied a slightly modified patch: https://git.proxmox.com/?p=pve-container.git;a=commitdiff;h=ef241384c684dcb1bbd0f537ab1c58e676ddf530 Does that work for you? ___ pve-devel mailing list pve-devel@pve.proxmox.com

[pve-devel] [PATCH] extend ZFSPoolPlugin::zfs_get_zvol_size with quota

This is necessary if we use Container because they use subvol. subvol has no size but a quota. if return is 0 there is no quota set. --- PVE/Storage/ZFSPoolPlugin.pm | 16 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/PVE/Storage/ZFSPoolPlugin.pm

[pve-devel] [PATCH] Fix: If a Ct are created and a pool are given add the Ct to pool.

--- src/PVE/API2/LXC.pm | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/PVE/API2/LXC.pm b/src/PVE/API2/LXC.pm index 93ab537..8823ae4 100644 --- a/src/PVE/API2/LXC.pm +++ b/src/PVE/API2/LXC.pm @@ -301,7 +301,7 @@ __PACKAGE__-register_method({ my $code = sub {

Re: [pve-devel] [PATCH] activate|deactivates volumes on ct start/stop.

I think it should work. I'll have more time for testing next week, I was very busy this week. - Mail original - De: dietmar diet...@proxmox.com À: aderumier aderum...@odiso.com, pve-devel pve-devel@pve.proxmox.com Envoyé: Vendredi 7 Août 2015 11:47:55 Objet: Re: [pve-devel] [PATCH]