Bug 1412472
| Summary: | [RFE] VT-d migration | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Peter Xu <peterx> |
| Component: | qemu-kvm-rhev | Assignee: | Peter Xu <peterx> |
| Status: | CLOSED ERRATA | QA Contact: | Pei Zhang <pezhang> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.4 | CC: | chayang, hhuang, juzhang, mrezanin, pezhang, qzhang, virt-maint, zhguo |
| Target Milestone: | rc | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | qemu-kvm-rhev-2.9.0-1.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-01 23:42:15 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Verification: Versions: qemu-kvm-rhev-2.9.0-4.el7.x86_64 3.10.0-666.el7.x86_64 Steps: 1. In src host, boot guest with '-device intel-iommu' # /usr/libexec/qemu-kvm -name rhel7.4 -M q35,kernel-irqchip=split \ -cpu host -m 8G \ -device intel-iommu,intremap=true,caching-mode=true \ -smp 4,sockets=1,cores=4,threads=1 \ -device pcie-root-port,id=root.1,slot=1 \ -device pcie-root-port,id=root.2,slot=2 \ -netdev tap,id=hostnet0,vhost=on \ -device virtio-net-pci,netdev=hostnet0,id=net0,bus=root.1,mac=18:66:da:5f:dd:01 \ -drive file=/mnt/nfv/rhel7.4_nonrt.qcow2,format=qcow2,if=none,id=drive-virtio-blk0,werror=stop,rerror=stop \ -device virtio-blk-pci,drive=drive-virtio-blk0,id=virtio-blk0,bus=root.2 \ -vnc :2 \ -monitor stdio \ 2. In des host, boot guest with '-incoming' < same qemu command line as above step 1> -incoming tcp:0:5555 3. Do Migration from src host to des host (qemu) migrate -d tcp:10.73.72.152:5555 4. Repeat ping-pong migration for several times. Works well. 5. Repeat reboot/shutdown guest several times. Works well. So this bug has been fixed well. Thanks. Set this bug 'VERIFIED' as Comment 3. Please correct me if I was wrong about any step during verification. 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, 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-2017:2392 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, 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-2017:2392 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, 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-2017:2392 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, 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-2017:2392 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, 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-2017:2392 |
Description of problem: Support VT-d migration. Version-Release number of selected component (if applicable): N/A. How reproducible: N/A. Steps to Reproduce: 1. Start VM1 with Intel vIOMMU: $bin -M q35,kernel-irqchip=split -enable-kvm \ -device intel-iommu,intremap=on \ -netdev user,id=net0 \ -device e1000,netdev=net0 \ -m 512M -monitor stdio \ /var/lib/libvirt/images/vm1.qcow2 2. Start VM2 as incoming guest: $bin -M q35,kernel-irqchip=split -enable-kvm \ -device intel-iommu,intremap=on \ -netdev user,id=net0 \ -device e1000,netdev=net0 \ -m 512M -monitor stdio \ -incoming tcp:0:6666 \ /var/lib/libvirt/images/vm1.qcow2 3. Migrate VM1 -> VM2 Actual results: Cannot migrate. Expected results: Migrate should succeed.