Latest activity

What's new Featured content New posts New profile posts Latest activity
  • J
    Johannes S reacted to UdoB's post in the thread Upgrade von 6.3-2 with Like Like.
    Boah! Da steht: Ich hätte das eine TB DDR4 RAM :-) Das Ding wird vermutlich durchaus das tun, was es verspricht. Aber: man kann halt nix erweitern. Und "Dual 4K" sind für einen Einsatz als Pseudo-Server genauso verschenkt wie "WiFi 2.4G + 5.0G...
  • J
    Johannes S reacted to bbgeek17's post in the thread NVMe Over TCP - Proxmox VE with Like Like.
    A few notes based on our experience with NVMe/TCP and PVE: Your performance expectation should come from your storage stack, not your choice of protocol. The transport is usually not the bottleneck in setups like this. If you're seeing latencies...
  • J
    Johannes S reacted to JoaGamo's post in the thread High Latency on a new HDD-disks (ceph) with Like Like.
    As already said, 80-100ms latency is very normal for HDDs If you want to improve Ceph performance on the HDD pool, consider offloading WAL + RocksDB to a SSD for HDD OSDs. The safest method implies you have to evacuate each existing HDD OSD...
  • J
    JoaGamo replied to the thread High Latency on a new HDD-disks (ceph).
    As already said, 80-100ms latency is very normal for HDDs If you want to improve Ceph performance on the HDD pool, consider offloading WAL + RocksDB to a SSD for HDD OSDs. The safest method implies you have to evacuate each existing HDD OSD...
  • N
    NevadaTech replied to the thread [SOLVED] Proxmox crashing, hardware issue?.
    Yes, I agree completely. The similarity+constant is why I thought the DIMM was bad. In one maintenance window I pulled the RAM and installed it reverse order. I also let the mobo dictate the default memory settings. I sure there are ways to eek...
  • I
    informant posted the thread failed to query local AF_VSOCK CID in Proxmox VE: Installation and configuration.
    Hi i have since last proxmox update in one vm following error: what is it, it dont comes before. i have solve as workarround it with nano /etc/default/grub systemd.ssh_auto=no update-grub reboot any ideas?
    • 1784644708330.png
  • J
    JoaGamo replied to the thread Proxmox VE Ceph Benchmark 2023/12 - Fast SSDs and network speeds in a Proxmox VE Ceph Reef cluster.
    See the updated documentation here with OpenFabric https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server
  • N
    NevadaTech replied to the thread [SOLVED] Proxmox crashing, hardware issue?.
    About 2 days ago I updated the AMD-microcode waited for a couple hours and no CPU/memory errors showed up on the console, the AMD-Vi wait loop still appeared but it seemed a little less frequent (seemed or reality?) shutdown I then went into...
  • jsterr
    jsterr reacted to bbgeek17's post in the thread NVMe Over TCP - Proxmox VE with Like Like.
    A few notes based on our experience with NVMe/TCP and PVE: Your performance expectation should come from your storage stack, not your choice of protocol. The transport is usually not the bottleneck in setups like this. If you're seeing latencies...
  • T
    TErxleben replied to the thread Upgrade von 6.3-2.
    Wenn du verlässliche Sicherungen hast, dann reicht das zur Installation. Nur am Rande: Ich nutze da z.B. gerne einen Stick mit Ventoy, statt einen bootable Stick pro SW. Ein HW-Wechsel ist völlig unnötig.
  • U
    uzumo reacted to bbgeek17's post in the thread NVMe Over TCP - Proxmox VE with Like Like.
    A few notes based on our experience with NVMe/TCP and PVE: Your performance expectation should come from your storage stack, not your choice of protocol. The transport is usually not the bottleneck in setups like this. If you're seeing latencies...
  • jsterr
    jsterr replied to the thread Proxmox VE Ceph Benchmark 2023/12 - Fast SSDs and network speeds in a Proxmox VE Ceph Reef cluster.
    Full meshed with sdn fabric (openfabric) is the way to go. See the 9.0 Release Video for a quick introduction.
  • B
    BerndZ replied to the thread Upgrade von 6.3-2.
    Kann aber auch sein, dass ich das jetzt falsch interpretiert habe
  • B
    BerndZ replied to the thread Upgrade von 6.3-2.
    ThoSo hat die Frage vorhin gestellt, ob es nicht sinnvoll wäre, im Zuge der Modernisierung auch die Maschine zu ersetzen. Daher dachte ich, dass es wegen dem Alter sinnvoll wäre. Diese Aussage klingt jetzt eher so als wäre das (noch) nicht...
  • J
    john-tapestry replied to the thread Utilizing PMG with Office 365.
    Finally had another moment to work on this. running SA update leads to this error. Timeout::_run: check: no loaded plugin implements 'check_main': cannot scan! Check that the necessary '.pre' files are in the config directory. At a minimum...
  • W
    wendellrodriguez reacted to Jens-Complea's post in the thread Migration from VMware with Like Like.
    It worked with VM number 2 also. So, it seems to work with the more direct injection of the SCSI driver.
  • bbgeek17
    bbgeek17 replied to the thread NVMe Over TCP - Proxmox VE.
    A few notes based on our experience with NVMe/TCP and PVE: Your performance expectation should come from your storage stack, not your choice of protocol. The transport is usually not the bottleneck in setups like this. If you're seeing latencies...
  • T
    TErxleben replied to the thread Upgrade von 6.3-2.
    Das Ding ist für deine Anforderungen völlig i.O.
  • B
    BerndZ replied to the thread Upgrade von 6.3-2.
    Intel NUC i3 10. Gen - gekauft 12/2020, hergestellt 07/2020 Samsung 970 EVO Plus NVMe M.2 SSD, 1 TB
    • Proxmox3.jpg
  • U
    uzumo reacted to tschmidt's post in the thread [SOLVED] Some Windows VMs start with incorrect clock with Like Like.
    It isn't enforced. It's set when the VM is started, then left alone. Expect some drift if you don't shut down regularly. (Soft reboots don't count.) (Additionally that "explanation" makes no sense to me at all)
Show older items
Top Bottom
Back