On 08/03/2015 04:22 PM, Dietmar Maurer wrote:
the data property is not available via me.data, but via me.config.data.
So we need to handle this in the parent class.
So why do we need both cases?
+ data : me.data || me.config.data
Isn't it enough to do:
+ data :
So I tried to enhance this patch based on the mailing list suggestions.
It might be a small thing, but if 1 user asks publicly for the signification
of this field, probably there are 10 others behind who don't dare to ask ...
___
pve-devel mailing
Do not hardcode the name of the admin user, instead move it to a stub
function
which we can enhance when our templates provide the necessary meta
information.
I don't think this patch does improve something.
___
pve-devel mailing list
Do not hardcode the name of the admin user, instead move it to a stub function
which we can enhance when our templates provide the necessary meta information.
---
www/manager/lxc/CreateWizard.js | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git
Please see attached a patch to implement resize for the DRBD backend.
I hope it matches all your coding style guidelines;
feedback is welcome, of course.
Regards,
Phil
From 4ceb4d737d4c604dcf99bbd46d60d731626e9781 Mon Sep 17 00:00:00 2001
From: root r...@proxmox4b2.at.linbit
Date: Mon, 3 Aug
Anyways, I tested the patch, and volume_resize() now returns without errors.
The problem is that it does not resize the underlying LVM volume.
Do I need to install any drbdmanage updates/patches to make that work?
I just scanned the drbdmanage sources, and the corresponding implementation
is
On Mon, Aug 03, 2015 at 12:02:10PM +0200, Alexandre DERUMIER wrote:
But you also now only add tap devices to vmbrX instead of vmbrXvY,
which is wrong, the vmbrXvY bridges are now virtually unused.
Yes, this is expected.
we don't need vmbrXvY anymore, because we tag vlan on vmbrX ports
works fine here on opteron 61XX and opteron 63XX.
This is on baremetal, I can't test in nested vitualization.
- Mail original -
De: datanom.net m...@datanom.net
À: pve-devel pve-devel@pve.proxmox.com
Envoyé: Lundi 3 Août 2015 11:28:19
Objet: Re: [pve-devel] updated PVE 4.0 packages on
On Mon, 3 Aug 2015 11:08:59 +0200
Michael Rasmussen m...@datanom.net wrote:
I have just noticed that pve-qemu-kvm_2.4-1_amd64.deb also brings qemu
2.4 which theoretically also could be the problem, but I still believe
it is a issue with seabios since the way it stops working has been seen
Ok, I'll try qemu 2.4 on opteron today (on baremetal, not nested).
- Mail original -
De: datanom.net m...@datanom.net
À: aderumier aderum...@odiso.com, pve-devel pve-devel@pve.proxmox.com
Envoyé: Dimanche 2 Août 2015 15:53:56
Objet: Re: [pve-devel] updated PVE 4.0 packages on pvetest
Hi
On 07/30/2015 09:03 AM, Alexandre DERUMIER wrote:
This is fixed in qemu 2.4rc3
I confirm can our pve-qemu-kvm package in version 2.4-1 has this fixed.
Thanks for the update !
Emmanuel
___
pve-devel mailing list
pve-devel@pve.proxmox.com
On Mon, 3 Aug 2015 08:12:27 +0200 (CEST)
Alexandre DERUMIER aderum...@odiso.com wrote:
Ok, I'll try qemu 2.4 on opteron today (on baremetal, not nested).
I have just noticed that pve-qemu-kvm_2.4-1_amd64.deb also brings qemu
2.4 which theoretically also could be the problem, but I still
Hi,
Please change the red text into: successfully
Aug 03 09:25:52 starting migration of VM 158 to node 'prox05' (10.160.5.15)
Aug 03 09:25:52 copying disk images
Aug 03 09:25:52 migration finished successfuly (duration 00:00:00)
TASK O
Immo
___
---
src/PVE/AbstractMigrate.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/PVE/AbstractMigrate.pm b/src/PVE/AbstractMigrate.pm
index 01d0a50..caa6573 100644
--- a/src/PVE/AbstractMigrate.pm
+++ b/src/PVE/AbstractMigrate.pm
@@ -218,7 +218,7 @@ sub migrate {
die
Signed-off-by: Alexandre Derumier aderum...@odiso.com
---
src/PVE/Network.pm | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/PVE/Network.pm b/src/PVE/Network.pm
index 9c05e78..dd34198 100644
--- a/src/PVE/Network.pm
+++ b/src/PVE/Network.pm
@@ -312,6 +312,7 @@ sub tap_plug {
if
In ExtJS5 when we use the following call (taken from OptionView.js)
Ext.applyIf(me, {
items: {
xtype: 'pveKVComboBox',
data: data,
}
});
the data property is not available via me.data, but via me.config.data.
So we need to
Seems to work :-)
On Mon, Aug 03, 2015 at 03:07:37PM +0200, Alexandre Derumier wrote:
Signed-off-by: Alexandre Derumier aderum...@odiso.com
---
src/PVE/Network.pm | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/PVE/Network.pm b/src/PVE/Network.pm
index 9c05e78..dd34198 100644
---
17 matches
Mail list logo
