longer's latest activity

  • L
    longer replied to the thread VM Migration error.
    Share your storage config: ~# cat /etc/pve/storage.cfs
  • L
    longer replied to the thread migrating machines in case extern network fails.
    Did you test this and got the error above? I assume since the migration network on a different network it should work, assuming you still have corosync quorum on the other nodes.
  • L
    longer replied to the thread Server 2025 High CPU.
    @mubbasher.hussain any updates?
  • L
    longer replied to the thread Proxmox VE 9.1 installation process does not recognize keyboard and mouse.
    Cool, thanks for sharing
  • L
    longer replied to the thread Moving from 8.4 to 9.2.
    Your observed problem sound like the described known issue: https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Network_Interface_Name_Change
  • L
    longer replied to the thread ceph 1 daemons have recently crashed.
    Always welcome. I will keep an eye on the thread. In case it reoccur share journalctl again covering issue time: root@pve2 :# journalctl --since "2026-07-xx xx:00" --until "2026-07-yy yy:yy" > /tmp/syslog.txt.gz
  • L
    longer replied to the thread ceph 1 daemons have recently crashed.
    Once finish editing and saving that file, please proceed with recreating the monitor using the Proxmox GUI.
  • L
    longer replied to the thread ceph 1 daemons have recently crashed.
    Okay, so 10.10.10.2 is still listed at the end of the mon_host line inside the [global] section. You can use your preferaed editor and delete the ip: 10.10.10.2. make a copy of the file before making any change.
  • L
    longer replied to the thread ceph 1 daemons have recently crashed.
    can you share: ~# cat /etc/pve/ceph.conf
  • L
    longer replied to the thread ceph 1 daemons have recently crashed.
    Please try without the -k option: root@pve2 :# journalctl --since "2026-07-27 22:00:00" --until "2026-07-27 23:30:00" > /tmp/syslog.txt.gz
  • L
    longer replied to the thread ceph 1 daemons have recently crashed.
    You can attempt again after couple of minutes, if still same issue check: - Check the Active Mon Map ceph mon dump
  • L
    longer replied to the thread Proxmox doesn't have internet access.
    As @daanw said, you network interfaces are all down, double check the Physical server cables connections and also on the switch side.
  • L
    longer replied to the thread Cant acces to webGUI after trying to change the node/hostname name.
    Just posting Proxmox wiki: https://pve.proxmox.com/wiki/Renaming_a_PVE_node
  • L
    longer replied to the thread VirtIO Block or IDE.
    Oh you already have thread about this: https://forum.proxmox.com/threads/migration-of-windows-server-2003.185331/
  • L
    longer replied to the thread ceph 1 daemons have recently crashed.
    So at the moment, the daemon successfully restarted, and running for more than hour. Looking at journalctl may provide related information, so the last crash from shared crash info was at 2026-07-27 23:21, therefore take look what happend before...
  • L
    longer replied to the thread Proxmox VE 9.1 installation process does not recognize keyboard and mouse.
    Not really sure, but did you verify different port portv2 and v3 to see if any differences? Just my 2 cent, Do you have IPMI/iDRAC? maybe you can attempt from IPMI console and check this issue after booting.
  • L
    longer replied to the thread VirtIO Block or IDE.
    The recommendation is to use virtio dirvers for best performance: https://pve.proxmox.com/wiki/Windows_2003_guest_best_practices In the wiki its also mentioned: "the latest VirtIO iso do not include drivers for Windows 2003. You need to download...
  • L
    longer replied to the thread ceph 1 daemons have recently crashed.
    Is it always mon.pve2 ? You could attempt to destroy and create this mon in case other mon are fine. Could you also share: ~# ceph status
  • L
    longer replied to the thread Server 2025 High CPU.
    Is the high CPU usage showing up inside the Windows Guest (Task Manager), or on the Proxmox Host GUI? If inside the Windows VM What specific process is consuming the CPU? I would suggest to test to: - Increase the assigned core to e.g 8 cores...
    • testing.png
  • L
    longer replied to the thread Server 2025 High CPU.
    hmmm there currently known issue explained in: https://forum.proxmox.com/threads/windows-server-2025-cpu-suddenly-at-100.184763/post-861490 Where its recommended to use CPU type other than host CPU. So you can roll out this and keep CPU type as...
Show older items
Top Bottom
Back