Search results

I found what the problem was. I should have filled in the read limit in the restore window. However it suggests (greyed out) that not filling in a value means that the default will be used. I tried 0 as suggested the value to be unlimited, did not work either. I used value 1 and than the restore...

When restoring a LXC container I got the this error: Parameter verification failed. (400) bwlimit: type check ('number') failed - got '' The same on my second Proxmox (not clustered). What can be wrong? first server version: proxmox-ve: 6.1-2 (running kernel: 5.3.13-1-pve) pve-manager: 6.1-4...

Thanks, Nice progress!!

No problem here with zimbra on openvz. Not tried yet on LXC. I installed it on ubuntu. Peter

Since a few days after the last updates I do backups every night wthout any problem: lxc, on NFS, LZO, snapshot. Peter

I hear just the sound of silence.....

This is a serious problem for me. And I would like to know whether it has the attention of the Proxmox Team. So, dear Dietmar, give us one of your famous one word answers on my question: is the Proxmox Team working on this problem? Peter

Yesterday 15/1/2016 I updated the node and rebooted it. Backup to NFS was perfect. Today the scheduled backup failed: the vm's were O K. The first CT hung on suspend vm. Still the same pattern: one backup is perfect, and then the next backups have this issue. After reboot one goog backup. Etc...

Well Dietmar, look here: https://forum.proxmox.com/threads/lxc-backup-randomly-hangs-at-suspend.25345/ This seems to be a real bug. Reported 28-12-2015 on this very list. No reaction of the Proxmox team. Very unusual I must agree. But still. For the rest I'm quite happy to use the Turnkey LXC...

In my case on a NFS share and all the vm and ct are running

Still the same problem here. Did a complete reinstall of proxmox 4.1, with all the latest updates. Vm and lxc vt's backup fine two times. Then the vm's are still well backupped but the lyxcct's start to fail at suspend vm. At first the second one then the first one. After a restart of the...

Nobody having the solution? Peter

Same problem here. KVM's are backuped without any problem. LXC containers are backup once on a clean nfs share, next backups fail, at first on the last lxc container and then on the backup of the first. vzdump.conf changed: # vzdump default settings tmpdir: /tmp #dumpdir: DIR #storage...

Bravo! Congratulations!

Hi, Searching on google I found that the problem could be the mbr. The bios not immediatly recognizing the boot data in the MBR written on the disk for zfs. Since I plan to invest in two new Proxmox servers without having to pay for expensive raid cards. it is very important for me to know...

Hello Tom, THe hardware is: mboard: Asus M2N-VM-DVI, with processor: AMD Athlon 64 X2 Dual Core 5200+, memory 8GB, two hdds sata: 1TB and 1,5 TB in zfs raid0. This is my third try: this time booting takes 30 minutes. after post the screen turns completely black for a long time, then the grub...

For a test with zfs as root file system I installed proxmox 3.4 on two different servers, with two hdd's in zfs raid-0. Once booted both machines are very fast for their age. But booting takes 45 minutes to more than an hour. As I have two Proxmox 3.3 servers now, that I will replace with new...

Congratulations Peter Using Proxmox since 4 may 2008 and quite happy to!

Congratulations for this great piece of software. Thank you guys. Danke vielmals. Peter Using Proxmox since 4/5/2008

Last Linux Magazine (issue#150) has an article on Proxmox. Virtualization with the Proxmox Virtual Environment 2.2Virtualization Control RoomAuthor(s): Thomas Drilling The Proxmox Virtual Environment has developed from an insider’s tip to a free VMware ESXi/ vSphere clone. We show you how to...