Yes is true about snapshot but needs to use qcow2 image format.
Also, remember to check preallocation to off, in order to thinprovisin works properly.
https://pve.proxmox.com/pve-docs/chapter-pvesm.html
Hi @Gilberto Ferreira
Yes, I have seen that is a problem with IPv6. My LAN interface of Synology had activated this and it was the reason for the leg error messages.
I have disable IPv6 in the LAN interface of Synology and the messages have...
I think turns the VM into a template or even clone it would be a more efficient way to deal with it.
Just move the vm config to another folder doesn't fix the issue, because the VM virtual disk will be there anyway.
This could be lead for...
[ SOLVED ] After iDrac reset everything seems to be in order.
Hi there.
I have two Proxmox 8.3.4 running in a R650xs.
On of them is ok.
But the other, the fun ran at full speed all the time.
So they called Dell Support and Dell said that the...
I assume it will work, but haven't tested this myself!
Looking at the date of the article and the history of our full-mesh article, it appears that it was written just a few months before we added the "routed with fallback" option, which is based...
Hi... Thank you for your considerations. The article that I sent in the opening thread, mention something about use the loopback interface, IPv6 and OSPF. Should this set up work out of the box?
Thanks
We have some customers who set up a 5-node full mesh with the OpenFabric variant by using 4-port 25 Gbit NICs. But those were all full Ceph nodes AFAIR. Seems to be working quite well for them and up to 5 nodes is still manageable regarding the...
Thank for your reply.
Unfortunately my customer has 4 server and since ceph cluster is better in odd servers, we figured out that add a low profile machine as a 5th node will be a solution.
But he can afford to have a good switch for do a...
Hello @Gilberto Ferreira
For mesh is recommended 3 node cluster, if you have more nodes or plan to expand, go with switches.
https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server
L
Edit: correct link
Hi there.
I want to create a full mesh network cluster with 5 nodes.
So, I went ahead and found this tutorial, which is for 3 nodes but I intend to adapt to work with 5 node. (1 of them, the 5th node will be only for quorum!)...
So I have this issue today as well, with two servers which dispite has the same processor, one has two and the other has just one (we are waiting for a shippiment).
Using host doesn't work.
Using x86-64-v2-AES works as expected.
And I have such an experience. Proxmox 8 is already installed. and the problem seems to be when using the Host processor type. This type was chosen in order to use more than 512 GB of RAM on a VM. Otherwise, YOU would not have started.
Hi there...
Before create a cluster with 2 servers, I changed it's name from sp1-pd... to proxmox01 and proxmox02.
A name more suitable, indeed!
Now, I don't no why, but there is a mistery rubbish in the HA Stack, like showing in the image...
Although is not encourage, you can compile a custom kernel for yourself. Not an easy task, I might add.
Here some instructions:
https://forum.proxmox.com/threads/proxmox-ve-8-0-mainline-kernel-builds.135375/
Let me know about your progress...
I forked and modified the Proxmox kernel repo to build mainline releases with their modifications. The modifications I made feels like a fair amount of duct tape was used to make this work. But for now, it compiles mainline builds and I'll get...
Is there any plan to support linux 6.12 for an incremental release? Or perhaps the next major release. There have been some massive performance improvements merged into 6.12 and, especially for virtualization tooling, it would be a shame to miss...