Hello Dmitry,
Restarting prl-disp did fix the prlctl issues. Will see if I can figure out
some of the other issues, like why some templates will build and others error
saying none of the settings are set.
Thanks,
On 09/25, Dmitry Mishin wrote:
> Hello,
>
> Please check that prl-disp service
Hello,
Please check that prl-disp service is up & running.
Thank you,
Dmitry.
On 25/09/2017, 01:39, "users-boun...@openvz.org on behalf of Mark
Johanson"
wrote:
>Hello,
>
>Sorry if my terminology is wrong, when I refer to virtuozzo I mean the
>paid stuff not openvz. All though now I suppose th
Hello,
Sorry if my terminology is wrong, when I refer to virtuozzo I mean the paid
stuff not openvz. All though now I suppose there really is no difference
between them.
The vzctl commands (ie vzctl list) work and list a running vm:
#vzlist
CTID NPR
So did not mean SolusVM as the hypervisor. Long day and lots of head beating
trying to get things working in OpenVZ 7.
On 09/24, Mark Johanson wrote:
> If I am not using Virtuozzo as a hypervisor, is openvz 7 going to even be
> possible for use?
>
> #prlctl list
> Login failed: Unable to connec
Greetings,
- Original Message -
> If I am not using Virtuozzo as a hypervisor, is openvz 7 going to
> even be possible for use?
>
> #prlctl list
> Login failed: Unable to connect to Virtuozzo. You may experience a
> connection problem or the server may be down. Contact your Virtuozzo
> ad
