Looks like you've hit this bug:
https://bugzilla.proxmox.com/show_bug.cgi?id=647
which is still marked as unresolved.
So your remaining options could be:
- follow Henry's tip and use the "debian way"
- try to get an older version and upgrade after installation
- resize the VG after...
Thanks for the feedback Eduardo, glad to hear it-s working now.
It-s a pity that so many people don-t give a feedback when something worked for them, would help others visiting this forum.
Dirk
Did you use the other possible options like maxroot, swapsize, maxvz and did they work as expected?
Maybe the minfree option would do the trick for you, did you try it?
Dirk
Had the same issue with one of my 2008R2 machines a few days ago (ballon, disk and network driver virtio .102).
Solution for me was:
- bring down the VM
- replace the virtio nic with intel e1000
All cpu peaks went away after that.
Quite strange because i have other servers using virtio network...
Paul,
even if you could edit the properties for ex. the local storage of node 4 to allow backups you-d have to export /var/lib/vz and than create kind of a little mess in having backups and vms mixed in one storage. It is possible but i would defiently not recommend it.
Proxmox grabs all disk...
You probably build all VMs on local storage on node 1?
Use shared storage for the VMs to migrate them around, no rsync needed.
The backup storage has to be a) available on the node from which you want to backup a VM and b) marked as backup storage (which local storage is not). So either use...
Proxmox 2, fully updated to latest version, kernel 2.6.32.-13-pve
Using KVM with raw-disks only for all VMs
Suse Enterprise server 11SP1 (3 disks) has problems with its system disk (IDE, no cache).
After a few hours the root-filesystem is suddenly switched to read-only and in the messages...
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.