Search results

  1. G

    vnc access

    Try ssh -X.
  2. G

    Poor performance with qmrestore

    Just for fun :) dd if=/dev/zero of=/dev/null on my netbook default -> 215 MB/s bs=2K -> 824 MB/s bs=4K -> 2.0 GB/s bs=8K -> 2.0 GB/s bs=16K -> 2.5 GB/s bs=32K -> 2.4 GB/s bs=64K -> 2.6 GB/s bs=128K -> 2.7 GB/s bs=256K -> 2.7 GB/s bs=512K -> 2.3 GB/s bs=1M -> 1.4 GB/s bs=4M -> 1.1 GB/s bs=6M ->...
  3. G

    Poor performance with qmrestore

    As I investigated on the differnent systems with and without raid the best performance would be always between 32K and 1M. In my current configuration maximum is on bs=256K.
  4. G

    Poor performance with qmrestore

    I have done some tests. Sources: - Production Cluster (3 VMs running on the current Server and 5 on another) - RAID 0 -> DRBD -> LVM - KVM VM 1 drive 16Gb Here are results: bs is Default (512 bytes) -> 10.6 MB/s bs=128K -> 19.6 MB/s bs=256K -> 20.6 MB/s bs=512K -> 20.2 MB/s bs=1M -> 19.7 MB/s...
  5. G

    Poor performance with qmrestore

    I don't think it's a good idea to go direct because it can make host server a bit slow for a restore time.
  6. G

    Bug tracker

    That's nice! Thank you for information.
  7. G

    Bug tracker

    Would public read-only VCS be okay? What do you think?
  8. G

    Poor performance with qmrestore

    I didn't know that qmrestore use dd but I totally agree with that. I'm always use dd with bs=1M for the best performance while copy drives or partitions.
  9. G

    Minor feature: virtual machines should wait DRBD

    If I do it manually is can became broken after update.
  10. G

    Minor feature: virtual machines should wait DRBD

    Proxmox 1.6 Two hosts LVM on DRBD Guest's drives on that LVM It would be nice if virtual machines wait drbd on host server boot. If they don't you should start them manually after drbd is accessible.
  11. G

    Resize Harddisk

    I'm not sure this is really so. As well reducing physical volume will be really harder then logical volumes inside the volume group especially if you don't have additional storage for keeping data temporarily. Moreover, if the system doesn't have enough memory and it tries to use swap - this is...
  12. G

    Resize Harddisk

    vgdisplay pvdisplay -m PS: What the reason to increase swap? What the reason to use it outsite LVM?
  13. G

    Resize Harddisk

    It's possible but not easy. Don't you really have a swap? swapon -s lvdisplay
  14. G

    Resize Harddisk

    It depends of type of storage you are using.
  15. G

    vzdump of KVM in snapshot issue

    I mean: 1. start job 2. hook->stop machine 3. start backup 4. hook->start machine (there is no hook here) 5. stop backup 6. job end
  16. G

    vzdump of KVM in snapshot issue

    :) I've tried to do it using "hooks + snapshot mode" but I didn't manage because there a no any hooks just after starting backup. Have a nice day, Stas
  17. G

    DRBD perfs with different kind of disk for each node

    As well you will probably use syncer rate that will be less then disk performance. http://www.drbd.org/users-guide/s-configure-syncer-rate.html
  18. G

    vzdump of KVM in snapshot issue

    I'm totally agree and ask for the same some time before: http://forum.proxmox.com/threads/2349-Backup-KVM-with-stop-shapshot Unfortunately developers don't think it would be used by many people. Shall we arrange voting?
  19. G

    Considerations regarding snapshot backup consistency

    I asked for the quite same with one difference: I think stop+snapshot will be better than suspend+snapshot http://forum.proxmox.com/threads/2349-Backup-KVM-with-stop-shapshot