On Thu, 2019-07-04 at 21:06 +0200, Martin Maurer wrote:
> Hi all!
>
> We're happy to announce the first beta release for the Proxmox VE 6.x
> family! It's based on the great Debian Buster (Debian 10) and a 5.0
> kernel, QEMU 4.0, ZFS 0.8.1, Ceph 14.2.1, Corosync 3.0 and countless
Thank you for
> Ran into an interesting problem today. Topology is a 4-Node Cluster on v.5.2,
> been up and running without issues for 10 months or so. Several VMs running
> on node 1, 2 & 3, maybe 30% loaded. I keep node 4 empty for HA and new build
> VM testing. All VMs are set for HA and auto start on
--- Begin Message ---
У пт., 05-го лип. 2019, о 10:19 Gilberto Nunes wrote:
> Hi there! Correct me if I wrong, but after make changes in network still
> need reboot the server?
If you know what you're doing, you can cat interfaces.new > interfaces
and systemctl restart networking or something like
Hi,
On Fri, 5 Jul 2019 10:19:59 -0300
Gilberto Nunes wrote:
> Hi there! Correct me if I wrong, but after make changes in network
> still need reboot the server?
In the default setup this is still correct.
However PVE has the `ifupdown2` package in the repository (since quite
some while - 5.2
Hi there! Correct me if I wrong, but after make changes in network still
need reboot the server?
---
Gilberto Nunes Ferreira
(47) 3025-5907
(47) 99676-7530 - Whatsapp / Telegram
Skype: gilberto.nunes36
Em sex, 5 de jul de 2019 às 06:16, Gilou
escreveu:
> Le 04/07/2019 à 21:06, Martin
Le 04/07/2019 à 21:06, Martin Maurer a écrit :
> Hi all!
>
> We're happy to announce the first beta release for the Proxmox VE 6.x
> family! It's based on the great Debian Buster (Debian 10) and a 5.0
> kernel, QEMU 4.0, ZFS 0.8.1, Ceph 14.2.1, Corosync 3.0 and countless
> improvements and
Le 05/07/2019 à 09:57, Fabian Grünbichler a écrit :
the Corosync upgrade should be pretty pain-free, as long as you follow
the instructions given in the upgrade Guide.
I hope so, I remember the last upgrade from major release of corosync
(3.x to 4.0 for PVE and 1.x to 2.0 for corosync if I
Hi,
On 7/5/19 9:32 AM, mj wrote:
> Looks like a great new release!
>
> Does corosync 3.0 mean that the notes on
> [https://pve.proxmox.com/wiki/Multicast_notes] are no longer relevant?
We will update the documentation and wiki articles regarding this in
the following days, until the final PVE
On Fri, Jul 05, 2019 at 09:10:09AM +0200, Alain Péan wrote:
> It seems that the upgrade from 5.4 to 6.0 will be a hard way. New version of
> Debian, and major version of corosync, 3.0...
new (major) versions of PVE are always based on new Debian releases ;)
the Corosync upgrade should be pretty
Hi Martin,
Thanks a lot for your hard work, Maurer-ITans and the rest of developers...
It seems that in PVE 6.0, with corosync 3.0, multicast won't be used by
default? I think it could be interesting to have a PVE_6.x cluster wiki
page to explain a bit the new cluster, max nodes, ...
Also,
On 7/4/19 8:45 PM, Craig Jones wrote:
Hello,
I have a VM that I'm passing a GPU through to. The passthrough itself
works great. The issue is that whenever this VM is powered on, the host
will reboot without any interaction from me. The reboot happens anywhere
from 3 - 15 minutes after the VM
Thank you for the hard work.
Such an exciting project.
On Thu, 4 Jul 2019 at 21:06, Martin Maurer wrote:
> Hi all!
>
> We're happy to announce the first beta release for the Proxmox VE 6.x
> family! It's based on the great Debian Buster (Debian 10) and a 5.0 kernel,
> QEMU 4.0, ZFS 0.8.1, Ceph
12 matches
Mail list logo
