I upgraded from linux-2.6.17-vserver-2.0.2.1/util-vserver-0.30.212-r2 to
linux-2.6.20-vserver-2.2.0/util-vserver-0.30.213 about a month and a
half ago. Didn't have any problems at all.
YMMV, though.
Cheers,
Einar
John Alberts wrote:
> Hi. I'm using vserver successfully on a production server fo
A question - is it possible to have something like the CPU token mechanism,
but for IO operations (f.e. hdd-s) ? I have a problem where one of the
contexts is really heavy on IO and I'd try to limit that. The scheduler is
CFQ, but that does not help much on itself, it's not the scheduling itself
Thank you David and Oliver for your replies. I am glad to see there are
other using Gentoo with vserver happily, but it's disappointing that
noone seems to be using vhashify. That's would be nice to have since I
plan on having up to 60 vhosts.
Oliver: I am somewhat amazed that your setup works. I
I know nothing about catalyst, but had some issue with guest as well, suddenly
they turned out no responding anymore.
The reason was metalog (inside guest) not processing the log messages it got
through /dev/log. I didn't investigate why metalog did not process the log
data anymore...
Since then
This is going to be very vague but please bear with me.
We just rebooted into a new kernel 2.6.20-1.2312.fc5.vs2.2.0.1smp and
now the Catalyst test servers (http) will not automagically restart
correctly when they detects changes in the .pm files. I see the message
it has noticed the changed
Hi. I'm using vserver successfully on a production server for over
1.5 years now. I have upgraded without major problems in the past,
but it seems that there has been a pretty big change in revision
numbers since my last update.
This is a Gentoo host vserver and I am running vserver-sources
v2.0
Daniel Hokka Zakrisson wrote:
Roderick A. Anderson wrote:
With the announcement of the EOL for Fedora Core 5 I'm wondering where
I should go next or if I should go ... next?
So actually this is more a question for Daniel Zakrisson since he
provides the FC5 vserver kernel and vserver-utils RPM
