Em qui, 11 de abr de 2019 às 12:13, Mira Limbeck
escreveu:
> Hi,
>
> According to
> https://pve.proxmox.com/pve-docs/chapter-pvesm.html#storage_glusterfs
> there's no support for content type 'rootdir' which is required for
> containers.
>
Thank you.
Filipe.
moving my stuff from 3.4, feeling the joy.
Sure hope it will be as reliable as 3.4 was. Darn thing ran forever
On 4/11/2019 11:00 AM, Filipe Alvarez wrote:
Hi,
First, congrats to the new 5.4 proxmox version, its awesome.
We are running a ceph and gluster lab and, we cannot add container
Hi,
According to
https://pve.proxmox.com/pve-docs/chapter-pvesm.html#storage_glusterfs
there's no support for content type 'rootdir' which is required for
containers.
On 4/11/19 5:00 PM, Filipe Alvarez wrote:
Hi,
First, congrats to the new 5.4 proxmox version, its awesome.
We are running
Hi,
First, congrats to the new 5.4 proxmox version, its awesome.
We are running a ceph and gluster lab and, we cannot add container as
content of gluster storage (just disk image).
With ceph, I can add both.
So the question is, is it a limitation from gluster or some error in my
configuration?
Am 11.04.19 um 16:07 schrieb Thomas Lamprecht:
On 4/11/19 2:47 PM, Uwe Sauter wrote:
Thanks for all your effort. Two questions though:
From the release notes:
HA improvements and added flexibility
It is now possible to set a datacenter wide HA policy which can change the
way guests
On 4/11/19 2:47 PM, Uwe Sauter wrote:
> Thanks for all your effort. Two questions though:
>
>
> From the release notes:
>
> HA improvements and added flexibility
>
> It is now possible to set a datacenter wide HA policy which can change
> the way guests are treated upon a Node shutdown or
Thanks for all your effort. Two questions though:
From the release notes:
HA improvements and added flexibility
It is now possible to set a datacenter wide HA policy which can change the
way guests are treated upon a Node shutdown or
reboot. The choices are:
freeze: always freeze
Thanks for the comments, seems these cards support SR-IOV, and it was
disabled in the bios, enabling all interfaces to be seen.
Been running older PVE for years, thought it might just be an update.
But things are different and hopefully this will be a good thing overall
if SR-IOV really
Nice job
Thanks a lot
---
Gilberto Nunes Ferreira
(47) 3025-5907
(47) 99676-7530 - Whatsapp / Telegram
Skype: gilberto.nunes36
Em qui, 11 de abr de 2019 às 07:10, Martin Maurer
escreveu:
> Hi all!
>
> We are very pleased to announce the general availability of Proxmox VE 5.4.
>
> Built
In dmesg output, are there lines like "e1000e :00:19.0 enp0s25: renamed
from eth0" ?
The question I see is: are all of your interfaces detected but Udev is doing
something wrong or does the kernel not detect all
interfaces (besides it seems to see all PCIe devices).
You could try to create
So I'm missing enp68
On 4/11/2019 8:02 AM, Dominik Csapak wrote:
hi
On 4/11/19 1:48 PM, David Lawley wrote:
not so fast.. borked network settings so I did a another fresh
install, if enpX is the physical location I am at a loss where it
gets enp67?? By this example I would assume I
hi
On 4/11/19 1:48 PM, David Lawley wrote:
not so fast.. borked network settings so I did a another fresh
install, if enpX is the physical location I am at a loss where it gets
enp67?? By this example I would assume I want enp43s0f0 ... etc
hex 43 = dec 67
pve gui shows
enp8s0f1
not so fast.. borked network settings so I did a another fresh
install, if enpX is the physical location I am at a loss where it gets
enp67?? By this example I would assume I want enp43s0f0 ... etc
pve gui shows
enp8s0f1
enp8s0f0
enp7s0f1
enp7s0f0
enp67s0f1
enp67s0f0
lspci shows
Hi all!
We are very pleased to announce the general availability of Proxmox VE 5.4.
Built on Debian 9.8 (Stretch) and a specially modified Linux Kernel
4.15, this version of Proxmox VE introduces a new wizard for installing
Ceph storage via the user interface, and brings enhanced flexibility
14 matches
Mail list logo
