New test this morning.
in VM hardware the firewall was not enabled on the interface.
I have the tap chains created on forward chain.
So the solution VM by VM is working. It will be longer to configure
(need to do it on each VM).
2015-05-13 0:08 GMT+02:00 Flavius Bindea :
> I did tests.
> QEMU c
I did tests.
QEMU chains are not created.
2015-05-12 6:10 GMT+02:00 Dietmar Maurer :
>
>> You are rigth. FirewallSimulator was not adapted to this new chain.
>> I've added this workarround:
>
> Thanks, but I still think adding a FORWARD chain is the wrong way, because
> you can do the same thing
Hello,
Spaces are allowed in order to look like iptables syntax.
I'll add some regression tests.
Regards,
Flav
2015-05-12 8:37 GMT+02:00 Dietmar Maurer :
>> diff --git a/src/PVE/Firewall.pm b/src/PVE/Firewall.pm
>> index 2bdff20..a3b4ccb 100644
>> --- a/src/PVE/Firewall.pm
>> +++ b/src/PVE/Fire
applied both patches, thanks.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
> http://git.qemu.org/?p=qemu.git;a=commit;h=0403b0f539f40a21da60409b825b4653b273ab39
>
>
> does proxmox 4.0 will be based on qemu 2.3 ? or waiting 2.4 in some months ?
We always try to use the latest stable version. So I guess that means we want to
use 2.3 for now (and update to 2.4 when it is
---
bin/spiceproxy | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/bin/spiceproxy b/bin/spiceproxy
index fbeb7a6..07acf32 100755
--- a/bin/spiceproxy
+++ b/bin/spiceproxy
@@ -60,7 +60,8 @@ sub init {
my $lockfh = IO::File->new(">>${accept_lock_fn}") ||
die "unabl
---
src/PVE/API2/LXC.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/PVE/API2/LXC.pm b/src/PVE/API2/LXC.pm
index c565326..4a2e329 100644
--- a/src/PVE/API2/LXC.pm
+++ b/src/PVE/API2/LXC.pm
@@ -651,7 +651,7 @@ __PACKAGE__->register_method ({
my ($remip, $family);
With ExtJS 4, we introduced an override to Ext.grid.feature.Chunking
to fix scrollings problems in the grid when having a high number
of nodes. Ext.grid.feature.Chunking has been removed from ExtJS
in version 5, so we hope either the problem is fixed on ExtJS side,
or we will have to find a differe
---
PVE/ExtJSIndex5.pm | 4
1 file changed, 4 insertions(+)
diff --git a/PVE/ExtJSIndex5.pm b/PVE/ExtJSIndex5.pm
index 1fd6dbc..a3da17b 100644
--- a/PVE/ExtJSIndex5.pm
+++ b/PVE/ExtJSIndex5.pm
@@ -39,6 +39,10 @@ _EOD
+
+
+
+
_EOD
--
2.1.4
___
http://git.qemu.org/?p=qemu.git;a=commit;h=0403b0f539f40a21da60409b825b4653b273ab39
does proxmox 4.0 will be based on qemu 2.3 ? or waiting 2.4 in some months ?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailma
The proxmox-upgrade-4.0 you see is a service pack for the Mail Gateway,
and is unrelated to the Virtualisation Platform.
pve running on top of debian jessie is still devel-only at the momment.
It is not a recommanded production environnment ( this is why we chat
about it in pve-devel ;)
Many
Hello Cesar
On 05/12/2015 01:16 PM, Cesar Peschiera wrote:
> Alexandre, many thanks for the information.
>
> And please, let me to do a questions:
> 1) Should i change the information of his repositories for his future
> updates? (in terms of Debian Jessie and PVE no-subscription), as also,
> wh
Alexandre, many thanks for the information.
And please, let me to do a questions:
1) Should i change the information of his repositories for his future
updates? (in terms of Debian Jessie and PVE no-subscription), as also, what
text should have?.
2) Is this upgrade stable for PVE?, or is onl
---
src/PVE/API2/LXC.pm | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/src/PVE/API2/LXC.pm b/src/PVE/API2/LXC.pm
index a6b2e2e..60ad647 100644
--- a/src/PVE/API2/LXC.pm
+++ b/src/PVE/API2/LXC.pm
@@ -650,14 +650,16 @@ __PACKAGE__->register_method ({
$sslcert
---
PVE/API2/Qemu.pm | 10 ++
PVE/QemuMigrate.pm | 3 ++-
PVE/QemuServer.pm | 9 ++---
3 files changed, 14 insertions(+), 8 deletions(-)
diff --git a/PVE/API2/Qemu.pm b/PVE/API2/Qemu.pm
index c0a6bc3..fae2872 100644
--- a/PVE/API2/Qemu.pm
+++ b/PVE/API2/Qemu.pm
@@ -1299,17 +1299,
---
PVE/API2/Nodes.pm | 10 ++
PVE/API2Tools.pm | 5 -
2 files changed, 10 insertions(+), 5 deletions(-)
diff --git a/PVE/API2/Nodes.pm b/PVE/API2/Nodes.pm
index 1191925..3519117 100644
--- a/PVE/API2/Nodes.pm
+++ b/PVE/API2/Nodes.pm
@@ -680,14 +680,16 @@ __PACKAGE__->register_metho
>>Oh, it is OK!, and where can i find the procedure?
Here my notes
convert cluster.conf to /etc/corosync/corosync.conf
generate /etc/corosync/authkey
#cp /etc/corosync/corosync.conf
#touch /proxmox_install_mode
#apt-get update
#apt-get upgrade
#apt-get remove clvm vzctl
#apt-get dist-upgrade
Hi Alexandre
I have done the upgrade to jessie online, without interruption
(but I don't use drbd, only remote storage which is more easier).
Oh, it is OK!, and where can i find the procedure?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http
If an array is requested, the function now returns ($ip, $family),
otherweise just the IP alone.
Several ipv6 related changes in other packages need to pass the packet
family to functions and will make use of this functionality.
---
data/PVE/Cluster.pm | 28 +---
1 file cha
>>I meant to say for the migration of Debian wheezy to Jessie with PVE 4.0
>>always that the migration online isn't possible.
>>¿is a good idea? or ¿do you have other best idea?.
>>
>>Moreover, about of our conversation, what do you meant with "you need to
>>re-install"?
Hi,
I have done the upgr
applied
On 05/12/2015 09:51 AM, Wolfgang Bumiller wrote:
Adapted the pve-common patchset so next_*_port functions explicitly take a
family argument instead of an array passed to Socket::IP.
Wolfgang Bumiller (2):
add a socket family argument to next_*_port functions
new helper: getaddrinf
Adapted the pve-common patchset so next_*_port functions explicitly take a
family argument instead of an array passed to Socket::IP.
Wolfgang Bumiller (2):
add a socket family argument to next_*_port functions
new helper: getaddrinfo_all
src/PVE/Tools.pm | 28 ++--
1
Instead of assuming a local address of 0.0.0.0, the next_*_port family
of functions now takes an optional packet family argument (AF_INET/AF_INET6),
used for ipv6 support.
---
src/PVE/Tools.pm | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/src/PVE/Tools.pm b/src/
As it's commonly used in ipv6 support code a getaddrinfo wrapper passing
default flags and dealing with the (err,result) tuple was added.
---
src/PVE/Tools.pm | 15 ++-
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/src/PVE/Tools.pm b/src/PVE/Tools.pm
index 0c6e532..018
While in posix gethostbyname(3) does support ipv6, perl's gethostbyname
usually returns wrong results for names, or no results for ipv6
addresses. Since we provide a getaddrinfo helper already, we now use
that instead.
---
PVE/Storage.pm | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(
I supplemented the patch with a description regarding the reason for replacing
gethostbyname. It's simply that perl's gethostbyname doesn't support ipv6 the
way POSIX' gethostbyname(3) does.
An easy way to test this:
$ perl -MData::Dumper -e 'print Dumper(gethostbyname("::1")), "\n";'
While this
26 matches
Mail list logo
