Hi OpenVZ mailinglist,
After the last upgrade batch (see below) and reboot to the latest
kernel, prlctl seems to have lost access to my containers.
Any suggestion?
The legacy vzctl cli still works. (I can start and work with the containers)
# vzlist -o ctid
CTID
1ab0f712-3bc4-45d6-b215-49247
I have the same problem here, but in my case,
1. prlctl list -a has the VM listed in shutdown state while vzlist has it
in running state
2. I cannot boot, shutdown, migrate or do anything via prlctl
Everything was working fine in the previous release. Currently my vzmigrate
is broken too for some
Hello
on my side, my last update was on may 23rd , but everything worked fine after
reboot , prlctl ok .
# uname -a
Linux 3.10.0-957.12.2.vz7.86.2 #1 SMP Wed May 15 09:45:34 MSK 2019 x86_64
x86_64 x86_64 GNU/Linux
# cat /etc/virtuozzo-release
OpenVZ release 7.0.10 (254)
# cat /etc/redhat-re
Hi,
# uname -a
Linux 3.10.0-957.12.2.vz7.86.2 #1 SMP Wed May 15 09:45:34 MSK 2019 x86_64
x86_64 x86_64 GNU/Linux
# cat /etc/virtuozzo-release
OpenVZ release 7.0.10 (254)
# cat /etc/redhat-release
Virtuozzo Linux release 7.5
Exactly the same version.
I discovered creating a new ct, results in
Or, how about - /prlctl register 1ab0f712-3bc4-45d6-b215-49247fb93934/
By the way, I hope Virtuozzo can produce more error messages in case
prlctl register failed.
In the past, I even included "--verbose" , nothing show in console nor log.
--
Regards,
George
On 05-Jun-19 11:16 PM, jus...@
