> Any reason to use 64k blocks and not something bigger? Backups should be
> sequential on all storage backends so something bigger shouldn't hurt.
Maybe you can raise that question on the qemu devel list?
___
pve-devel mailing list
pve-devel@pve.proxm
> Any reason to use 64k blocks and not something bigger?
Again, take a look at the qemu backup code. I guess it is
possible, but not trivial.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>>Ceph drops it's own readahead cache after the first 50MB to let the OS
>>do his own readahead which makes sense. But qemu itself does not have
it'>>s own readahead while doing backups.
Does is help (for backup) if you always force readahead with
rbd readahead disable after bytes=0
-
>>Any reason to use 64k blocks and not something bigger? Backups should be
>>sequential on all storage backends so something bigger shouldn't hurt.
Just found an old thread about this, when Dietmar has sent firsts backup
patches to qemu mailing
https://lists.nongnu.org/archive/html/qemu-devel/2
Hello Dietmar,
Am 16.02.2016 um 14:55 schrieb Stefan Priebe - Profihost AG:
Am 16.02.2016 um 12:58 schrieb Stefan Priebe - Profihost AG:
Am 16.02.2016 um 11:55 schrieb Dietmar Maurer:
Is it enough to just change these:
The whole backup algorithm is based on 64KB blocksize, so it
is not trivia
On Thu, 18 Feb 2016 17:56:00 +0100 (CET)
Dietmar Maurer wrote:
>
> What is wrong with our quota features?
>
> https://git.proxmox.com/?p=pve-container.git;a=commitdiff;h=50df544c7207da5de0251d61d633ed0147258031
>
> needs pve-container >= 1.0-43
>
Nothing. I was not aware of its existents - st
> On February 18, 2016 at 5:54 PM Michael Rasmussen wrote:
>
>
> On Thu, 18 Feb 2016 17:49:31 +0100 (CET)
> Dietmar Maurer wrote:
>
> >
> > What backport do you talk about? Current version is pve-kernel-3.10.0-16-pve
> > (3.10.0-43):
> >
> I was thinking of why make update to pve-kernel-3
ideas from this howto:
> https://www.howtoforge.com/tutorial/how-to-setup-virtual-containers-with-lxc-and-quota/
> be incorporated in Proxmox to support some kind of quota in LXC
> containers?
What is wrong with our quota features?
https://git.proxmox.com/?p=pve-container.git;a=commitdiff;h=50df
On Thu, 18 Feb 2016 17:49:31 +0100 (CET)
Dietmar Maurer wrote:
>
> What backport do you talk about? Current version is pve-kernel-3.10.0-16-pve
> (3.10.0-43):
>
I was thinking of why make update to pve-kernel-3.10.0-15-pve when the
current version is pve-kernel-3.10.0-16-pve?
--
Hilsen/Regar
> > What do you talk about exactly?
> >
> Did you see my last post?
yes
> pve-kernel-3.10.0-15-pve (3.10.0-41) <-- todays update
That update was Sun, 17 Jan (not today)
> pve-kernel-3.10.0-16-pve (3.10.0-42)
>
> pve-kernel-3.10.0-16-pve already contains the patch 3.10.0-41 so why backport
> f
Hi all,
Could the ideas from this howto:
https://www.howtoforge.com/tutorial/how-to-setup-virtual-containers-with-lxc-and-quota/
be incorporated in Proxmox to support some kind of quota in LXC
containers?
--
Hilsen/Regards
Michael Rasmussen
Get my public GnuPG keys:
michael rasmussen cc
http:
Signed-off-by: Dominik Csapak
---
www/manager/qemu/Clone.js | 1 +
www/manager/qemu/HDEdit.js | 3 ++-
www/manager/qemu/HDMove.js | 1 +
3 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/www/manager/qemu/Clone.js b/www/manager/qemu/Clone.js
index de0c95a..03322eb 100644
--- a/www/man
add htmlEnode as a renderer to fields which lets you
input arbitrary strings, to prevent html tags
Signed-off-by: Dominik Csapak
---
www/manager/dc/AuthView.js | 1 +
www/manager/dc/GroupView.js | 1 +
www/manager/dc/PoolView.js | 1 +
www/manager/dc/SecurityGroups.js
and the same for manager6
Signed-off-by: Dominik Csapak
---
www/manager6/dc/AuthView.js | 1 +
www/manager6/dc/GroupView.js | 1 +
www/manager6/dc/PoolView.js | 1 +
www/manager6/dc/SecurityGroups.js| 2 +-
www/manager6/dc/UserView.js | 1 +
www/manager6/gr
On Thu, 18 Feb 2016 13:39:15 +0100 (CET)
Dietmar Maurer wrote:
> > Why is pve-kernel-3.10.0-15-pve updated while pve-kernel-3.10.0-16-pve
> > is not?
>
> What do you talk about exactly?
>
Did you see my last post?
pve-kernel-3.10.0-15-pve (3.10.0-41) <-- todays update
pve-kernel-3.10.0-16-pve
> Why is pve-kernel-3.10.0-15-pve updated while pve-kernel-3.10.0-16-pve
> is not?
What do you talk about exactly?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
On Wed, Feb 17, 2016 at 03:59:33PM +0100, Timo Grodzinski wrote:
> Hi Wolfgang,
>
> Thanks for your annotations!
>
> Am 17.02.2016 um 15:01 schrieb Wolfgang Bumiller:
> > Please keep our coding style in mind.
> > There should be no spaces after opening and before closing parenthesis.
>
> Do you
Hi,
On Mon, Feb 15, 2016 at 02:25:04PM +0100, Timo Grodzinski wrote:
> Hi list,
>
> here is the patch for uploading and importing disk images to vms.
>
> - I have added an an 'Upload disk' button in the vm's hardware tab
> - It is also possible to upload gzipped image files, they will be extracted
On Thu, 18 Feb 2016 12:31:21 +0100
Michael Rasmussen wrote:
> Hi all,
>
> Why is pve-kernel-3.10.0-15-pve updated while pve-kernel-3.10.0-16-pve
> is not?
>
Looks very strange to me:
zcat /usr/share/doc/pve-kernel-3.10.0-15-pve/changelog.Debian.gz |head
pve-kernel-3.10.0 (3.10.0-41) unstable;
Hi all,
Why is pve-kernel-3.10.0-15-pve updated while pve-kernel-3.10.0-16-pve
is not?
--
Hilsen/Regards
Michael Rasmussen
Get my public GnuPG keys:
michael rasmussen cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir datanom net
http://pgp.mit.edu:11371/pks/lookup?op=get&s
applied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
applied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
applied both patches
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
And reuse it for ArchLinux.
---
src/PVE/LXC/Setup/ArchLinux.pm | 5 +++--
src/PVE/LXC/Setup/Base.pm | 9 +
src/PVE/LXC/Setup/SUSE.pm | 9 -
3 files changed, 12 insertions(+), 11 deletions(-)
diff --git a/src/PVE/LXC/Setup/ArchLinux.pm b/src/PVE/LXC/Setup/ArchLinux.pm
ind
---
To be consistent with the other distribution setups.
src/PVE/LXC/Setup/SUSE.pm | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/src/PVE/LXC/Setup/SUSE.pm b/src/PVE/LXC/Setup/SUSE.pm
index b7814fa..b1be09a 100644
--- a/src/PVE/LXC/Setup/SUSE.pm
+++ b/src/PVE/LXC/Setup/S
applied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
applied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
applied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
applied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
applied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
30 matches
Mail list logo
