1,433
edits
Changes
Importing a new version from external source
== 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 <code>--verbose</code> option.
* Kernel information
** kernel version, architecture and flavour (<code>uname -a</code>)
** 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
** <code>vzctl --version</code>
* OpenVZ/Virtuozzo environment information
** Virtuozzo version <code>cat /etc/virtuozzo-release</code>
** <code>/etc/vz/vz.conf</code> file
** <code>/etc/vz/<veid>.conf</code> file, where <code><veid></code> is an id of container in question.
* Various log files
** <code>/var/log/messages</code>
** <code>/var/log/vzctl.log</code>
** Virtuozzo allows to gather all useful logs into single report. Execute <code>prlsrvctl problem-report --send</code> and <code>prlctl problem-report [CTUID|VMUID] --send</code> 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.
* 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 <code>--verbose</code> option.
* Kernel information
** kernel version, architecture and flavour (<code>uname -a</code>)
** 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
** <code>vzctl --version</code>
* OpenVZ/Virtuozzo environment information
** Virtuozzo version <code>cat /etc/virtuozzo-release</code>
** <code>/etc/vz/vz.conf</code> file
** <code>/etc/vz/<veid>.conf</code> file, where <code><veid></code> is an id of container in question.
* Various log files
** <code>/var/log/messages</code>
** <code>/var/log/vzctl.log</code>
** Virtuozzo allows to gather all useful logs into single report. Execute <code>prlsrvctl problem-report --send</code> and <code>prlctl problem-report [CTUID|VMUID] --send</code> 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.
