Search results

  1. I

    UNIX sockets dead after chkpnt/restoring an OpenVZ container

    Yes, I'm evaluating that option, the question is that I'ld like to be sure that the kernels are supported... which 2.6.18 source is used to build the pve kernel image? I mean, are all known security patches included or should I build my own versions if I want all the patches?
  2. I

    UNIX sockets dead after chkpnt/restoring an OpenVZ container

    I've installed the 2.6.18 linux kernel on two nodes and as far as I know that fixes the Unix socket problem: Unix sockets do work after a suspend/resume cycle and after a container live migration. ¿Are there any plans of reviewing/updating the OpenVZ kernel patches for the 2.6.2* or 2.6.3*...
  3. I

    UNIX sockets dead after chkpnt/restoring an OpenVZ container

    Hi Dietmar, Have you reported confirmed this bug in your setup, or reported the bug upstream? Just to know the bug number so I can keep an eye.
  4. I

    UNIX sockets dead after chkpnt/restoring an OpenVZ container

    Just for the record, I've just tested this on PVE kernels 2.6.24-8-pve and 2.6.24-9-pve. The behaviour didn't change.
  5. I

    UNIX sockets dead after chkpnt/restoring an OpenVZ container

    Hi dietmar, Sorry for not being too clear. In my experience, the flaw is 100% reproducible with a plain chkpnt/restore of a Debian lenny container. Just to be plain sure, I've downloaded the 64bit version of the Debian lenny template from Proxmox's templates...
  6. I

    UNIX sockets dead after chkpnt/restoring an OpenVZ container

    There seems to be an error on the way the UNIX sockets are handled after an OpenVZ checkpoint / restore. We have detected it with postfix, as the mail system fails after restoring a container with the following messages on the mail.log file: Dec 17 17:04:27 clustest postfix/pickup[7575]...
  7. I

    New pve-kernels; regeneration of initrds.

    Ok, I'll do my best to have a look at this. Is there a source repo for the PVE installer?
  8. I

    New pve-kernels; regeneration of initrds.

    Hello, Recent upgrades of the PVE kernels have failed on us because they suddenly don't regenerate the initramfs during the postinstall and instead they just carry the initrd inside the .deb package. Generating the initrd after the install is what Ubuntu and Debian kernels traditionally do...
  9. I

    Survey: Proxmox VE Kernel with or without OpenVZ?

    The biggest advantage of Proxmox VE for us is the really nice web frontend for both OpenVZ and KVM. We use OpenVZ a lot more than KVM, and are slowly migrating our big Linux-VServer setup to PVE, but some of the servers are also hosting Windows boxes which were migrated from old hardware...
  10. I

    pvemirror/pvetunnel can fill a hard drive quickly

    Hi, We're making heavy use of PVE in our research institute and this week we had a bad suprise with the pvetunnel and pvemirror daemons. Two nodes in our large cluster are having hardware problems, and were shutdown. pvemirror and pvetunnel starting writing several dozens of error messages...
  11. I

    Error in dependency handling

    The attached Makefile and dab.conf are enough for creating a template which shows the error. After creating a VM from the template, you can open a console and check that packages are missing: vztest:/# /etc/cron.daily/dlocate sh: /usr/lib/locate/frcode: No such file or directory vztest:/#...
  12. I

    Error in dependency handling

    Hi all! I found an error in DAB's handling of dependencies in dab install <package>. It doesn't recognise X | Y dependencies. For instance, one of the instructions in my Makefile is dab install dlocate. This package in Debian Lenny has the following dependencies: awk, dctrl-tools | grep-dctrl...