Gregor at HostGIS wrote:
That does, indeed, sound very familiar.
I just vzcfgvalidate-d my config files and it threw up no problems or
errors. :-/
Aww, darn. My thread is here:
http://bugzilla.openvz.org/show_bug.cgi?id=1345
It's embarrassing, though a relief, that by the time I had opened th
That does, indeed, sound very familiar.
I just vzcfgvalidate-d my config files and it threw up no problems or
errors. :-/
Aww, darn. My thread is here:
http://bugzilla.openvz.org/show_bug.cgi?id=1345
It's embarrassing, though a relief, that by the time I had opened the
ticket the problem neve
Gregor at HostGIS wrote:
Unless each VM is stopped from inside it (usually using halt),
stopping the container doesn't manage to stop it most of the time, it
just blocks.
Does it give a timeout? I had an issue before, where "vzctl stop XXX"
would eventually time out, leaving the VE in an unpl
Unless each VM is stopped from inside it (usually using halt), stopping
the container doesn't manage to stop it most of the time, it just blocks.
Does it give a timeout? I had an issue before, where "vzctl stop XXX"
would eventually time out, leaving the VE in an unpleasant state: no
processes
I'm finding that when the host node is being shut down, the vz service
often hangs on stopping. I only have one test VM running. If I vzctl
enter the vm and issue halt, it stops cleanly. Doing shutdown -h seems
more unreliable.
Unless each VM is stopped from inside it (usually using halt), sto
