Search results

Case: Proxmox cluster with three nodes, connected to a powerblock. The powerblock is then connected to the APC. APC: connected with USB to one node. I wonder what would be a decent solutions, in order to gracefully shut down VMs and nodes, when a blackout happen, and the battery starts to run...

Not sure if this is the right place, but currently I'm rethinking my Proxmox cluster and I just need a little clarification. This is because I recently read a bit about CEPH, and also because I discovered the Thinkpad Tiny. Since this model can carry a Low Profile PCIe NIC. Setup: 2 x Elitedesk...

Would there be any complications by using the XFS-filesystem for the VM, while the Proxmox datacentre storage actually uses a ZFS-filesystem? I know its not best practice to use ZFS on ZFS, but I wonder if thats true for XFS on ZFS as well?

Update: Well, seems like its only the VM that does not get an IP address. Other VMs get an IP address from the second network card. For the VM, the interface / card was visible, but I had to add a new connection with nmtui. After this, the device was listed in nmtui as beeing activated. Also...

So far I've read the Samsung SM883 would be great in general. Would that be so? There are also PM883s and cost 50% compared to the SM883. Are they both do their job, without queuing a regular (VM) Windows 10 update for example? I've been using 2 PNY CS900 and they hit the limit pretty fast...

Proxmox is using a ZFS raid1 storage. On there, a disk has been created for a VM. This disk is currently formatted as ext4. Does that make sense? I guess its up to me. I'm just double checking. I might format the disk to ZFS, since it has the ability to check integrity.

Can't speak advanced Debian language, but I just installed Proxmox a week ago. 1) I wanted to change the physical port to access Proxmox GUI. - Could not get it done from the GUI - I could get it done from /etc/interfaces > just by replacing the interface name - It worked great at it's new port...