Search results

Thanks for your reply it was just a writting mistake a I executed "-O raw"

wolfgang you're the ONE ! as you said, I used the zfs plugin and did the following: 1- created a new file system using the command zfs create rpool/zfsdisks 2- added a new storage: storage (Datacenter -> [Storage] -> Add, choose "ZFS", called "zfsvols", as "ZFS Pool" choose "rpool/zfsdisks"...

Hi thanks a lot for your reply I did the following 1- converted my original vmdk file to the row format with the follwing command qemu-img convert -f vmdk vm-100-disk-1.vmdk -O qcow2 vm-100-disk-1.raw 2- did the backup of my vm on [proxmox3-node1] 3- restored the backup on...

I migrated to 4.2 but when trying to get my old VMs working in the new environement no way !! here's an example I 've : vm1-disk.vmdk (is a vmdk disk in an old proxmox 3 server) that I want to get it work in proxmox 4.2 in a VM with id 100. I tried : 1- to copy vm1-disk.vmdk to...

Hi thanks a lot for your answer Udo.. 1- I already changed the "IDE mode" to the "AHCI mode" in the bios settings , that changed nothing 2- "seek time of 24.6 is very bad!" I don't now why ?! - "Is the disk busy from other things?" => there isn't any vm running, just fresh proxmox 4.1...

As I can't figure out how to fix this I 'm going back to proxmox 2.0

Thanks a lot for your quick answer, I did the following: 1- remounted my second drive with "barrier=0" mount /dev/sdb1 /mnt/sdb1 -o barrier=0 2- did the pverperf again pveperf /mnt/sdb1 CPU BOGOMIPS: 24741.56 REGEX/SECOND: 2709607 HD SIZE: 458.32 GB (/dev/sdb1) BUFFERED READS: 178.32...

HI thanks a lot for this excellent project... Here's my PB 1- my vms are too slow.. can't even open a window while using a rdp access to them 2- a backup of vm of 2GB hard disk size took 8hours ! after a lot Googling I comes with the following conclusions This is due to the very slow FSYNCS...