OpenVZ Forum: Support » OpenVZ on Ubuntu Hardy, can't stop containers

Home » General » Support » OpenVZ on Ubuntu Hardy, can't stop containers

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

OpenVZ on Ubuntu Hardy, can't stop containers [message #32691]

Sun, 24 August 2008 14:40

markusthielmann
Messages: 4
Registered: August 2008

Junior Member

I'm trying to get OpenVZ on Ubuntu Hardy to work. I'm using 2.6.24-21-openvz and I'm able to create, start and use containers (both own containers and downloaded ones, testing hardy and CentOS containers).

The problem is: Whenever I try to stop a container via "sudo vzctl stop <ID>", my keyboard stops working and I'm no longer able to start new applications. Applications running will still work, but after a few minutes they start getting unresponsive.

I'm not even able to shut down, since I'm unable to start the shutdown application. vzctl.log and syslog don't show any information besides "VE 123456 : Stopping VE ...". When shutting down via the power key, I'm able to catch a few error messages from openvz, complaining about problems with the network device driver. Unfortunately, I can't find these messages in any log files.

This might be a configuration problem. Does someone has experienced similar problems?

Report message to a moderator

Re: OpenVZ on Ubuntu Hardy, can't stop containers [message #32694 is a reply to message #32691]

Sun, 24 August 2008 21:40

piavlo
Messages: 159
Registered: January 2007

Senior Member

Check if you have any VE processes in uninterruptable sleep (the D state) or any HN kernel threads in D state?
If you got one of these ,specially kernel thread, then almost certainly your only solution is hard reset of HN.
By the way do you have nfs clients in your VE?

Report message to a moderator

Re: OpenVZ on Ubuntu Hardy, can't stop containers [message #32695 is a reply to message #32694]

Sun, 24 August 2008 22:32

markusthielmann
Messages: 4
Registered: August 2008

Junior Member

No D states, no NFS client.

I'm rebooting the machine quite often (it's my desktop machine), so I tried hard resetting about 20 times since I discovered the problem Smile

Report message to a moderator

Re: OpenVZ on Ubuntu Hardy, can't stop containers [message #32697 is a reply to message #32695]

Sun, 24 August 2008 22:44

piavlo
Messages: 159
Registered: January 2007

Senior Member

Can you see with dmesg or on the console any kernel messages
, if you can't get to the console try setting network console.

Quote:

The problem is: Whenever I try to stop a container via "sudo vzctl stop <ID>", my keyboard stops working and I'm no longer able to start new applications

If your keyboard is stuck and you can run anny apps, how did you check that you have no D states? Smile

Report message to a moderator

Re: OpenVZ on Ubuntu Hardy, can't stop containers [message #32699 is a reply to message #32697]

Mon, 25 August 2008 00:05

markusthielmann
Messages: 4
Registered: August 2008

Junior Member

I finally got a kernel message:

"unregister_netdevice: waiting for lo to become free."

It seems this bug was introduced while patching 028stab053 to the Hardy kernel. At least the last two comments to the Ubuntu Bug report indicate that I'm not the only user with that problem.

https://bugs.launchpad.net/ubuntu/hardy/+source/linux/+bug/2 49137

Report message to a moderator

Re: OpenVZ on Ubuntu Hardy, can't stop containers [message #32738 is a reply to message #32691]

Tue, 26 August 2008 21:07

markusthielmann
Messages: 4
Registered: August 2008

Junior Member

The problem is solved with the latest kernel (2.6.24-21) in "proposed". See https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/25 8044 for details.

Report message to a moderator

Re: OpenVZ on Ubuntu Hardy, can't stop containers [message #32996 is a reply to message #32738]

Tue, 16 September 2008 15:06

darrenm
Messages: 2
Registered: September 2008
Location: UK

Junior Member

markusthielmann wrote on Tue, 26 August 2008 22:07

The problem is solved with the latest kernel (2.6.24-21) in "proposed". See https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/25 8044 for details.

That kernel fixed it for me but now I have no sound. I'm not worried about that though.

I now can't stop VE's when I have NFS client mounts on them. I'm sure I saw something about making a change in the VE to stop the NFS mounts on a halt command but that doesn't seem to be working if I just add umount -a -tnfs to /etc/init.d/halt

Any ideas?

Report message to a moderator