Search results

I noticed that after the restore the container files are properly present in /var/lib/vz/private/NNN/ However the following are missing: - there is no config file for the container at /etc/pve/openvz/ - there is no filesystem under /var/lib/vz/root/NNN Looking at the config files I think I...

We have started the upgrade of our cluster to Proxmox VE 4.1, but there are so many problems (and no solution in sight for them) that we are thinking about returning to PVE 3.4. Problem is we have a few containers that are already converted to LXC, is there any way of converting them back to...

These RAW disk files are sparsely allocated, so they only use the disk space that's actually written to them. root@proxmox4:/var/lib/vz/images/227# ls -lah total 34G drwxr----- 2 root root 4.0K Dec 19 01:16 . drwxr-xr-x 19 root root 4.0K Dec 19 04:06 .. -rw-r----- 1 root root 80G Dec 19 16:10...

Tom, Dietmar! At least two of us have tested thin-lvm, we can confirm it does not work for LXC at all. Any idea when can we expect a fix to test?

Is it really available? Have you guys tested this? Is this only available in pvetest? I have followed Dietmar's steps to create a thin lvm, and I can't restore containers to it. It is also fully unsupported by the webinterface.

Yeah it doesn't work. I have repeated your steps exactly, the storage shows up in the list (type: Unknown, content: Disk Image, Container), yet when I try to restore a container to it, it says: It looks like I can restore KVM guests to it, but the problem is I need snapshot backup for LXC...

I haven't tried it yet, but I don't think you should format your thin-pool to ext4, you only need to give the thin pool to Proxmox via storage.cfg, and then it will store the raw images on it. (Just like with regular lvm storage: you only gave a vg to Proxmox, not an lv or a filesystem.)

Good news for phone and tablet users, however the density of information went down horribly on desktops, on which I believe many of your users work all day long. Any possibility of giving a more compact theme as an option? Also the Proxmox logo in the header is kinda huge, maybe you could get by...

Looks like the actual disk size inside an LXC container is smaller than reported, because our containers are routinely getting full before hitting the specified disk size. For example in this container there is a 2GB difference between available disk space and disk size. root@lxc:/# du -chs *...

Sorry I don't know what you mean, how are they back? If you mean lvm thin pools, then we will have to test that first, not to mention backup-restore our entire container storage...

Yes it is, because as I already wrote we simply can't use ZFS on our hardware, so that leaves me with no other options - apart from the barely integrated and untested technology preview. Exactly. Using a RAID card instead of ZFS can be a valid choice for many people, for many reasons. But if...

Dietmar, I have to say this decision to silently remove a tried and tested container backup solution from Proxmox without providing a clear upgrade path to another, working method was absolutely unprofessional. A lot of people (and their users and clients) depend on Proxmox, and LVM snapshot...

Ok so how do I use it in practice? Do these steps look correct? 1. lvreduce pve/data so there is free space for the thin pool in the pve VG 2. lvcreate -n pvepool -L size pve 3. lvconvert --type thin-pool pve/pvepool 4. add storage.cfg entry for thin pool lvmthin: thin1 vgname pve...

There are a couple of problems with this: 1. Why do I need a thin pool for snapshot backups? Snapshots are an LVM feature, and they were available for vzdump backups long before thin pools... why are they not used for backups? 2. How do I create a storage in the Proxmox interface from a thin...

I still can't do a snapshot backup of an LXC container stored in the local "Directory" type storage, even though it is ext4 on LVM (which supports snapshots). This is a huge regression compared to OpenVZ. If I create an LVM type storage on the same "pve" VG, will I be able to move my containers...

In that case, could you enable the bind-mounts of the replacement /proc files to show actual cpu number (cpu limit) and swap size available to a container?

Dietmar I'm not sure about LXD, but Ubuntu provides the desired functionality through lxcfs: https://insights.ubuntu.com/2015/03/02/introducing-lxcfs/ https://linuxcontainers.org/lxcfs/ Here is the github page: http://github.com/lxc/lxcfs

The problem with testing a different distribution is twofold: - it introduces too many variables (different version of ZoL, different kernel & drivers, etc.) - it defeats the purpose of debugging an issue of Proxmox (also I have to use Proxmox, not something else) However, I have tried your...

Blaming would be a strong word, but since I first encountered these errors, I have replaced every single piece of hardware in the machine (apart from the harddrives), and the errors remained. The only connection between hardware and the errors were the number of DIMMs installed. Please see...

Doesn't seem to be the case on Proxmox 4. root@proxmox:~# numactl --show policy: default preferred node: current physcpubind: 0 1 2 3 4 5 6 7 cpubind: 0 nodebind: 0 membind: 0 root@proxmox:~# numactl --hardware available: 1 nodes (0) node 0 cpus: 0 1 2 3 4 5 6 7 node 0 size: 31666 MB node 0...