Recent content by alexskysilk

  1. A

    Proxmox Install Failing on R740xd - PERC H730P

    the (much) greater likelihood is that this disk is failing. have you run a smart test? (smarctl --test=long /dev/sda) Assuming the drives are NOT bad, next is to run a full lifecycle upgrade. has the problem gone away? If not, your machine is likely defective- and its probably NOT your perc...
  2. A

    Proxmox VE 9.1.1 – Windows Server / SQL Server issues

    thats a completely normal behavior for windows. It happens to me on a desktop- explorer really likes to cross all the t's and dot all the i's. if you want faster file copy use a different tool (eg, robocopy.) Not sure if that relates to the initial topic, but this behavior is not at all relevant...
  3. A

    New Cluster for VMware migration

    I dont believe NFS is an option on an IBM FlashSystem 5200- maybe yours is a different product?
  4. A

    Best architecture for running 50+ VDSs each with its own Proxmox VE on a large Dedicated Server (2 TB RAM)

    well then, I dont have any useful advice for you. go forth and prosper :)
  5. A

    Best architecture for running 50+ VDSs each with its own Proxmox VE on a large Dedicated Server (2 TB RAM)

    makes a lot more sense- but still doesnt answer why you want the vps to run proxmox. Also, in this configuration you really want to use shared storage and not local drives. you can still use nvmes with ceph.
  6. A

    Best architecture for running 50+ VDSs each with its own Proxmox VE on a large Dedicated Server (2 TB RAM)

    because its dumb. YOU might convolute a way to make it make sense; in my world, customers pay me to AVOID complexity. again, the product is the VM.
  7. A

    Best architecture for running 50+ VDSs each with its own Proxmox VE on a large Dedicated Server (2 TB RAM)

    so the PRODUCT is 20 VMs, not a hypervisor.
  8. A

    Best architecture for running 50+ VDSs each with its own Proxmox VE on a large Dedicated Server (2 TB RAM)

    Thats... absurd. you're wasting all those resources without any benefit; a cluster is of no value if all resources are HOSTED BY THE SAME DEVICE.
  9. A

    Best architecture for running 50+ VDSs each with its own Proxmox VE on a large Dedicated Server (2 TB RAM)

    This is how I look at it. You are offering to operate a bus for people. but instead of selling seats, you are putting busses inside your bus. Whats the use case?! If you're trying to offer a customer resources that they can distribute between disparate vms, thats simple enough to do WITHOUT...
  10. A

    Best architecture for running 50+ VDSs each with its own Proxmox VE on a large Dedicated Server (2 TB RAM)

    you use the word "need" in a context I dont understand. This isn't a rational product offering as far as I can tell.
  11. A

    Best architecture for running 50+ VDSs each with its own Proxmox VE on a large Dedicated Server (2 TB RAM)

    You dont. I dont understand the use case enough to comment on the wisdom of the solution; please explain what you mean by VDS, and why you want proxmox inside them.
  12. A

    Best architecture for running 50+ VDSs each with its own Proxmox VE on a large Dedicated Server (2 TB RAM)

    no. There is almost NEVER a use case for nested hypervisors except for development/lab use. Even if we assume there are no cpu/ram performance degradation that occurs with modern VT extensions (hint: there are) the consequences of cascading memory space governors and another level of write...
  13. A

    Best architecture for running 50+ VDSs each with its own Proxmox VE on a large Dedicated Server (2 TB RAM)

    mapping individual disks to vms is almost never the correct approach. You can and should present a dedicated vdisk on a highly performant, highly available storage option instead of bifurcating it and offering neither. Beyond performance, having a modern CoWFS under the vdisks provides fault...
  14. A

    [SOLVED] Streched unbalanced cluster

    my bad. ignore me.
  15. A

    [SOLVED] Streched unbalanced cluster

    The number of nodes isnt the issue; understand that since all data is replicated between site a and site b, you can only use the capacity of the smaller side no matter what you do- there is no benefit to having more OSD space on one side.
See more
Top Bottom
Back