OK, it is not possible to implement this, because qemu only allows
a single qmp connection. So if we keep a connection open to get events,
we would block everything else.
Yes, maybe with some kind of proxy daemon
qmp command --- qmp proxy daemon-events---qemu process
But that mean another
OK, it is not possible to implement this, because qemu only allows a
single qmp connection. So if we keep a connection open to get events,
we would block everything else.
Yes, maybe with some kind of proxy daemon
qmp command --- qmp proxy daemon-events---qemu process
But that
Hi,
On 08/11/14 11:02, Dietmar Maurer wrote:
SCENARIO: proxmox HA cluster, VM images exclusively on RBD
GOAL: use Ceph auth for fencing
Currently this can't be done, but I think the following changes would allow it:
- Move storage client auth keyring from /etc/pve/priv/ceph to somewhere
Below command does not work for me:
# ip6tables -A INPUT -m addrtype --dst-type MULTICAST -j DROP
ip6tables: No chain/target/match by that name.
Any ideas whats wrong?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
# ip6tables -A INPUT -m addrtype --dst-type MULTICAST -j DROP
ip6tables: No chain/target/match by that name.
Any ideas whats wrong?
Strange, It's working for me (kernel 3.10)
#ip6tables -A INPUT -m addrtype --dst-type MULTICAST -j DROP
# ip6tables-save
# Generated by ip6tables-save
Does not work with 2.6.32. But maybe we can simply use
-d ff00::/8
to match ipv6 multicast traffic?
-Original Message-
From: Alexandre DERUMIER [mailto:aderum...@odiso.com]
Sent: Montag, 10. November 2014 11:39
To: Dietmar Maurer
Cc: pve-devel@pve.proxmox.com
Subject: Re: ipv6
On Tue, 11 Nov 2014 00:27:46 +0100
Michael Rasmussen m...@datanom.net wrote:
Hi all,
Just to let you know. I have started implementing the feature for
applying maintenance mode to a node. Right-click on any node will open
a context menu which, at the moment, only contains one item:
Option 4, You could have a drop down box with a default selection of
Distribute Evenly then a list of all available nodes.
This would allow the user to just click through and have them distribute
evenly, OR they could select a specific node.
On Tue, Nov 11, 2014 at 12:32 PM, Michael Rasmussen
Agree with Andrew on this one. I could also see default migration paths
being defined somewhere, such that when a node goes into maintenance mode,
VMs are migrated to the preconfigured target node, with a fallback to the
user-selected mode (that is, distribute evenly, or distribute to selected
Option 4, You could have a drop down box with a default selection of
Distribute
Evenly then a list of all available nodes.
For each VM?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Would a shutdown option for VM's make sense?
On 11 November 2014 09:32, Michael Rasmussen m...@datanom.net wrote:
On Tue, 11 Nov 2014 00:27:46 +0100
Michael Rasmussen m...@datanom.net wrote:
Hi all,
Just to let you know. I have started implementing the feature for
applying maintenance mode
Would a shutdown option for VM's make sense?
I think there would be situations where that would make sense. We have
suspend now, too, so it would make sense to add that to the list as well.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
12 matches
Mail list logo
