Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-137735

[Windows]Can not connect to VM via vsock after migration

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • rhel-10.2
    • virtio-win
    • None
    • Important
    • rhel-virt-windows
    • None
    • QE ack
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • Red Hat Enterprise Linux
    • None
    • None
    • Yes
    • Unspecified
    • Unspecified
    • Unspecified
    • x86_64
    • Windows
    • None

      What were you trying to do that didn't work?
      Try to connect to VM via vsock after VM migration

      Please provide the package NVR for which bug is seen:
      kernel-6.12.0-151.el10.x86_64
      qemu-kvm-10.1.0-3.el10.x86_64
      edk2-ovmf-20250822-1.el10.noarch
      prewhql-294

      How reproducible:
      100%

      Steps to reproduce
      1.Boot up a src VM(guest-cid=4), a dst VM(guest-cid=5).
      2.Try to connect to src VM, it works well
      3.Migrate src VM to dst VM, no errors during migration, and migration finished successfully
      4.Try to connect to dst VM. can not connect to dst VM

      Expected results
      Connect to VM successfully

      Actual results

      1. ssh -o ProxyCommand="socat - VSOCK-CONNECT:5:22" Administrator@0.0.0.0
        2025/12/24 22:40:15 socat[1252176] E connect(5, AF=40 cid:5 port:22, 16): Connection timed out
        Connection closed by UNKNOWN port 65535

              leidwang Leidong Wang
              leidwang Leidong Wang
              Virt Windows SST Bugs Virt Windows SST Bugs
              Leidong Wang Leidong Wang
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: