Search results

  1. B

    Proxmox Datacenter Manager - First Alpha Release

    Ah, so even if cluster quorum is broken, you can access individual nodes via the DC UI? That is useful.
  2. B

    Proxmox Datacenter Manager - First Alpha Release

    Very interesting. One question - if you're running a single small cluster, i.e a typical homelab or SMB setup, is there much advantage to using Datacenter over the std cluster UI, or is it more aimed at large multiple cluster setups?
  3. B

    Proxmox VE 8.4 released!

    Be interesting to see how it works for you, I tried it between two different model Intel GPU's, no surprise, that died on its ass :) But still great for offline migrations.
  4. B

    Proxmox VE 8.4 released!

    A Resource Mapping? their an option in the Mapping for allow live migrations.
  5. B

    Proxmox VE 8.4 released!

    Would a Virtiofs passthrough of a ZFS Mount be suitable as a datastore for a PBS VM?
  6. B

    Proxmox VE 8.4 released!

    If you have console access, on boot, choose an earlier kernel
  7. B

    Proxmox VE 8.4 released!

    Oh awesome, that would be perfect. Count me in for testing!
  8. B

    Proxmox VE 8.4 released!

    Yeah its tempting. I'm using the lxc for docker to run a media stack (plex + arrs) and it works pretty well apart from the bind mount for the media dir. I did have it properly mapped, uid and guid were correct in the lxc, but had weird access permissions errors with writing stuff to it. The src...
  9. B

    Proxmox VE 8.4 released!

    Any chance of virtiofs being available for containers? would love an easier alternative for unprivileged containers than bind mounts. Getting the uid/gid mappings correct is a nightmare.
  10. B

    Proxmox VE 8.3 released!

    I'm on 6.8.12-4-pve, not seeing any 6.11 in the repos. Edit: Found it, was showing in cmd line auto complete for some reason. Installed, we'll see how it goes. Thanks.
  11. B

    Hard reboots and lockups since PVE 8.2 => 8.3

    No worries! I ended up installing both :) Also fixed up my quorum votes. I've had no issues since then, so hopefully one of those fixed the issue. Thanks!
  12. B

    Hard reboots and lockups since PVE 8.2 => 8.3

    Updated to the latest earlier this year No I do not, though my cpu is a i5-11500, would the intel microcode be the one to use? I'll schedule some downtime for that. Thanks!
  13. B

    Hard reboots and lockups since PVE 8.2 => 8.3

    Sorry, yes I do Would uploading the dmesg.tx be sufficient? root@px-server:/var/lib/systemd/pstore/173240759# ls -lah total 227K drwxr-xr-x 2 root root 45 Nov 24 10:33 . drwxr-xr-x 3 root root 3 Nov 24 10:33 .. -rw------- 1 root root 1.4K Nov 24 10:19 dmesg-efi_pstore-173240759601001...
  14. B

    Hard reboots and lockups since PVE 8.2 => 8.3

    Thanks, yah I just noticed the quorum issue while checking things, have updated it. pvecm status Cluster information ------------------- Name: blackpaw Config Version: 3 Transport: knet Secure auth: on Quorum information ------------------ Date: Wed Nov...
  15. B

    Hard reboots and lockups since PVE 8.2 => 8.3

    nb. ceph has been uninstalled, looks like it needs more cleanup :)
  16. B

    Hard reboots and lockups since PVE 8.2 => 8.3

    No HA Enabled. I did notice I had Quorum votes set to 2 for the main node, total of 4 for the cluster, a hangover from when I only had 2 nodes. Have set it back to 1 vote, dunno if that could have munged things? Nov 25 23:16:14 px-server ceph-crash[1686]: WARNING:ceph-crash:post...
  17. B

    Hard reboots and lockups since PVE 8.2 => 8.3

    @mira As per the title, my main server (part of a 3 node cluster) has been rebooting or locking up daily since upgrading to 8.3, it runs 8 containers and a windows vm. Headless, so I can't see whats on the console :( journalctl --since '2024-11-24'|grep -i panic Nov 24 10:33:58 px-server...
  18. B

    Proxmox VE 8.3 released!

    I've had several hard reboots or lockups a day on my main server since updating from 8.2 to 8.3, sorry, not a lot to go on, its headless. Is there any logs I can look into after the fact? Should I try pinning a previous kernel version, see if that helps?