Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-19260

[2100054] Windows VM with WSL2 guest fails to migrate

XMLWordPrintable

    • CNV Virtualization Sprint 220, CNV Virtualization Sprint 221, CNV Virtualization Sprint 222, CNV Virtualization Sprint 223
    • Urgent
    • None

      Description of problem:
      Migration of windows VM that has wsl2 guest fails

      Version-Release number of selected component (if applicable):
      Openshift version: 4.11.0-fc.0
      CNV version: 4.11.0
      HCO image: brew.registry.redhat.io/rh-osbs/iib:251904

      How reproducible:
      100%

      Steps to Reproduce:
      1.Create windows 10 vm with
      cpu:
      features:

      • name: vmx
        policy: require
        2.Start VM (should start OK, wsl2 linux guest should also start OK)
        3.Migrate VM

      Actual results:
      Migration fails

      Expected results:
      Migration succeeds

      Additional info:
      In source virt-handler logs 2 "types" of error messages were found for failed migration:
      1)

      {"component":"virt-launcher","level":"error","msg":"internal error: qemu unexpectedly closed the monitor: 2022-06-21T14:03:47.472258Z qemu-kvm: Guest enabled re-enlightenment notifications, 'tsc-frequency=' has to be specified","pos":"virNetClientProgramDispatchError:172","subcomponent":"libvirt","thread":"30","timestamp":"2022-06-21T14:03:47.763000Z"} {"component":"virt-launcher","level":"info","msg":"2022-06-21T14:03:47.472291Z qemu-kvm: error while loading state for instance 0x0 of device 'cpu'","subcomponent":"libvirt","timestamp":"2022-06-21T14:03:47.763469Z"} {"component":"virt-launcher","kind":"","level":"error","msg":"Live migration failed.","name":"windows-wsl2-1655820075-1479514","namespace":"virt-general-test-wls2","pos":"live-migration-source.go:1052","reason":"error encountered during MigrateToURI3 libvirt api call: virError(Code=1, Domain=10, Message='internal error: qemu unexpectedly closed the monitor: 2022-06-21T14:03:47.472258Z qemu-kvm: Guest enabled re-enlightenment notifications, 'tsc-frequency=' has to be specified\n2022-06-21T14:03:47.472291Z qemu-kvm: error while loading state for instance 0x0 of device 'cpu'\n2022-06-21T14:03:47.474064Z qemu-kvm: load of migration failed: Invalid argument')","timestamp":"2022-06-21T14:03:47.830105Z","uid":"407b7386-4285-40cd-8fb3-a37253f11f7f"} {"component":"virt-launcher","kind":"","level":"error","msg":"Failed to migrate vmi","name":"windows-wsl2-1655820075-1479514","namespace":"virt-general-test-wls2","pos":"server.go:111","reason":"migration job 7d8cf65e-0ca3-4b53-a1c5-cfb912fb0f65 already executed, finished at 2022-06-21 14:03:47.725005494 +0000 UTC, completed: true, failed: true, abortStatus: ","timestamp":"2022-06-21T14:03:47.914858Z","uid":"407b7386-4285-40cd-8fb3-a37253f11f7f"}

      2)

      {"component":"virt-launcher","level":"error","msg":"operation failed: migration out job: unexpectedly failed","pos":"qemuMigrationJobCheckStatus:1749","subcomponent":"libvirt","thread":"33","timestamp":"2022-06-21T19:40:49.306000Z"} {"component":"virt-launcher","kind":"","level":"error","msg":"Failed to migrate vmi","name":"windows-wsl2-1655828106-1022391","namespace":"virt-general-test-wls2","pos":"server.go:111","reason":"migration job 89a5647e-04bb-4389-a0e2-975e3d570034 already executed, finished at 2022-06-21 19:40:49.646566613 +0000 UTC, completed: true, failed: true, abortStatus: ","timestamp":"2022-06-21T19:40:49.769054Z","uid":"099cb027-11f1-45d7-a99a-b5f51b724a33"} {"component":"virt-launcher","level":"error","msg":"internal error: qemu unexpectedly closed the monitor: 2022-06-21T19:40:49.239598Z qemu-kvm: Guest enabled re-enlightenment notifications, 'tsc-frequency=' has to be specified","pos":"virNetClientProgramDispatchError:172","subcomponent":"libvirt","thread":"33","timestamp":"2022-06-21T19:40:50.010000Z"} {"component":"virt-launcher","level":"info","msg":"2022-06-21T19:40:49.239642Z qemu-kvm: error while loading state for instance 0x0 of device 'cpu'","subcomponent":"libvirt","timestamp":"2022-06-21T19:40:50.011006Z"} {"component":"virt-launcher","level":"error","msg":"End of file while reading data: Input/output error","pos":"virNetSocketReadWire:1792","subcomponent":"libvirt","thread":"29","timestamp":"2022-06-21T19:40:50.011000Z"} {"component":"virt-launcher","level":"error","msg":"internal error: client socket is closed","pos":"virNetClientSendInternal:2159","subcomponent":"libvirt","thread":"33","timestamp":"2022-06-21T19:40:50.028000Z"} {"component":"virt-launcher","kind":"","level":"error","msg":"Live migration failed.","name":"windows-wsl2-1655828106-1022391","namespace":"virt-general-test-wls2","pos":"live-migration-source.go:1052","reason":"error encountered during MigrateToURI3 libvirt api call: virError(Code=1, Domain=7, Message='internal error: client socket is closed')","timestamp":"2022-06-21T19:40:50.039747Z","uid":"099cb027-11f1-45d7-a99a-b5f51b724a33"}

      Removing
      cpu:
      features:

      • name: vmx
        policy: require
        from VM spec fixes the migration issue, but wsl2 guest won't work

              iholder@redhat.com Itamar Holder
              vsibirsk Vasiliy Sibirskiy
              Vasiliy Sibirskiy Vasiliy Sibirskiy
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: