Search results

  1. D

    Qemu guest agent in centos5 or debian6

    Can you try on Debian 7.1 ? Debian 6 kernel is very old.... (2.6.32 deb). Luca
  2. D

    Multipath and QEMU: /dev/sdc: read failed

    It's OK, I did not realize you used a storage intel. I use different IBM SAN and... require a different configuration. There is a setting on SAN BIOS ? BIOS on fibre channel cards is update ? Luca
  3. D

    Multipath and QEMU: /dev/sdc: read failed

    Could be a configuration error on multipath ? Various SAN devices uses different configuration... Can I see multipath config, "multipath -ll" output ? I had similar problems in the past because the bios of the SAN was configured incorrectly, especially if the SAN requires RDAC. There is an old...
  4. D

    [SOLVED] VM freeze or service stalling after live migration (3.1)

    In another post, on PVE 3.0 I've a similar problem on Windows guest, *but* ONLY on different hardware node. On three nodes, 1-2 are identical, node 3 is different, migrate to-from node 1-2 works fine, migration to-from node 3 freeze VM and 100% CPU. I have not had the possibility to upgrade...
  5. D

    You do not have a valid subscription for this server

    Proxmox is GPL compliant. If you buy a subscription you can use "enterprise repository" : MORE tested, suitable for production server. If you don't buy a subscription you can use "free repository": LESS tested. In a nutshell, that's all
  6. D

    Sheepdog: run sheepdog on a dedicated eth/bound ?

    .. is possible ? The sheepdog configuration is really poor. I can set several parameters in /etc/default/sheepdog ? I would like to perform sheepdog at least on a dedicated 4 gbps bound (or a dedicated 10 gbps eth) Luca
  7. D

    hyperV=virtual guest service - VmWare=Vmware tools - proxmox=???

    .. and very important .. enable shadow copy function on Win guest during backup by PVE ( important for MsSQL - Exchange). Without this function would be like removing the power supply to VM.
  8. D

    HP Microserver g2020t

    There are same HD in addition to SD card ? If yes, you can try to remove HD, install PX on SD, than plug HD.
  9. D

    PX 3.0: live migration (node to node) freeze VM on different hardware

    Yes, absolutely Node 1: kernel 2.6.32-22 (Jul 15 08:36), pve-qemu-kvm: 1.4-13 Node 2: kernel 2.6.32-22 (Jul 15 08:36), pve-qemu-kvm: 1.4-13 Node 3: kernel 2.6.32-22 (Jul 15 08:36), pve-qemu-kvm: 1.4-13
  10. D

    PX 3.0: live migration (node to node) freeze VM on different hardware

    On Node 1-2: Intel Xeon E5-2603 (2 socket) On Node 3: Intel Xeon E5345 (2 socket I can try qemu64 ... and/or update to PX 3.1 (include several bugfix)
  11. D

    PX 3.0: live migration (node to node) freeze VM on different hardware

    KVM64 (default) I've tried on several VM... freeze on 100% CPU after migration vs Node 3 (node1 <> node2 all ok)
  12. D

    PX 3.0: live migration (node to node) freeze VM on different hardware

    Hello ! I've a problem on PX 3.0 (I know, it is not the latest version) on migration (node to node) on nodes with different hardware (processors). The cluster has three nodes, node 1 and node 2 are identical and migration works fine. When I try to migrate to node 3, migration works but the VM...
  13. D

    Proxmox 2.x / 3.x cluster question

    Hi ! HA is not mandatory, If you don't have shared volume you can manage server 1 and 2 like a cluster with not shared datastore (simply server 1 has datastore 1 and server 2 has datastore 2). The problem ... there is'nt a shared area... if you have an NFS volume shared.. you can try storage...
  14. D

    Proxmox VE Differential Backups for Proxmox 3.1

    No, the speed of diff restore is lower than a simple full restore. The goal is the space reduction on storage backup, and is not little
  15. D

    Proxmox VE Differential Backups for Proxmox 3.1

    Oh yes ! Differential backup in Proxmox would be a great feature ! I use this patch and works wery well. BUT ... xdelta3 is very CPU intensive program, at the end, full backup and differential backup use the same time. The real difference is the space used on backup storage (obviously). I think...
  16. D

    2.6.32-22-pve > Kernel panic - not syncing: Fatal exception

    Can you try to upgrade system BIOS && controller (P400) BIOS ? I run Proxmox on HP Proliant DL series and it's rock solid... Luca
  17. D

    New Kernel for Proxmox VE 3.0

    Thanks Tom ! Just installed :)
  18. D

    3 kernel panic in a day

    Mhhhh running kernel: 2.6.32-16-pve -> very old version Possible hardware problem ? First try to update to the last...
  19. D

    postgres is extrem slow

    I think the problem is in the terminology used by HP. Controller P400 does not come natively with the battery, it is an optional. If the battery is not present the cache (on controller) is disabled by default in writing, if it is present can be activated. Obviously enable write caching is...
  20. D

    postgres is extrem slow

    BUFFERED READS: 199.18 MB/sec -> OK for P400 RAID5 (best performance on RAID 10) AVERAGE SEEK TIME: 5.77 ms -> OK for 10k rpm SAS disks *BUT* you *MUST* upgrade P400 firmware... it is possible that the RAID be corrupted in rare conditions. Several years ago, on P200 controller (HP) adding...