Bug 1945589 - Live migration with virtiofs is possible
Summary: Live migration with virtiofs is possible
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Virtualization
Version: 2.6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.9.0
Assignee: Nahshon Unna-Tsameret
QA Contact: zhe peng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-01 11:02 UTC by Fabian Deutsch
Modified: 2021-11-02 15:57 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-02 15:57:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt kubevirt pull 5763 0 None closed Prevent migration of VMIs that uses virtiofs 2021-06-20 08:56:18 UTC
Red Hat Product Errata RHSA-2021:4104 0 None None None 2021-11-02 15:57:41 UTC

Description Fabian Deutsch 2021-04-01 11:02:53 UTC 
Description of problem:
VMs using virtiofs can currently be migrated but this should not be possible due to technical limitations

Version-Release number of selected component (if applicable):
2.6

How reproducible:


Steps to Reproduce:
1. Create vm with virtiofs PVC
2. live migrate
3.

Actual results:
Live migration is started

Expected results:
Live migration should be blocker

Additional info:
virtiofs is not yet supported, yet it is a known issue
Comment 1 sgott 2021-07-12 17:48:35 UTC 
Targetting this BZ to the next release as a PR to solve it is merged upstream.
Comment 2 Kedar Bidarkar 2021-09-06 14:37:24 UTC 
[kbidarka@localhost virtiofs]$ oc apply -f vm-rhel84-virtiofs-ocsfs.yaml
virtualmachine.kubevirt.io/vm-rhel84-virtiofs-ocsfs created

[kbidarka@localhost virtiofs]$ oc get vmi
NAME                       AGE     PHASE       IP             NODENAME                           READY
vm-rhel84-virtiofs-ocsfs   18s     Running     xx.yy.zz.aa   cnvqe-lab13.redhat.com   True

----

[kbidarka@localhost migration]$ cat migration-job-dv.yaml
apiVersion: kubevirt.io/v1alpha3
kind: VirtualMachineInstanceMigration
metadata:
  creationTimestamp: null
  name: job-vm-rhel83
  namespace: default
spec:
  vmiName: vm-rhel84-virtiofs-ocsfs
status: {}

[kbidarka@localhost migration]$ oc get vmi
NAME                        AGE    PHASE     IP             NODENAME                           READY
vm-rhel84-virtiofs-ocsfs    11m    Running   xx.yy.zz.aa   cnvqe-lab13.redhat.com   True

[kbidarka@localhost migration]$ oc apply -f migration-job-dv.yaml
Error from server: error when creating "migration-job-dv.yaml": admission webhook "migration-create-validator.kubevirt.io" denied the request: Cannot migrate VMI, Reason: VirtIOFSNotLiveMigratable, Message: VMI uses virtiofs

[kbidarka@localhost migration]$ oc describe vmi vm-rhel84-virtiofs-ocsfs | grep -B 10 LiveMigratable
  Active Pods:
    05d6f60f-6916-4b4e-9607-927375aec507:  cnvqe-lab13.redhat.com
  Conditions:
    Last Probe Time:       <nil>
    Last Transition Time:  2021-09-06T13:55:45Z
    Status:                True
    Type:                  Ready
    Last Probe Time:       <nil>
    Last Transition Time:  <nil>
    Message:               VMI uses virtiofs
    Reason:                VirtIOFSNotLiveMigratable
    Status:                False
    Type:                  LiveMigratable



VERIFIED with: virt-operator/images/v4.9.0-40
Comment 5 errata-xmlrpc 2021-11-02 15:57:28 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Virtualization 4.9.0 Images security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:4104
Note You need to log in before you can comment on or make changes to this bug.