OpenVZ Forum


Home » General » Support » *SOLVED* Graphical Desktops cause othersockbuf failures
icon5.gif  *SOLVED* Graphical Desktops cause othersockbuf failures [message #10281] Wed, 14 February 2007 10:34 Go to next message
alevchuk is currently offline  alevchuk
Messages: 22
Registered: February 2007
Location: University of California,...
Junior Member
I'm probably one of the first who is trying to run graphical desktops under OpenVZ.

My goal is to provide VE's with graphical desktops for the Computer Science department of my university. This is about 300 students.

On my intentionally weak test server (1.4 GHz AMD Athlon with 1.6 GB Ram):
* I have compiled ovz028test015.1 kernel on Unbuntu
* I made a Xubuntu 7.04 (The Feisty Fawn) OpenVZ template
* I can start a the graphical session inside the VE, connecting to it with NX

Besides a few warning dialogs, the desktop environment start-up fine, I can even open a number of small applications.

But launching the browser, or even opening several terminals (in X) causes things to become unstable: New applications crash before they get started.

In the terminal I got some: memory cannot be allocated
And failed attempts to fork.


Please help!


There are othersockbuf failures in my beancounters, here is what it looks like:
http://pastebin.ca/355273

I tried raising the limits with "vzctl set".
This gets rid of the failures, but does not solve the problem.



[Updated on: Thu, 15 February 2007 10:14] by Moderator

Report message to a moderator

Re: Graphical Desktops cause othersockbuf failures [message #10283 is a reply to message #10281] Wed, 14 February 2007 11:45 Go to previous messageGo to next message
Vasily Tarasov is currently offline  Vasily Tarasov
Messages: 1345
Registered: January 2006
Senior Member
Hello,

are you sure, that there is no failcounters at all now?

Thanks,
Vasily.
Re: Graphical Desktops cause othersockbuf failures [message #10311 is a reply to message #10283] Wed, 14 February 2007 18:09 Go to previous message
alevchuk is currently offline  alevchuk
Messages: 22
Registered: February 2007
Location: University of California,...
Junior Member
Yes - you are right. Later at night I started noticing other failcounters. I had to increase the following limit to eliminate the failcounters:

sudo vzctl set 232 --privvmpages 491520:535750 --save
sudo vzctl set 232 --numfile 20480:20480 --save
sudo vzctl set 232 --othersockbuf 1320960:3368960 --save
sudo vzctl set 232 --othersockbuf 1320960:3368960 --save
sudo vzctl set 232 --numothersock 800 --save
sudo vzctl set 232 --othersockbuf 1320960:3368960 --save

The values are the same as my original but multiplied by 10.

It works now!

There is only one warning dialog that pops-up when the Virtualized Xubuntu Feisty is starting: "Failed to initialize HAL!", but everithing works!
Previous Topic: NIC problem with openvz patched kernel
Next Topic: *SOLVED* Out of Socket Memory on the Hardware Node
Goto Forum:
  


Current Time: Mon Aug 12 08:34:16 GMT 2024

Total time taken to generate the page: 0.02766 seconds