On Mon, 10 May 2021 at 22:31, Christian Ehrhardt <
<email address hidden>> wrote:
> Hi Francisco,
> I have re-checked but I don't see any other related code for your issue.
> The PPA contains the one fix we know about.
>
> I could think of old guests (that existed and were configured autostart
> before the upgrade) to maybe stay in their odd state. But disabling and
> enabling autostart for them should make it work.
> Is at least that working for you?
>
> --
> 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
>
Hi Christian,
Thanks for your response.
Do you mean disabling and enabling autostart to the old guests?
In our dev lab worked straight away after installing the first PPA you
bundled together, I didn't have to disable and enable autostart.
Kind Regards, /about. me/francisco. menchaca linkedin. com/in/ franciscomencha ca> facebook. com/pacomenchac a> <http:// twitter. com/paquito_>
FRANCISCO MENCHACASALES ENGINEER | https:/
<email address hidden> | +61 406 204 483
<http://
<http://
On Mon, 10 May 2021 at 22:31, Christian Ehrhardt <
<email address hidden>> wrote:
> Hi Francisco, /bugs.launchpad .net/bugs/ 1921325 qemu-system- x86_64 --version dfsg-1ubuntu7. 32) /bugs.launchpad .net/ubuntu/ +source/ libvirt/ +bug/1921325/ +subscriptions
> I have re-checked but I don't see any other related code for your issue.
> The PPA contains the one fix we know about.
>
> I could think of old guests (that existed and were configured autostart
> before the upgrade) to maybe stay in their odd state. But disabling and
> enabling autostart for them should make it work.
> Is at least that working for you?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> 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 emulator version 2.11.1(Debian 1:2.11+
>
>
> $ 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:/
>