* [PVE-User] can't lock file '/var/lock/qemu-server/lock-XXX.conf' - got timeout
@ 2024-02-06 12:05 Andrei Boros
0 siblings, 0 replies; only message in thread
From: Andrei Boros @ 2024-02-06 12:05 UTC (permalink / raw)
To: pve-user
Hi,
I am encountering problems stopping VMs. It happens intermittently.
I have a Ubuntu-22.04 server edition. Not yet installed qemu agent inside.
I have a generic Linux VM in which I want to use G4L to import disk image.
I have a Win10 for testing, with qemu-agent and drivers.
All these machines can't be stopped or reset.
I am talking about HARD STOP or HARD RESET.
From the top menu, shutdown dropdown -> Stop. It says command stop
successful. Nothing happens.
From noVNC console, power -> hard stop. It says command stop successful.
Nothing happens.
From node shell: qm stop XXX
fails showing: can't lock file '/var/lock/qemu-server/lock-XXX.conf' -
got timeout
The Win10 machine shuts down gracefully only when a user is logged in.
If requesting shutdown at login screen, nothing happens. And the stop
command fails as well.
And after all this, 10-15 minutes later, it magically works!
Is it a bug? Am I doing something wrong?
Thank you.
--
*ing. Andrei Boros*
Serviciul IT&C
*Radio Romania*
|Tel: +40-21-303-1870
+40-745-115721
Email: andrei@srr.ro <mailto:andrei@srr.ro>|
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2024-02-06 12:20 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-02-06 12:05 [PVE-User] can't lock file '/var/lock/qemu-server/lock-XXX.conf' - got timeout Andrei Boros
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox