Search results

  1. C

    root partition "full"

    AH! I think this did in fact help me figure out the problem. It seems to have made a backup to /backup at some point when the normal backup drive was not mounted so it wrote all the backup data to a folder /backup on the root partition.
  2. C

    root partition "full"

    I'm having an odd problem where the root partition is reported to be full but in reality is not. Filesystem Size Used Avail Use% Mounted on /dev/mapper/pve-root 95G 95G 0 100% / tmpfs 3.9G 0 3.9G 0% /lib/init/rw udev 3.9G 312K 3.9G...
  3. C

    Record option no longer available

    In Proxmox VE 1.9 there was a button on the KVM console to do screen recordings which I found very useful. Is this functionality still in pve 2.x and if so how do I get to it?
  4. C

    OpenVZ console does not connect

    Possibly related: There seem to be processes hanging around after I close the Java console. Example for OpenVZ container 126. /usr/bin/dtach -A /var/run/dtach/vzctlconsole126 -r winch -z /usr/sbin/vzctl console 126
  5. C

    OpenVZ console does not connect

    Indeed this does seem to work for some of the newer images. However the older ones are still failing. (Regardless of making tweaks suggested by the wiki page you linked before)
  6. C

    OpenVZ console does not connect

    I now have the same behavior on a Debian 7.0 standard template which did work earlier. Added screen shot for clarity of situation.
  7. C

    OpenVZ console does not connect

    I did look at that, but as I mentioned: The agetty solution being the one that is proposed on the wiki page.
  8. C

    OpenVZ console does not connect

    I've looked at the devpts and agetty solutions, but neither seems to help any. In this case I'm using the CentOS5 default template. I do get the Java console, but all it shows is a single ` in the top left. (Consoles to KVM/qemu machines do seem to work normally.) Extra info: Fresh install...
  9. C

    Cannot assign more than 7979 MB of memory.

    Yes, not in the container, but I mean I have a swap partition on the physical host machine. And I can assign part of the swap to my openvz container in the VE webinterface. I can also on the commandline assign swap using vzctl that will show up as swap inside the container for use as cache...
  10. C

    Cannot assign more than 7979 MB of memory.

    It has 8 GB of ram in it. (Which probably boils down to it being shown as 7979.) However since I also have a swap partition I'd expect I can assign a portion of the hardware nodes RAM, and then entirely separate of restrictions on ram that I can also assign an indpendent and arbitrarily large...
  11. C

    Cannot assign more than 7979 MB of memory.

    I'm having a problem with an openvz container. There seems to be no combination of memory and swap I can assign in the interface that results in more than 7979 MB showing up in the VM. In this specific case I'm trying it in an ubuntu 10.04 amd64 template.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!