qm list
VMID NAME STATUS MEM(MB) BOOTDISK(GB) PID
516 kvm516.islaserver.com stopped 1536 0.00 0
Stopped ?
It's working (example http://www.anrao.es)
Uff.
In this host there other two VPS KVM running.
514 & 969
Why don't show...
uhmm..
Easy.
1.- Ask for keys of mahcine.
2.- Sysadmin give you key
3.- Goi to system
4.- Run backup command for XX VID whit problems..
Other way... i don't kown
On log any... because I don't like see how growing backup size
may 11 06:02:56 INFO: Starting Backup of VM 516 (qemu)
may 11 06:02:56 INFO: running
may 11 06:02:56 INFO: status = running
may 11 06:02:56 INFO: backup mode: snapshot
may 11 06:02:56 INFO: bandwidth limit: 10240 KB/s
may 11...
AFter several test.
1.- If put cfq scheluder, KVM VPS don't work. Very heavy load on server
2.- If put deadline scheluder, backup grow, grow, grow
Example:
VPS 999
43810819 7,2G -rw-r--r-- 1 root root 7,1G may 10 20:22 vm-999-disk-1.qcow2
43810820 5,1G -rw-r--r-- 1 root root 5,1G may 9 22:26...
Well.
For change scheluder, i dont' use modifiy grub. Don't need. Only change on system.
Of course, we try with normal scheluder and try with
echo deadline > /sys/block/sda/queue/scheduler
http://wiki.openvz.org/I/O_priorities_for_containers
Desesperate. Just like move from OpenVZ to KVM...
With OpenVZ work perfectly.
pveperf
CPU BOGOMIPS: 22537.14
REGEX/SECOND: 970755
HD SIZE: 9.92 GB (/dev/sda1)
BUFFERED READS: 74.77 MB/sec
AVERAGE SEEK TIME: 7.43 ms
FSYNCS/SECOND: 982.78
DNS EXT: 32.39 ms
DNS INT: 1.37 ms (ovh.net)
Scenario
QEMU/KVM VPS on host machine for only QEMU VPS (3 VPS)
8GB RAM / 2 Disk SATA / 1 XEON
backup mode: snapshot
Disk (try with raw & qcow2) on BUS IDE or SCSI
vzdump --compress --dumpdir=/backup --mailto fenzen@gmail.com 516
INFO: starting new backup job: vzdump --compress...
Error show:
INFO: setting parameters failed - VM is locked (backup)
ERROR: Backup of VM 516 failed - command 'qm set 516 --lock backup' failed with exit code 255
On same machine there are 4 machines KVM. Only this VID has problem.
/usr/local/bin/backup.sh
INFO: starting new backup job: vzdump...
There is a new template naming convention, so maybe you need to rename your templates to something like:
<OS>-<OSVERSION>-<NAME>_<VERSION>_<ARCH>.tar.gz
Ok... Thanks.
Get help on other post...
Now work perfectly..
Ok.
On last months, with prxomox version 1.3, 1.4 & 1.5 we work PERFECTLY with OpenVz official templates for Centos 64 with 4 proxomox machines and 25 VPS wiht Centos 5.X x64.
Now, DON'T work templates.
"only templates issued by us are known" on your wiki, you say "get virtualappliances on...
Now. Any server work with templates on Web interface. Not on Opera, Not Firefox.
Others server are Proxomox 1.4 and we are working since 1.3 and 1.4 too.
I'm lost
Proxmox: 1.5 Debian 5 x64
Templates download from OpenVZ (Centos x64)
If migrate (vzdump) any VPS with Centos64 form another Proxomox, work fine (this machien it's failover & backup machine)
See images attached
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.