| Summary: | sys-cluster/vzctl USE=vz should configure with --with-vz-kernel | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Mitch Harder <mmharder> |
| Component: | [OLD] Server | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
I'm going to close out my bug as OBSOLETE. As far as I know, vzctl will work with an upstream kernel even if it's configured with --with-vz. Three years ago, it looked like upstream was going to differentiate their support for upstream kernels, but the concept never seemed to gather any traction. |
The sys-cluster/vzctl ebuild (for versions 4.4, 4.5.1, 4.6.1) should consider the 'vz-kernel' USE flag in the src_configure() section. OpenVZ is in the process of providing limited support for non-openvz kernels. Since the most recent openvz kernel is 2.6.32, it is becoming more interesting to sometimes use openvz with a more recent upstream kernel. This configuration flag notifies vzctl not to look for certain kernel hooks. For the most part, vzctl still works OK on upstream kernels even if it isn't built this way, but it may help in some corner cases to be explicit about using an upstream kernel. The configure script help section describes this configuration option as follows: --with-vz Enable support for OpenVZ kernel I have modified my local ebuild as follows: --- /usr/portage/sys-cluster/vzctl/vzctl-4.6.1.ebuild 2013-12-03 10:06:11.000000000 -0600 +++ /usr/local/portage/sys-cluster/vzctl/vzctl-4.6.1-r1.ebuild 2013-12-31 07:10:15.867038248 -0600 @@ -51,7 +51,7 @@ src_configure() { --enable-udev \ --enable-bashcomp \ --enable-logrotate \ - --with-vz \ + $(use_with vz-kernel vz) \ $(use_with ploop) \ --with-cgroup }