Bug 1331549 - Block live migration is refused when tunnelling is on and selective disk migration list is empty
Summary: Block live migration is refused when tunnelling is on and selective disk migr...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-28 18:58 UTC by Pawel Koniszewski
Modified: 2016-05-03 05:46 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-29 06:55:02 UTC


Attachments (Terms of Use)

Description Pawel Koniszewski 2016-04-28 18:58:17 UTC
Description of problem:
Block live migration is refused when libvirt tunnelling is used and list of devices passed to 'migrate_disks' is empty.

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

How reproducible:
100%

Steps to Reproduce:
1. Trigger tunnelled block live migration of virtual machine and pass empty list for migrate_disks parameter 

Actual results:
Block live migration is refused, because selective disk migration does not work with tunnelled live migrations.

Expected results:
Block live migration should work as expected, no additional devices to migrate so it shouldn't fail because of tunnelling

Comment 1 Peter Krempa 2016-04-29 06:55:02 UTC
(In reply to Pawel Koniszewski from comment #0)

[...]

> Actual results:
> Block live migration is refused, because selective disk migration does not
> work with tunnelled live migrations.

Migration with non-shared storage is not supported by libvirt when using the tunelled migration approach. The current plan to add security to the storage migration is to use the ongoing work to add TLS support for all qemu streams rather than trying to squeeze everything through the libvirt streams API.


Note You need to log in before you can comment on or make changes to this bug.