Recent content by sol-invictus

  1. S

    IOTOP on LXC

    You can use a specialized version from iotop for cgroups where you can define the lxc container you want to monitor: ./iotop.py -g /lxc/1234/ns For more information see https://forum.proxmox.com/threads/proxmox5-debian9-and-iotop-in-container-error.40838/
  2. S

    Proxmox5 Debian9 and iotop in container error

    I found out that ./iotop.py -g /lxc/[CONTAINER-ID] is not enough to list just the container. You have to exactly put the string like shown in CGROUP when running just ./iotop.py (sort by CGROUP reversed). In my case it was: ./iotop.py -g /lxc/1234/ns
  3. S

    Proxmox5 Debian9 and iotop in container error

    I have the same problem, iotop does not run in an LXC container (Container: Debain 9.9, Proxmox 6) iotop version 0.6-2 root@lxc-container:~# iotop Traceback (most recent call last): File "/usr/sbin/iotop", line 17, in <module> main() File "/usr/lib/python3/dist-packages/iotop/ui.py"...
  4. S

    Migration of servers to Proxmox VE

    Hello! Is there a possibility to migrate an existing vserver to proxmox? or do i have to migrate the vserver-host to an openvz server like described here: http://wiki.openvz.org/Migration_from_Linux-VServer_to_OpenVZ - and afterwards migrate the containers to proxmox described in your link?
  5. S

    problems with mouse under different guestOS

    hi! I'm using the KVM from proxmox 1.3 with different guest-OS like WinVista, Win7, AROS, ReactOS, ... But with AROS and ReactOS i have a problem with the mouse, which is not moving at all under AROS and under ReactOS it's jumping around (most times disapearing bottom right). I used the...