Hello.
Due to number of issues with PVE 4 and LXC, I would like to downgrade to Proxmox 3.4.
Is it possible to convert an LXC container to an OpenVZ container ?
Thank you
I have the same problem after upgrading to Proxmox 4. I disabled barriers, switched to data=writeback and use chroot disk for containers which helps to improve the situation but IOwait is still a problem. I opened a thread here.
Proxmox staff does not react to the problem despite many threads...
I considered it but some VMs are quite large and will take some time to transfer it from a server to the other. Whereas if I have a local copy I can restore it quickly so I would like to avoid deleting the backup after the transfer.
Hello.
I have a partition for backups but it is not large enough for two copies of each VM. I set Max Backup = 1 in the storage options to prevent that.
Proxmox tries to create a new archive and then delete the old one for a scheduled backup. It fails when there is no enough storage available...
When I use noVNC on a container. E.g. if I open VIM within that container and hold the down key to scroll down, the console will hang and won't react until I close it and reopen it.
Hello
In Proxmox 3 and OpenVZ, I was able to:
- hot increase or decrease the disk size of a container. With PVE 4, I can only increase raw devices and chroot disks will see all the storage available (no quota possible)
- have good storage performances. With PVE 4 I have IOwait issues like many...
How do you conclude it was corrupted file system ? Because you are running out of ideas ?
My server is from a fresh Proxmox 4 install. Don't want to do that again (I have a lot of data to backup and restore) if there is no way to confirm this is actually the issue.
I am using ext3 by the way.
I regret I upgraded to Proxmox 4. If I had known I would have such performance issues, I would have stayed on version 3... Many users are reporting the same issue and I haven't seen any official reply from Proxmox staff... Don't know if they are just ignoring the problem or too busy to...
So I converted all my containers from RAW disks to chroot. IO wait are better, performances have improved but it is still not as good as when I was under OpenVZ. Just have a look at my example below.
I looked at the backup logs when I was running PVE 3.4 and compared them with the duration from...
Hello.
You can use HAProxy to achieve that, I wrote a tutorial on how to redirect a subdomain to another webserver (in this case, your proxmox GUI):
http://freedif.org/redirect-a-subdomain-to-a-vm-with-haproxy/
You need to adapt it to redirect a subdomain to your proxmox IP & port. On my...
Hello.
I experience the same problem: https://forum.proxmox.com/threads/performance-issue-unusual-high-io-delay.26012/
Is it possible to convert disks instead of restoring containers ?
Already tried... It seems jbd2 is the journalling process causing my issue.
Edit: found someone with the same problem: https://forum.proxmox.com/threads/high-wait-io-after-and-load-average-upgrade-to-proxmox-4.25128
Is it a known issue ? any workaround ?
Hello.
I was running Proxmox 3.x on my server for a year but I experience slow performances after upgrading to Proxmox 4 (I did a clean install from OVH Proxmox 4 template and restored the containers manually).
I am hosting basic apps for my own usage (owncloud, seafile, openvpn, emby, sonarr...
Hum I see... cause I wanted to suggest to add a similar option in the GUI to enable a tun device for an OpenVPN server in a container. But I can understand this can be more complicated in the background than just adding some lines in a config file and there are implications I am not aware of...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.