Comment 9 for bug 1921325

Thank you very much Christian.

I apologise for not responding earlier.

Quick question do PPA's are integrated into future patches?

Thanks in advance for your help.

Regards,

Francisco

On Fri, 16 Apr 2021, 4:15 pm Christian Ehrhardt , <
<email address hidden>> wrote:

> Hi Francisco,
> I thought I had lost your activity on this case - glad to see you back on
> it.
> Yeah the old PPA is gone - you fell victim to my bi-yearly PPA cleanup :-)
> At some point I have to give launchpad all its gigabytes back ...
>
> I rebased the branch (since it aged anyway) and have thrown a new build
> into
> this new PPA/ticket:
>
> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4529
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1921325
>
> Title:
> VM will not auto-start automatically when server is rebooted after
> virsh domrename
>
> Status in libvirt package in Ubuntu:
> Fix Released
> Status in libvirt source package in Bionic:
> Triaged
> Status in libvirt source package in Focal:
> Fix Released
>
> Bug description:
>
> OS: Ubuntu 18.04.5
> uname -r
> 4.15.0-118-generic
>
>
> /usr/bin/qemu-system-x86_64 --version
> QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.32)
>
>
> $ virsh version
> Compiled against library: libvirt 4.0.0
> Using library: libvirt 4.0.0
> Using API: QEMU 4.0.0
> Running hypervisor: QEMU 2.11.1
>
> VM running on KVM on different servers won't start automatically when
> the server is rebooted after changing the VM domain name.
>
> Issue Replication:
>
> 1. Set the VM to autostart
> 2. Reboot the server
> 3. VM will start automatically
> 4. Changed the VM domain name virsh domrename VM.old VM.new
> 5. Set the VM.new domain to autostart
> 6. Reboot the server
> 7. VM.new won't start automatically.
>
> Can you please assist?
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions
>