[GH-ISSUE #304] How does Live Migration work ? #238

Closed
opened 2026-02-27 16:38:32 +03:00 by kerem · 6 comments
Owner

Originally created by @amarc on GitHub (May 12, 2014).
Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/304

Hello,

could someone point me to some Howto or docs on how live migration works ? Or at least what are requirements ? Does it require only SSH/TCP auth betwen host and destination or something more ? I tried to do migration but it complains about not having /some/path/diskimageofmachine.img on destination.. Isn't that what migration should do? Move disk and evertything needed and start it on destination.. ?

Thanks

Originally created by @amarc on GitHub (May 12, 2014). Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/304 Hello, could someone point me to some Howto or docs on how live migration works ? Or at least what are requirements ? Does it require only SSH/TCP auth betwen host and destination or something more ? I tried to do migration but it complains about not having /some/path/diskimageofmachine.img on destination.. Isn't that what migration should do? Move disk and evertything needed and start it on destination.. ? Thanks
kerem closed this issue 2026-02-27 16:38:32 +03:00
Author
Owner

@AlexH-HankIT commented on GitHub (May 12, 2014):

The live migration feature only migrates the RAM of a running virtual machine. Both hosts need access to the same datastore. Shared Storage for example. You can also use DRBD which will replicated the block devices between two hosts.

<!-- gh-comment-id:42858898 --> @AlexH-HankIT commented on GitHub (May 12, 2014): The live migration feature only migrates the RAM of a running virtual machine. Both hosts need access to the same datastore. Shared Storage for example. You can also use DRBD which will replicated the block devices between two hosts.
Author
Owner

@amarc commented on GitHub (May 13, 2014):

Thank you for comment MrCrankHank. Can someone also tell me if this error means that destination CPU does not support some of these flags, and is there any workaround for this ?

unsupported configuration: guest and host CPU are not compatible: Host CPU does not provide required features: erms, smep, 3dnowprefetch, rdrand, aes, movbe

<!-- gh-comment-id:42947479 --> @amarc commented on GitHub (May 13, 2014): Thank you for comment MrCrankHank. Can someone also tell me if this error means that destination CPU does not support some of these flags, and is there any workaround for this ? unsupported configuration: guest and host CPU are not compatible: Host CPU does not provide required features: erms, smep, 3dnowprefetch, rdrand, aes, movbe
Author
Owner

@retspen commented on GitHub (May 14, 2014):

Remove next line:

  <cpu mode='host-model'>
    <model fallback='allow'/>
  </cpu>
<!-- gh-comment-id:43057628 --> @retspen commented on GitHub (May 14, 2014): Remove next line: ``` <cpu mode='host-model'> <model fallback='allow'/> </cpu> ```
Author
Owner

@amarc commented on GitHub (May 14, 2014):

Great, that works as expected now. Is there any chance that creating a machine will default to this (XML to be without above mentioned) ?

<!-- gh-comment-id:43060543 --> @amarc commented on GitHub (May 14, 2014): Great, that works as expected now. Is there any chance that creating a machine will default to this (XML to be without above mentioned) ?
Author
Owner

@retspen commented on GitHub (May 14, 2014):

Uncheck "Host-Model" when you create new VM.

<!-- gh-comment-id:43060814 --> @retspen commented on GitHub (May 14, 2014): Uncheck "Host-Model" when you create new VM.
Author
Owner

@amarc commented on GitHub (May 14, 2014):

Great.. Thank you @retspen

<!-- gh-comment-id:43062054 --> @amarc commented on GitHub (May 14, 2014): Great.. Thank you @retspen
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/webvirtmgr#238
No description provided.