Release the agent lock when we shutdown the LRM and stopped all
services.
Signed-off-by: Thomas Lamprecht
---
src/PVE/HA/Env.pm | 9 +
src/PVE/HA/Env/PVE2.pm | 11 +++
src/PVE/HA/LRM.pm | 3 +++
src/PVE/HA/Sim/Env.pm |
rootfs need no mp because it is always /
---
src/PVE/API2/LXC.pm | 10 +-
src/PVE/CLI/pct.pm| 9 -
src/PVE/LXC.pm| 25 ++---
src/PVE/LXC/Create.pm | 2 +-
4 files changed, 36 insertions(+), 10 deletions(-)
diff --git a/src/PVE/API2/LXC.pm b/src/
---
src/PVE/LXC.pm | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/PVE/LXC.pm b/src/PVE/LXC.pm
index 33fca55..364c761 100644
--- a/src/PVE/LXC.pm
+++ b/src/PVE/LXC.pm
@@ -2363,6 +2363,8 @@ sub create_disks {
$conf->{$ms} = print_ct_mountpoint($mountpoint, $ms eq
'rootfs'
If map is not set you get a warning of an empty variable without real
information.
And when you try to start the container, it will not start without an
explication.
---
src/PVE/LXC.pm | 1 -
1 file changed, 1 deletion(-)
diff --git a/src/PVE/LXC.pm b/src/PVE/LXC.pm
index 860901f..af3b9b7 10064
This add support vlan trunks for qemu net interfaces.
based on theses patches:
http://pve.proxmox.com/pipermail/pve-devel/2014-September/012730.html
This works with OVS and linux vlan-aware bridge.
details are in commits
Regards,
Alexandre
___
pve-d
Signed-off-by: Alexandre Derumier
---
src/PVE/Network.pm | 36
1 file changed, 24 insertions(+), 12 deletions(-)
diff --git a/src/PVE/Network.pm b/src/PVE/Network.pm
index 8cd7698..293ebfa 100644
--- a/src/PVE/Network.pm
+++ b/src/PVE/Network.pm
@@ -161,7 +16
This add support for net trunks vlan filtering
for ovs and linux vlan-aware bridge
Can be mixed with current "tag" option
examples:
--
allow only 802.1Q packets with vlanid 2,3,4 :
netx: .,trunks=2,3,4
allow only 802.1Q packets with vlanid 2,3,4 and tag non-802.1Q packets to
vlani
>>- directly pipe to qemu-img so no need to aquire temp space for image
I'm not sure it's possible to pipe to qemu-img.
also, maybe it could be possible with raw source file, but qcow2,vmdk,vhdx have
some headers and specific structure, so it seem difficult.
One way is to implement an nbd serv
Il 2016-01-14 19:28 Stefan Priebe - Profihost AG ha scritto:
The idea is sonething like this:
- add an upload button next to resize for each disk
- use the iso / cd upload code for uploading (current browsers do not
seem to have an upload limit)
- directly pipe to qemu-img so no need to aquire te
Hello All,
The lxc-freeze program loops around until the freezer.state
becomes FROZEN. This can take an unacceptably long time.
Suggested solution/workaround is to add a timeout to invoking lxc-freeze.
Downside is, not all processes are guaranteed to be frozen, but on the upside
any processes pop
lxc-freeze is not guaranteed to return in a reasonable time.
Processes waiting in uninterruptible state stall the freeze.
But when the container is in FREEZING state, processes popping up
will be frozen immediately anyway, so just abort after 15 seconds.
Signed-off-by: Gerrit Venema
---
src/PVE/
Am 14.01.2016 um 18:54 schrieb Dietmar Maurer :
just to be sure. Nobody interested?
>>>
>>> I personally do not need such feature. What is the use case exactly?
>>
>> The idea is to enable people to easily migrate from vmware, xen,
>> virtualbox, local kvm to proxmox. The most common prob
> >> just to be sure. Nobody interested?
> >
> > I personally do not need such feature. What is the use case exactly?
>
> The idea is to enable people to easily migrate from vmware, xen,
> virtualbox, local kvm to proxmox. The most common problem we face is how
> do i get my virtual drives from
On Thu, 14 Jan 2016 17:21:20 +0100 (CET)
Alexandre DERUMIER wrote:
>
> for the upload through gui, I don't known if currently we are able to handle
> big images.
> But maybe upload through ssh is enough.
>
If upload is to be done through gui it needs to be async. Otherwise the
hole gui could f
>>Hi Alexandre,
>>
>>just to be sure. Nobody interested?
For my personnal needs, I don't care because I known how to do it command line.
But during my trainings, I have some students who's want this feature.
But I really don't have time to work on this.
I think it could be done like this:
Il 2016-01-14 16:48 Stefan Priebe ha scritto:
Am 14.01.2016 um 16:46 schrieb Dietmar Maurer:
Hi Dietmar,
Hi Alexandre,
just to be sure. Nobody interested?
I personally do not need such feature. What is the use case exactly?
The idea is to enable people to easily migrate from vmware, xen
Yes!
Not only very usefull for importing vmware images. Also very usefull to import
kvm images of virtual loadbalances, firewalls etc ...
At the moment it is very complicated to do that.
-Ursprüngliche Nachricht-
Von: pve-devel [mailto:pve-devel-boun...@pve.proxmox.com] Im Auftrag von
Di
El 14/01/16 a las 16:48, Stefan Priebe escribió:
Am 14.01.2016 um 16:46 schrieb Dietmar Maurer:
Hi Dietmar,
Hi Alexandre,
just to be sure. Nobody interested?
I personally do not need such feature. What is the use case exactly?
The idea is to enable people to easily migrate from vmware,
Le 13/01/2016 12:17, Timo Grodzinski a écrit :
> Hi,
>
> we plan to enable the user to upload and import disk images (qcow2,
> vmdk, raw, ... ).
>
> Is anyone interested in this feature to go upstream in the public pve repos?
>
> Any suggestions, hints or feature requests?
>
> Best regards,
> T
Am 14.01.2016 um 16:46 schrieb Dietmar Maurer:
Hi Dietmar,
Hi Alexandre,
just to be sure. Nobody interested?
I personally do not need such feature. What is the use case exactly?
The idea is to enable people to easily migrate from vmware, xen,
virtualbox, local kvm to proxmox. The most c
> Hi Dietmar,
>Hi Alexandre,
>
> just to be sure. Nobody interested?
I personally do not need such feature. What is the use case exactly?
Anyways, if the code is clean we can include it...
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http:
Hi Dietmar,
Hi Alexandre,
just to be sure. Nobody interested?
Greets,
Stefan
Am 13.01.2016 um 12:17 schrieb Timo Grodzinski:
Hi,
we plan to enable the user to upload and import disk images (qcow2,
vmdk, raw, ... ).
Is anyone interested in this feature to go upstream in the public pve repos
applied both patches
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
> This fix the problem that multiple ComboGrids were displaying the same
> listConfig.
applied. works as expected.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
> Otherise the lxc.service is restarted when upgrading the
> package causing all containers to be stopped.
>
> Note that this affects the 'prerm' portion of the package so
> upgrading from an older package to this one still performs
> the old version's stop action.
What if we do the following ins
Otherise the lxc.service is restarted when upgrading the
package causing all containers to be stopped.
Note that this affects the 'prerm' portion of the package so
upgrading from an older package to this one still performs
the old version's stop action.
---
debian/rules | 3 ++-
1 file changed, 2
---
PVE/QemuServer.pm | 374 +-
1 file changed, 232 insertions(+), 142 deletions(-)
diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
index 09095fa..7ac09b9 100644
--- a/PVE/QemuServer.pm
+++ b/PVE/QemuServer.pm
@@ -485,38 +485,232 @@ for (my $
---
PVE/QemuServer.pm | 88 ++-
1 file changed, 48 insertions(+), 40 deletions(-)
diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
index c08bb20..09095fa 100644
--- a/PVE/QemuServer.pm
+++ b/PVE/QemuServer.pm
@@ -381,7 +381,6 @@ EODESCR
s
This fix the problem that multiple ComboGrids were displaying the same
listConfig.
---
www/manager6/form/ComboGrid.js | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/www/manager6/form/ComboGrid.js b/www/manager6/form/ComboGrid.js
index 5e8612f..6a90860 100644
--- a/www/manag
29 matches
Mail list logo
