OpenVZ Forum: Users » possible container states/statuses

Home » Mailing lists » Users » possible container states/statuses

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

Re: possible container states/statuses [message #42736 is a reply to message #42735]

Tue, 17 May 2011 06:48

knawnd
Messages: 27
Registered: April 2011

Junior Member

> $ vzctl status 103
> CTID 103 exist mounted running
>
> As one can see 'vzctl status' doesn't show running CT as suspended. So
> what is the proper way to detect that state (running and suspended CT)?
I guess because 'suspended' is missing from the output of 'vzctl status'
command for such CT the attempt to stop a CT in such state (running and
suspended) has to be properly traced. For example, 'vzctl stop <CT_ID>'
has to print something like "CT is running and suspended. Please, resume
it by executing 'vzctl chkpnt <CTID> --resume' command in order to stop
it". Right now the action 'vzctl stop <CTID>' on running and suspended
CT ends with "Unable to stop container: operation timed out" what is
expected.

Regards,
Nikolay.

Report message to a moderator

[Message index]

		possible container states/statuses By: knawnd on Mon, 16 May 2011 13:43
		Re: possible container states/statuses By: kir on Mon, 16 May 2011 18:48
		Re: possible container states/statuses By: knawnd on Tue, 17 May 2011 06:13
		Re: possible container states/statuses By: knawnd on Tue, 17 May 2011 06:48
		Re: possible container states/statuses By: KriS83 on Mon, 16 May 2011 19:18
		Re: possible container states/statuses By: knawnd on Tue, 17 May 2011 05:50

Previous Topic:	Slackware 13 weirdness
Next Topic:	how to get the current HN CPU utilization by particular CT

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Mon Dec 15 12:36:21 GMT 2025

Total time taken to generate the page: 0.11640 seconds