Thanks for this. It proved to be very helpful. I was working on installing a GPU in my server and sometimes when accessing the GPU from a VM the host would reboot. My BIOS settings matched what you have here except for the I/OAT DMA Engine (I...
I am quite in agreement of the points raised above regarding shared LVMs across multipath-ed FC LUNs.
We migrated our VMware setup (def not so large as yours) a while back to Proxmox VE and chose this storage approach.
One point you raised...
Greetings, Sensei!
Thank you for your comments; I agree and appreciate the feedback!
I’ve added the suggested warning and clarified some configuration options, as I didn't have this specific PC on hand when I wrote the article.
However, the...
At some point you end up with the question whether you really want any potential customer who gets fed up with vmware. Like you don't want customers who take resources due to not having competent admins on their own and thus are filing tickets...
You've got it. That's exactly why SUSE put OCFS2 on corosync, kernel DLM and Pacemaker. One membership, one fencing authority.
As for doing the same on PVE... someone still has to pay to develop, debug, and support it. Not my circus not my...
Upgraded to proxmox 9.2.10 on Sunday September the 6th.
Have had two downtimes of a host because of that since.
Both downtimes occurred during the Proxmox Backup of some other machines which places an extra burden on the physical disks. And in...
This is for a commercial setup, right? And you are starting from scratch, without much experience, right?
If both is true you need either an external consultant (as @LnxBil already mentioned) or a lot of time.
You mentioned "DR", Desaster...
https://proxmox.com/en/products/proxmox-backup-server/overview and https://pbs.proxmox.com/docs/
https://proxmox.com/en/partners/find-partner/explore
EDIT: You are asking very broad/generic questions and give almost no context. This will only...
Proxmox Backup Server is the answer, if you want to use other backup software, please ask in their respective forums.
It is also highly advised to use a Proxmox consultant for commercial best practices which also helps with implementation...
ok, my bad :)
If the Samsung T7 was already connected to the pve1, and the cluster was created on pve1, then the storage configuration should already have been part of /etc/pve/storage.cfg on pve1.
When pve2 was joined, storage configuration...
First I must admit that I really didn't know which script is responsible. It just didn't matter to me - as it just did work. Always.
And now I had to check :-)
This one is it (probably):
~# grep -R reboot-required /etc/kernel/ /lib/kernel/...
No need to worry as already told.
More context:
- https://www.linuxatemyram.com/
- https://forum.proxmox.com/threads/fabc-why-is-proxmoxve-using-all-my-ram-and-why-cant-i-see-the-real-ram-usage-of-the-vms-in-the-dashboard.165943/
Hello Roland,
Just for your information,
I have the same in my lab.
pve1 pveproxy[1165]: worker 107438 finished
pve1 pveproxy[1165]: starting 1 worker(s)
pve1 pveproxy[1165]: worker 120699 started
pve1 pveproxy[120695]: got inotify poll request...
ok, my bad :)
If the Samsung T7 was already connected to the pve1, and the cluster was created on pve1, then the storage configuration should already have been part of /etc/pve/storage.cfg on pve1.
When pve2 was joined, storage configuration...
Okay - I think I follow, but just to be sure, because it happened like this:
The SamsungT7 USB disc is attached to the first pve node since well when that node was created a year or two ago (it was a 8.2, nowdays upgraded to 9.2.x), which is...
By the way, I also reproduced the issue on AlmaLinux 10.1 (kernel 6.12.0-124.52.1.el10_1.x86_64) with this command :
fio --name=stress-hdd --ioengine=libaio --iodepth=8 --rw=randwrite \
--bs=4k --direct=1 --fdatasync=8 --size=20G --numjobs=4...
I think the problem is that the USB storage was configured only on pve2 before it was added to the cluster.
Since the cluster was created on pve1, the /etc/pve configuration from pve1 becomes the cluster configuration and is synced to the other...
No problem, nobody' perfect. I'm happy that you can help with my problem. OK, great so;
unmount /mnt/pve/ISO_Storage
AND
unmount /mnt/pve/Synology
these will unmount the ext4 and nfs drive shares,
and just so I know my way back after...