Search results

  1. V

    [SOLVED] Cluster with Ceph become degraded if I shut down or restart a node

    Given the problem described above I moved on to: osd_pool_default_min_size = 1 AND osd_pool_default_size = 2 I know it's not ideal but now I don't think I can do otherwise. Tonight I will try to shut down a server, as I will need to add a graphics card. I have a question, could the fact that I...
  2. V

    [SOLVED] Cluster with Ceph become degraded if I shut down or restart a node

    Now i have this message: Degraded data redundancy: 189517/12115939 objects degraded (1.564%), 6 pgs degraded, 6 pgs undersized pg 2.d is stuck undersized for 13h, current state active+undersized+degraded+remapped+backfill_toofull, last acting [1,3] pg 2.2f is stuck undersized for 13h, current...
  3. V

    [SOLVED] Cluster with Ceph become degraded if I shut down or restart a node

    I just set osd_pool_default_size = 3 through the webgui. I expected there were only remapped PGs. The reconstruction should finish in two / three hours Tomorrow I try to restart a node to confirm that the change has the desired results.
  4. V

    [SOLVED] Cluster with Ceph become degraded if I shut down or restart a node

    So I could set up osd_pool_default_min_size = 1 or osd_pool_default_size = 3 In the first case I would have more space and less redundancy, in the second the opposite.
  5. V

    [SOLVED] Cluster with Ceph become degraded if I shut down or restart a node

    I have a 4 node cluster with two disks each node. When for maintenance or upgrade of a server I have to shut down or restart a node become degraded. Initially the degraded PGs are exactly half of the total, in the image the reconstruction had started a few minutes earlier. The problem is that...
  6. V

    Nested Hyper-V Virtualization Inhibits VM Startup

    Does it work for more than 24 hours straight?
  7. V

    Opt-in Linux Kernel 5.15 for Proxmox VE 7.x available

    I'm on 5.16 and GPU passingthrough didn't give me any problems.
  8. V

    Nested Hyper-V Virtualization Inhibits VM Startup

    It seems to be talking about a problem related to virtualization nested all in the Windows environment and does not mention AMD environments. But it sure is worth a try.
  9. V

    [SOLVED] Windows guest with hyper-v crashes

    You can try with the 5.15 kernel. https://forum.proxmox.com/threads/opt-in-linux-kernel-5-15-for-proxmox-ve-7-x-available.100936/ The problem seems to be limited to nested Hyper-V on AMD environments.
  10. V

    Nested Hyper-V Virtualization Inhibits VM Startup

    So I don't think there is any hope that this will be fixed. Seems like a kernel-level problem, I'm also trying 5.16 but unsuccessful for now. The other nested virtualizations seem to be fine, I tried another proxmox and virtualbox under windows environment, no problem. The problem is that I...
  11. V

    Nested Hyper-V Virtualization Inhibits VM Startup

    Trying, I found that the problem occurs when activating Hyper-V.
  12. V

    Opt-in Linux Kernel 5.15 for Proxmox VE 7.x available

    Now yes, last BIOS and last micro code. With this instruction: https://wiki.debian.org/Microcode#Debian_10_.22Buster.22_.28stable.29 Windows 11 PRO, i will try Windows server 2022. Please tell me where to find proxmox logs so maybe I can be more helpful in identifying the problem.
  13. V

    VM GPU sharing

    Excuse me if I reassume this post but: How exactly? In servers with multiple unassigned graphics cards in passthrough is there any way to select which one to share?
  14. V

    Opt-in Linux Kernel 5.15 for Proxmox VE 7.x available

    So the problem could be limited to nested Hyper-V (on AMD environments)? I have updated to the latest version of the bios and I always have the same problem. After almost exactly one day the car freezes. I also tried it by making a proxmox installation from scratch and configuring only that VM.
  15. V

    Opt-in Linux Kernel 5.15 for Proxmox VE 7.x available

    On 5.13 I have this problem. This confirms that the problem lies in the proxmox - AMD interaction. Both are out of the question.
  16. V

    Opt-in Linux Kernel 5.15 for Proxmox VE 7.x available

    Have you activated nested virtualization? Because all the other machines work fine However even after the update I have the same problem. After about a day of operation the VM with nested virtualization begins to freeze.