Search results

  1. T

    Sudden PowerOutage fail proof?

    Power is always a cause of issues! You can have disks that haven't been properly written to, causing failures of either the host or guest(s). If you want a reliable server you can trust, reliable power you can trust is a must. Most people would install a UPS and then run some sort of UPS...
  2. T

    clean old kernels

    No, this is community support. If you're a paying customer, you'd use the ticket system. I'm sorry you think I'm a bug. Good luck with being shouty.
  3. T

    clean old kernels

    @UHL-Services It's free software. If you don't like the support you're getting, for free, running free software, go elsewhere. This is community support, if you want official support, pay for it. I don't even know why I am bothering to answer your question, but I will anyway. You don't use...
  4. T

    vlc stream

    You probably need to turn off hardware offload or similar on your VM's NICs. You don't give any deatils though so it's impossible to guess :)
  5. T

    Proxmox VE is 10 years old!

    Proxmox is amazing. Thank you. Here's to another great 10 years (I've only been using it for about 10 weeks!)
  6. T

    [SOLVED] Proxmox and ram /swap usage

    You should read this. What's you're seeing isn't a problem, even though you assume it is. Basically, Linux is moving your memory that hasn't changed/been modified in a while to swap, and using your actual physical RAM for cache/active memory. This is almost always a good thing for performance...
  7. T

    pve file missing after unistall of smartctrl

    You probably need to edit your /etc/apt/sources.list.d/pve-enterprise.list to include use the pve-no-subscription repo. Then you'll be able to install things.
  8. T

    4.15 based test kernel for PVE 5.x available

    Running Linux orbit 4.15.15-1-pve #1 SMP PVE 4.15.15-6 on a QOTOM i5 box and it's working fine. I even notice that my Intel NICs now are using MSI-X interrupts. With 4.13 it was only using MSI interrupts.
  9. T

    Proxmox Server power off

    Whatever you want?? Usually you should ensure the guest VM's are shutdown before you shutdown proxmox. If you have the guest tool installed, the guest should get notified when the host it shutting down and shut themselves down nicely.
  10. T

    Prox' LXC exposes info like load from host in top/htop

    The main thing that annoys me is "dmesg -c" in a LXC wipes the logs messages from the primary host! Maybe there's a way to fix this too. But it's just part and parcel of LXC's. They're not 100% seperation.
  11. T

    Should I turn off TSO and GSO on vmbr0?

    Dragging up an old thread here, but there's this post on reddit yesterday that said his performance improved once he disabled hardware offload on the interfaces on the virtual bridges. I just wish I could find some concrete evidence either way about this, so far it's all "well I tried X and it...
  12. T

    [SOLVED] Apparmor preventing LXCs starting after update

    I guess neither of these two have either a) a proper subscription or b) like me, use the pve-no-subscription repo. If you only upgraded using the default apt entries (And you did not have a valid sub), it would be possible to get into this situation I guess?
  13. T

    Enable MTU 9000 Jumbo Frames

    For the avoidance of doubt for anyone else coming to this topic, this is the full command I used in blue. Note I don't bother with the "dev" command in ip link, it seems redundant: iface vmbr1 inet manual bridge_ports enp1s0 bridge_stp off bridge_fd 0 pre-up ip...
  14. T

    Enable MTU 9000 Jumbo Frames

    @Percy: Can you confirm the full command is actually pre-up ip link set dev eth0 mtu 9000 Thanks!