Bug 2185031

Summary:	[RFE] virtiofsd: Allow migration with virtiofs attachement (nova inclusion)
Product:	Red Hat Enterprise Linux 9	Reporter:	René Ribaud <rribaud>
Component:	virtiofsd	Assignee:	German Maglione <gmaglione>
Status:	CLOSED MIGRATED	QA Contact:	xiagao
Severity:	medium	Docs Contact:
Priority:	medium
Version:	9.4	CC:	gmaglione, gouthamr, hreitz, jinzhao, juzhang, vgoyal, virt-maint
Target Milestone:	rc	Keywords:	FutureFeature, MigratedToJIRA, Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-22 16:22:17 UTC	Type:	Story
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description René Ribaud 2023-04-06 14:30:39 UTC

Hello folks,

Today migration with a virtiofs attachment is not possible as stated here: https://libvirt.org/kbase/virtiofs.html:
Note: virtiofs currently does not support migration so operations such as migration, save/managed-save, or snapshots with memory are not supported if a VM has a virtiofs filesystem connected.

We have an ongoing implementation for virtiofs within Nova (https://review.opendev.org/q/topic:origin%252Fbp%252Fmanila_shares_attachments_v3)
but the migration features are currently not allowed.

During the previous PTG, we had a conversation with an operator who expressed interest in Nova's virtiofs feature. However, he raised concerns about the feature's inability to support live migration, which he sees as a blocker.

Following our online discussion, I am aware that the virt team is actively addressing this issue.

This BZ aims to track this point and act as an "official" request from the Nova team to allow qemu migration with virtiofs.

Comment 3 RHEL Program Management 2023-09-22 16:19:48 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 4 RHEL Program Management 2023-09-22 16:22:17 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.