Search results

THX @fabian I restarted the servers :)

Hi @ ALL. Is it possible to rename a Datacenter ? I created the datacenter with the wrong name and would like to rename it again. I already renamed the /etc/pve/corosync.conf cluster name and recounted the version. The name should be "TRIO-RZA" and not "TRIO". Attached a screenshot from the...

We do have the same Problem with pve Version 6.3.3 Mar 25 16:31:19 NODENAME pvedaemon[19173]: VMNAME qmp command failed - VMNAME qmp command 'query-proxmox-support' failed - got timeout Mar 25 16:31:19 NODENAME pvestatd[1942]: VMNAME qmp command failed - VMNAME qmp command...

Hello, We are going to upgrade our PVE 5.4.3 cluster to PVE 6.3. We are using Gluster Storage (currently 3.8.8) for the storage backend. Is there any recommendation regarding the new version of Gluster Storage? Should we go for 5.5-3 (from Debian 10) or for a newer version from gluster.org...

looks like there was a lot of discussion about this issue in 2016: https://pve.proxmox.com/pipermail/pve-devel/2016-December/024488.html

cat /sys/module/vhost/parameters/max_mem_regions 64 referring to this thread this limit should not be 64 anymore in PVE. is there a reason why 64 is the default and what exactly does this parameter do ? is this parameter a size limit for memory hotplug ?

Hi, we have a problem activating memory hotplug on 7 vm's running on a 14 Node V6.1-7 Cluster. These VM's have either 32GB, 97GB or 141GB Ram assigned. When Memory hotplug is activated on these VM's the following message shows when trying to boot: kvm: -device...

Hi, for the 2nd time in only a few days we got a message about a crashed ceph-mon process: root@sv18002:~# ceph crash info 2020-03-09_07:11:48.755203Z_8747897c-939b-4012-9c50-f4e266562f28 { "os_version_id": "10", "assert_condition": "z >= signedspan::zero()", "utsname_release"...

Wow okay :) So you use proxmox to administrate your ceph via GUI in a easy way, right ?

@adamb Nice to hear that! Just one question: Do you use HA? We activated HA and have some problems after a lost node joined back into the cluster.

@RobFantini 1: this is the rule set from the Proxmox GUI :) 2: { "rule_id": 0, "rule_name": "replicated_rule", "ruleset": 0, "type": 1, "min_size": 2, "max_size": 4, "steps": [ { "op": "take"...

Our solution is: # rules rule replicated_rule { id 0 type replicated min_size 2 max_size 4 step take default step choose firstn 0 type datacenter step chooseleaf firstn 2 type host step emit }

@TwiX I just can say that we use a 25G badwidth for the connection between the DC's. I don't think there is a required bandwidth - it only depends on the latency which have to be < 2ms .

ok. then i guess, that somewhere on the installation iso are the default settings, used during the installation, stored. can you tell me where ? i would like to get my pxe installation as close as possible to a iso installation.

Not really. I'm looking for the default settings used during an installation, to get them into my PXE Debian Installation for Proxmox. I guess somewhere on the installation dvd is kind of a preseed file, where the default settings are defined.

Hi, where can i find the default installation settings for the debian of a proxmox installation like partitioning, lvm settings . packages etc. ? Regards Frank

THX Alwin, already got how to edit the crushmap :) I'm now trying to find a good solution for us. @Alwin do you have a good solution for this Problem?

THX Alwin, already got it :)

No there is no supernode for quorum. How I told before we have one other node (in an third datacenter) which don't have any storage or vms on it, only to have one more cluster vote. If one DC becomes fenced the 5 hosts from the 1th DC and the 1 node from the 3th DC becomes the majority so the...

Idk but you can create qdevices for corosync.