Recent content by dcrobinson

  1. D

    Can I install plex , transmission , rtorrent and other application ?

    I run Plex inside a container. It works very well. It is best to use a 64 bit container, because transcoding is more efficient on 64 bit.
  2. D

    LXC CPU Usage

    I've just realised that they're showing zero network traffic as well.
  3. D

    LXC CPU Usage

    The web UI shows "0.0% of 2CPUs" (for example) for all of my LXC VMs, except for one of them that just shows a single "-". All the VMs are working fine. Is this a known bug?
  4. D

    LVM, ZFS, snapshots etc

    I tried that but couldn't get LXC to work (and I had to change the caching on KVM machines, IIRC). I've given up trying to get it to work, and so I'm temporarily using the "unsupported" mdadm RAID10 with LVM/ext4. I'll move to ZFS at another time. I can live without live snapshots of LXC...
  5. D

    LVM, ZFS, snapshots etc

    Thanks Tom, that's very clear. I'll eagerly wait 4.1!!
  6. D

    LVM, ZFS, snapshots etc

    I've read lots of threads and have been struggling since upgrading to PVE4.0 3 days ago. I am now very confused! I read in one that you are currently adding snapshot backups to LVM storage. 1. Does this mean that if I have a directory storage with ext4+LVM I will be able to do snapshot...
  7. D

    ClamAV Engine & Db

    No. I have a VE installation, and I use ClamAV to scan the containerised VMs.
  8. D

    ClamAV Engine & Db

    For the last week or so I've been getting these warnings. Either my machine is broken, or it needs updating in the repositories I guess. Anyone else with the same problem? LibClamAV Warning: ************************************************** LibClamAV Warning: *** The virus database is older...
  9. D

    OpenVZ network problem

    Thanks for that advice. I have now sorted out the boot inconsistency, and have opted for 2.6.32. I now feel a complete fool - I finally worked out the problem. My gateway router had an old IP address binding to an ancient physical machine (long since dead). So it was rejecting any packets...
  10. D

    OpenVZ network problem

    OK, thanks, I'll try that. Any reason why I shouldn't stick with 2.6.32, (and install the proxmox-ve-2.6.32 package) or is 2.6.18 better for OpenVZ? I have a mix of OpenVZ and KVM virtual machines, although to be honest I am most concerned about the performance/stability of the KVM ones.
  11. D

    OpenVZ network problem

    pveversion -v output: pve-manager: 1.8-17 (pve-manager/1.8/5948) running kernel: 2.6.32-4-pve proxmox-ve-2.6.18: 1.8-14 pve-kernel-2.6.32-4-pve: 2.6.32-32 pve-kernel-2.6.18-5-pve: 2.6.18-14 pve-kernel-2.6.18-4-pve: 2.6.18-10 qemu-server: 1.1-30 pve-firmware: 1.0-11...