OpenVZ Forum


Home » General » Support » Hosting provider uses OpenVZ - what are the minimum container support requirements? (Trying to figure out what I need to leave intact when customising container to my needs)
Re: Hosting provider uses OpenVZ - what are the minimum container support requirements? [message #51616 is a reply to message #51566] Tue, 26 August 2014 03:11 Go to previous messageGo to previous message
adfhogan is currently offline  adfhogan
Messages: 3
Registered: July 2014
Location: Melbourne, Australia
Junior Member
Ok.. well guess I'll start answering my own questions Smile

So far I've found out that OpenVZ expects upstart and not sysvinit and if one allows sysvinit to take over when performing a dist-upgrade, it'll spin the CPU up to 100%
  • tamcore.eu/openvz-debian-7-und-sysvinit/ (German)
I also found out whilst reading the OpenVZ container instructions
  • openvz.org/Debian_template_creation
that OpenVZ expects:
  • /dev/ptmx (special character file, major 5, minor 2)
  • symlink /etc/mtab to /proc/mounts
This would mean that when upgrading within the guest (when one is a hosting customer, and not manager of the host environment) that anything that would change within the container the system init daemon, remove/reset the mtab symlink or would cause the ptmx special character device node to vanish will cause problems.

What remains to be determined is if Debian 'testing' can be made to play nice with Linux kernel 2.6.32-042stab092.3 (as opposed to its usual linux 3.x) and udev can be made to keep /dev/ptmx intact.

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: Ploop image incremental backups
Next Topic: CentOS 6 - /dev/shm Not Mounting at Boot
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Fri Oct 10 12:44:24 GMT 2025

Total time taken to generate the page: 0.13191 seconds
Powered by FUDforum Powered by Virtuozzo Containers