Hi guys. With this relatively new modular approach in libvirt - which service is needed in order to migrate guests via tcp? many thanks, L. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20230416/6d59d01b/attachment.htm>
> > With this relatively new modular approach in libvirt - which service is > needed in order to migrate guests via tcp? >I am not sure what you mean with 'new modular'. I am still on el7 going to el9 this year. I am doing live migrations just with these. libvirtd.service enabled virtlockd.socket enabled virtlogd.socket enabled
On Sun, Apr 16, 2023 at 08:54:57 +0200, lejeczek wrote:> Hi guys. > > With this relatively new modular approach in libvirt - which service is > needed in order to migrate guests via tcp?There is nothing special needed for migration when compared to running a VM. With new daemons you need 'virtqemud' to manage the VM and optionally 'virtnetworkd' if the VM uses libvirt-managed networks, 'virtstoraged' if it uses libvirt managed storage, and/or 'virtsecretd' if it uses secrets storage. Configuration of daemon options moved to the appropriate per-daemon config file.