I've got openvz setup and operating nicely with three VEs (ubuntu7.10, centos4,
redhat9) - but shell job control does not work in any of them.

^Z should suspend the current command inside the VE when in a shell where you've
  ssh'd into the VE - but instead it remains inside the current process. I've
checked stty settings and they appear equivalent in both the VE and host.

Have I missed enabling something which is mentioned in the documentation or is
this a known issue?

I'm using 2.6.20-ovz008-openvz1 (built from source) following instructions for
how to build when using Ubuntu as the host OS.

Any pointers to how to resolve this would be appreciated.

Thanks,
Tim.

I have just checked and it works for me (using kernel 2.6.18-028stab051).
Could you try using 2.6.18 (i.e. stable) kernels, or 2.6.24? Note that 
2.6.20 (as well as 2.6.22) is frozen and unsupported.

Tim Hudson wrote:
> I've got openvz setup and operating nicely with three VEs (ubuntu7.10, 
> centos4,
> redhat9) - but shell job control does not work in any of them.
>
> ^Z should suspend the current command inside the VE when in a shell 
> where you've
>  ssh'd into the VE - but instead it remains inside the current 
> process. I've
> checked stty settings and they appear equivalent in both the VE and host.
>
> Have I missed enabling something which is mentioned in the 
> documentation or is
> this a known issue?
>
> I'm using 2.6.20-ovz008-openvz1 (built from source) following 
> instructions for
> how to build when using Ubuntu as the host OS.
>
> Any pointers to how to resolve this would be appreciated.
>
> Thanks,
> Tim.
>

Kir Kolyshkin wrote:
> I have just checked and it works for me (using kernel 2.6.18-028stab051).
> Could you try using 2.6.18 (i.e. stable) kernels, or 2.6.24? Note that 
> 2.6.20 (as well as 2.6.22) is frozen and unsupported.

Thanks for the quick response!

As you suspected it works fine in 2.6.18-ovz-028stab051.1-smp - but I had 
problems with building that release from source which is why I moved to the same 
kernel release as the base Ubuntu 7.04 was using as I had no particular kernel 
version preference.

I do have other modules I need to compile up - hence the issue with compiling 
which lead me to a newer kernel release.

How 'stable' is the 2.6.24 release in terms of usage and known issues?

Thanks,
Tim.

Tim Hudson wrote:
> Kir Kolyshkin wrote:
>> I have just checked and it works for me (using kernel 
>> 2.6.18-028stab051).
>> Could you try using 2.6.18 (i.e. stable) kernels, or 2.6.24? Note 
>> that 2.6.20 (as well as 2.6.22) is frozen and unsupported.
>
> Thanks for the quick response!
>
> As you suspected it works fine in 2.6.18-ovz-028stab051.1-smp - but I 
> had problems with building that release from source

Can you elaborate here?

> which is why I moved to the same kernel release as the base Ubuntu 
> 7.04 was using as I had no particular kernel version preference.
>
> I do have other modules I need to compile up

...and here?

> - hence the issue with compiling which lead me to a newer kernel release.
>
> How 'stable' is the 2.6.24 release in terms of usage and known issues?

It hasn't been tested much yet, and still in very active development. We 
have an intention to make it stable though.

Kir Kolyshkin wrote:
> Tim Hudson wrote:
>> Kir Kolyshkin wrote:
>>> I have just checked and it works for me (using kernel 
>>> 2.6.18-028stab051).
>>> Could you try using 2.6.18 (i.e. stable) kernels, or 2.6.24? Note 
>>> that 2.6.20 (as well as 2.6.22) is frozen and unsupported.
>>
>> Thanks for the quick response!
>>
>> As you suspected it works fine in 2.6.18-ovz-028stab051.1-smp - but I 
>> had problems with building that release from source
> 
> Can you elaborate here?

I starting from a fresh git checkout of 2.6.18 from the main repository and 
rebuilt everything cleanly and didn't hit the problem I did with the pre-canned 
setup I grabbed before. I can add in the modules I needed and have a nicely 
working setup.

Thanks for the pointers to getting away from the non-supported 2.6.20 release 
which resolved the original issue. It would be good to see some Wiki entry or 
some note somewhere indicating not to use 2.6.20 (and I assume 2.6.22 from your 
email) as "frozen" doesn't communicate do-not-use to me at least.

Tim.