>
> Before rebooting hardware node I would try `vzctl chkpnt
> --resume` first, just in case.
>
bingo, thank you.
___
Users mailing list
Users@openvz.org
https://openvz.org/mailman/listinfo/users
Before rebooting hardware node I would try `vzctl chkpnt
--resume` first, just in case.
On 8/12/10, Gregor at HostGIS wrote:
> I got this all the time on other containers, and nobody was ever able to
> diagnose it. Fortunately the issue was corrected by upgrading to the
> latest 2.6.18 kernel
I got this all the time on other containers, and nobody was ever able to
diagnose it. Fortunately the issue was corrected by upgrading to the
latest 2.6.18 kernel and the latest vzctl.
But the kernel fix, as well as the "fix" for the frozen containers, was
to reboot the HN. And the HN shutdown
>
> i just tried my first vzmigrate (--online). it said "Failed to suspend
> container". vzps now shows "refridgerator" for its processes in the WCHAN
> column. vzctl stop or restart say "operation timed out". vzctl start says
> "Container is already running". man vzctl suggests a --fast stop
i just tried my first vzmigrate (--online). it said "Failed to suspend
container". vzps now shows "refridgerator" for its processes in the WCHAN
column. vzctl stop or restart say "operation timed out". vzctl start says
"Container is already running". man vzctl suggests a --fast stop option,
bu