Hi Piotr, You've hit a bug, wherein somehow the systemvm.iso wasn't ejected for the 4.17.0.0 systemvm. You can either do it manually on the KVM host (virsh change-media <domain name> <path such as hdb> --eject) or you can restart the network with cleanup=true or in case of systemvms just destroy them.
Regards. ________________________________ From: Wei ZHOU <[email protected]> Sent: Sunday, January 15, 2023 04:09 To: [email protected] <[email protected]> Subject: Re: sysvm live migration 4.17.2 Looks like a bug. systemvm.iso does not exist on 4.17+, it should be ejected when you patched the system vms. Can you retry after ejecting iso by "virsh change-media" ? -Wei On Saturday, 14 January 2023, Piotr Pisz <[email protected]> wrote: > Hi, > > After upgrading CS from 4.17.0 to 4.17.2 I have a strange symptom, live > migration system vm is not working. It ends with the message: > > Exception during migrate: org.libvirt.LibvirtException: Cannot access > storage file '/usr/share/cloudstack-common/vms/systemvm.iso': No such > file or directory > > In the directory it looks like this: > > [root@psc1 vms]# ls -l > razem 281080 > -rw-r--r-- 1 root root 98871867 12-14 06:55 agent.zip > -rw-r--r-- 1 root root 136442 12-14 06:55 cloud-scripts.tgz > -rw-r--r-- 1 root root 4452 12-14 06:55 patch-sysvms.sh > -rw-r--r-- 1 root root 94400512 2021-11-24 systemvm.iso.bak > -rw-r--r-- 1 root root 94404608 2021-11-21 systemvm.iso.bak~ > > Other than that, everything works as expected, I managed to path the > system vm version from 4.16 to 4.17 without any problems. > > Any suggestions? 😊 > > Best regards, > Piotr > >
