Difference between revisions of "Download/vzctl/3.0.22/changes"
(created) |
(fixed using git log) |
||
| Line 2: | Line 2: | ||
* A lot of bug fixes | * A lot of bug fixes | ||
* Ubuntu upstart compatibility | * Ubuntu upstart compatibility | ||
| − | {{Git log|vzctl|3.0.22}} | + | {{Git log|vzctl|vzctl-3.0.22||}} |
=== Compatibility === | === Compatibility === | ||
*A mechanism for choosing the interfaces to send ARP requests to has been improved (see description of <code>NEIGHBOUR_DEVS</code> in vz.conf(5) man page). In case VE IP addresses are not on the same subnet as HN IPs, it may lead to such VEs being unreachable from the outside world. The solution is to set up a device route(s) for the network your VEs are in. For more details, see {{bug|771}}. | *A mechanism for choosing the interfaces to send ARP requests to has been improved (see description of <code>NEIGHBOUR_DEVS</code> in vz.conf(5) man page). In case VE IP addresses are not on the same subnet as HN IPs, it may lead to such VEs being unreachable from the outside world. The solution is to set up a device route(s) for the network your VEs are in. For more details, see {{bug|771}}. | ||
Revision as of 17:30, 26 March 2008
Changes
- A lot of bug fixes
- Ubuntu upstart compatibility
For the complete list of changes in this release, see git changelog for vzctl-3.0.22.
Compatibility
- A mechanism for choosing the interfaces to send ARP requests to has been improved (see description of
NEIGHBOUR_DEVSin vz.conf(5) man page). In case VE IP addresses are not on the same subnet as HN IPs, it may lead to such VEs being unreachable from the outside world. The solution is to set up a device route(s) for the network your VEs are in. For more details, see OpenVZ Bug #771.
