Search results

  1. S

    bad network connexion from download.proxmox.com

    Hello! Since some days, it is close to be impossible to download from download.proxmox.com from my location. The line seems very bad. I only have some Ko or less with apt-get. See the folowing traceroute. traceroute to download.proxmox.com (188.165.145.222), 30 hops max, 40 byte packets 1...
  2. S

    Proxmox VE 1.8 released!

    Hi! Just to be sure. Is the Kernel 2.6.32 shipped with release 1.8 include the patch to have NFS working with openvz?
  3. S

    openvz server and NFS -> problem with "stop"

    Tested ok on one of my server. NFS volume mount fine and stop/restart of the openvz VM work fine too. Do you plan to add this new kernel version to the 1.7 release?
  4. S

    openvz server and NFS -> problem with "stop"

    Good new! Seems that the bug is corrected in Kernel RHEL6 042test006.1. This version have also the interesting "cpu limit" function back.
  5. S

    openvz server and NFS -> problem with "stop"

    Just to complete, unless the nfs volume is umounted manualy, the VM doesn't stop. As well with this bug, "migrate" doesn't work too. All this work fine with 2.6.18-4-pve INFO: task vzctl:7221 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this...
  6. S

    openvz server and NFS -> problem with "stop"

    Hello, Any news from this bug? I installed a new server yesterday and used it to check if the problem is still here. -> YES. Tested with uptodate Proxmox VE 1.7 with kernel 2.6.32-4-pve. VM is Debian amd64 Lenny uptodate. If you manualy unmount the nfs volume before doing stop, all is fine...
  7. S

    Unable to stop container: operation timed out

    I had the same problem with NFS. I swiched back to 2.6.18 and the problem is gone.
  8. S

    NFS error (exit code 32)

    More on NFS and Promox 1.6 (with Kernel 2.6.18). NFS mount doesn't work with the Debian x64 OpenVZ template. Works fine with i386 template. We got "no such device".
  9. S

    NFS error (exit code 32)

    The problem is that 2.6.18 is not very nice to use with last hardware as HP G6/G7 ou Dell Rxxx. Lack of support for these new hardwares. I will be interested too to have a system to select the right kernel at proxmox install.
  10. S

    NFS error (exit code 32)

    NFS should be supported with 2.6.32 but is curently buggy. Have you tried with Kernel 2.6.24?
  11. S

    NFS error (exit code 32)

    Use Kernel 2.6.18 in place of 2.6.32 and NFS will work fine with Proxmox 1.6.
  12. S

    openvz server and NFS -> problem with "stop"

    Hello! Sorry I was busy. Using 2.6.18, the NFS mount/umount work fine. We can stop the VM with NFS volume mounted without problem. Automount def in fstab is well mounted at start. But still a problem: we need to type "modprobe nfs" the first time on the proxmox server. I also found that when...
  13. S

    openvz server and NFS -> problem with "stop"

    I've done again all NFS test using a promox node not part of cluster. I used openvz template "debian-5.0-standard_5.0-2_i386" for the test. Same problem with NFS. I got an "Unable to stop container: operation timed out" if a NFS volume is mounted. And I need to type "modprobe nfs" before.
  14. S

    openvz server and NFS -> problem with "stop"

    Nothing special in INIT log but I made more test. See below. I have 2 proxmox VE servers : one master, one slave. The VE with NFS is on the slave server. The Proxmox servers are the last 1.6. pve-manager: 1.6-5 (pve-manager/1.6/5261) running kernel: 2.6.32-4-pve proxmox-ve-2.6.32: 1.6-25...
  15. S

    openvz server and NFS -> problem with "stop"

    Hi! I have an Proxmox VE 1.6 server with one openvz host. A remote volume is mounted on the VE using NFS client. When I "stop" the VE, nothing append. ps show the process but nothing append and I can't kill it. root 10081 1 0 13:56 ? 00:00:00 /usr/sbin/vzctl stop 108 I have...
  16. S

    1.6 upgrade failed -> PTE Read access is not set

    Sorry, I can't test right now. I have no HP server left to test. The DL360G6 is back in production (without hpacucli).
  17. S

    New Proxmox VE kernel branch 2.6.35 - with KSM support

    Good new but HP say 2.6.24 only. I tested with hpacucli_8.50-6.0.3-3 and Promox 1.6. The kernel freeze at boot . Have a look on this topic: http://forum.proxmox.com/threads/4725-1.6-upgrade-failed-gt-PTE-Read-access-is-not-set
  18. S

    New Proxmox VE kernel branch 2.6.35 - with KSM support

    hpacucli is not compatible with 2.6.32 or later kernel. Last supported kernel is 2.6.24.
  19. S

    1.6 upgrade failed -> PTE Read access is not set

    I seem to have found the culprit. If hpacucli_8.50-6.0.3-3_amd64.deb is installed, the kernel 2.6.32 crash and freeze the server. Do the same with oldest version of hpacucli. The system crash about 5 minutes after the server is loaded. It's repetitive. Will try later with pve-2.6.24.
  20. S

    1.6 upgrade failed -> PTE Read access is not set

    System is still completly unstable with 1.6 and DL360G6. I got "DMAR:[fault reason 06] PTE Read access is not set" after the last CT loaded. The system froze. Before it froze, GUI managment can't be accessed. pve-manager: 1.6-2 (pve-manager/1.6/5087) running kernel: 2.6.32-4-pve...