Bug 45256 – Locking for virtual machines

Bug 45256 - Locking for virtual machines


Summary:	Locking for virtual machines

Status:	CLOSED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Virtualization - KVM
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-08-25 07:42 CEST by Stefan Gohmann
Modified:	2023-06-28 10:46 CEST (History)
CC List:	3 users (show)

See Also:	45886
What kind of report is it?:	Bug Report
What type of bug is this?:	7: Crash: Bug causes crash or data loss
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	3: A User would likely not purchase the product
User Pain:	0.240
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2017082421000441, 2017050821000192
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Stefan Gohmann

2017-08-25 07:42:20 CEST

If NFS is used as shared storage, it is possible that a virtual machine is started on two hosts due to migration issues, see Ticket #2017082421000441 as an example.

NFS locking is not allowed for shared storage:
 https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/sect-shared-storage-nfs-migration.html
 http://wiki.qemu.org/Documentation/Migration_with_shared_storage

Maybe something like 'Virtual machine lock manager, virtlockd plugin' could solve this issue:
 https://libvirt.org/locking-lockd.html

Comment 1 Christina Scheinig

2017-12-05 11:39:28 CET

Locking would be nice, if a kernel crash is dumped to an other server, which takes about 2 hours. If the host server is available again, migrated guest systems could be started here by accident.

Comment 2 Stefan Gohmann

2019-01-03 07:19:44 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.