Special:Badtitle/NS1198:Reporting OpenVZ problem/3/en

You should always report

• clear problem description

It is necessary not just to describe the problem, but also post real commands, and real output on console. It is useful to run commands with --verbose option.

• Kernel information
  • kernel version, architecture and flavour (uname -a)
  • origin of your binary kernel (RPM from openvz.org, other repository, compiled from sources, ...)
  • .config file (if you compiled the kernel)
• Linux distribution used on HN
• console tools information
  • vzctl --version
• OpenVZ/Virtuozzo environment information
  • Virtuozzo version cat /etc/virtuozzo-release
  • /etc/vz/vz.conf file
  • /etc/vz/<veid>.conf file, where <veid> is an id of container in question.
• Various log files
  • /var/log/messages
  • /var/log/vzctl.log
  • Virtuozzo allows to gather all useful logs into single report. Execute prlsrvctl problem-report --send and prlctl problem-report [CTUID|VMUID] --send and specify problem report ID number in bug.
  • Other

If other programs are involved in your problem, try to run they with increased verbosity and attach appropriate log files, if they exist.