On Fri, 19 Aug 2016 08:02:26 +0200 (CEST)
Alexandre DERUMIER wrote:
>
> I don't think it's the same problem.
>
The error message I am getting here is exactly the same as I get for
backups.
--
Hilsen/Regards
Michael Rasmussen
Get my public GnuPG keys:
michael rasmussen cc
http://pgp.mit.ed
>>The move disk operation is hitting the same problem as backup with
>>dataplane.
I don't think it's the same problem.
drive-mirror itself it's working, it's the block-job-complete which is failing.
(can't rettache the new block device to iothread).
This is fixed in qemu 2.7 (which should be rel
On Fri, 19 Aug 2016 07:53:27 +0200
Michael Rasmussen wrote:
> I see a usecase for high iops requirement and especially when storage
> is ceph but for enterprise and/or HA usage in generel it is a disaster
> waiting to happen if moving a disk between storage pools is not
> supported and taking bac
On Fri, 19 Aug 2016 05:43:52 +0200 (CEST)
Alexandre DERUMIER wrote:
> just tested from ceph to ceph, with iothread enabled, indeed it's hanging the
> qemu process when doing the switch to new disk.
> data copy itself seem to works.
> I think this is a qemu bug, it should work.
>
The move disk o
>>I have just discovered that when iothread is enabled on a disk this
>>disk cannot be moved online using move disk.
>>>just tested from ceph to ceph, with iothread enabled, indeed it's hanging
>>>the qemu process when doing the switch to new disk.
>>>data copy itself seem to works.
>>>I thin
>>I have just discovered that when iothread is enabled on a disk this
>>disk cannot be moved online using move disk.
just tested from ceph to ceph, with iothread enabled, indeed it's hanging the
qemu process when doing the switch to new disk.
data copy itself seem to works.
I think this is a qem
Hi all,
I have just discovered that when iothread is enabled on a disk this
disk cannot be moved online using move disk. Also as discovered
previously you cannot make a backup of such disk either. The iothread
current implementation in Proxmox in my opinion is totally useless!
--
Hilsen/Regards
Reviewed-by: Dominik Csapak
On 08/18/2016 02:33 PM, Emmanuel Kasper wrote:
The current position inside the Workspace is saved via the StateProvider
separately thus this clearing operation do not lose the previous selection.
As a side effect by calling setContent(null) on logout we also fix the
The current position inside the Workspace is saved via the StateProvider
separately thus this clearing operation do not lose the previous selection.
As a side effect by calling setContent(null) on logout we also fix the
following bug:
when logging out while the Syslog tab of the Node panel was di
---
Note: already applied
DAB.pm | 22 ++
1 file changed, 14 insertions(+), 8 deletions(-)
diff --git a/DAB.pm b/DAB.pm
index 0f6b993..8991084 100644
--- a/DAB.pm
+++ b/DAB.pm
@@ -548,6 +548,7 @@ sub finalize {
my $instpkgs = $self->read_installed ();
my $pkginfo =
The current position inside the Workspace is saved via the StateProvider
separately thus this clearing operation do not lose the previous selection.
As a side effect by calling setContent(null) on logout we also fix the
following bug:
when logging out while the Syslog tab of the Node panel was di
On 07/11/2016 03:46 PM, Dominik Csapak wrote:
> this implements the new StatusView class for
> guests and templates
>
> using the new pveStatusView, we do not split the status
> panels per lxc/qemu, but for Template/Guest
>
> this makes more sense, since the information which lxc
> and qemu gue
On 07/11/2016 03:46 PM, Dominik Csapak wrote:
> this patch series changes the StatusView Panel
>
> this version has multiple advantages:
>
> uses space more efficiently
> (two columns on node statusview)
> makes information more readable
> (grouping, spacing, progressbar with colors)
> displays m
when a vzdump script is set and the backup fails early (eg.
when exceeding the number of backups) run_hook_script()
showed an uninitialized value error trying to use
$task->{mode} which is set only after prepare() was called.
This sets $task->{mode} early, still updated later to $stop
if !$running
Comment inline
On 08/17/2016 02:49 PM, Emmanuel Kasper wrote:
The current position inside the Workspace is saved via the StateProvider
separately thus this clearing operation do not lose the previous selection.
This patch also fixes another bug:
when logging out while the Syslog tab of the Nod
15 matches
Mail list logo
