Can you please make it available again? I need to install it on a couple of
production servers.
Thanks.
Francisco Menchaca
On Fri, 26 Mar 2021 at 20:30, Christian Ehrhardt <
<email address hidden>> wrote:
> Upstream issue: https://bugzilla.redhat.com/show_bug.cgi?id=1594985
> Upstream fix:
> https://gitlab.com/libvirt/libvirt/-/commit/359b938b8b37254e3e714a2a50e4b9a444516133
> I have a build for you to try in this PPA:
> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4503/
>
> Please let me know if that would work fine for you, then we can consider
> to start the SRU process
>
> ** Bug watch added: Red Hat Bugzilla #1594985
> https://bugzilla.redhat.com/show_bug.cgi?id=1594985
>
> ** Changed in: libvirt (Ubuntu Bionic)
> Status: Confirmed => Triaged
>
> ** Tags added: sever-next
>
> --
> 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,
Thank you very much for your help.
I tried creating the symlink manually and that worked. However, I tried to /launchpad. net/~ci- train-ppa- service/ +archive/ ubuntu/ 4503/ and is
install the build from the launchpad
https:/
not available anymore.
Can you please make it available again? I need to install it on a couple of
production servers.
Thanks.
Francisco Menchaca
On Fri, 26 Mar 2021 at 20:30, Christian Ehrhardt <
<email address hidden>> wrote:
> Upstream issue: https:/ /bugzilla. redhat. com/show_ bug.cgi? id=1594985 /gitlab. com/libvirt/ libvirt/ -/commit/ 359b938b8b37254 e3e714a2a50e4b9 a444516133 /launchpad. net/~ci- train-ppa- service/ +archive/ ubuntu/ 4503/ /bugzilla. redhat. com/show_ bug.cgi? id=1594985 /bugs.launchpad .net/bugs/ 1921325 qemu-system- x86_64 --version dfsg-1ubuntu7. 32) /bugs.launchpad .net/ubuntu/ +source/ libvirt/ +bug/1921325/ +subscriptions
> Upstream fix:
> https:/
> I have a build for you to try in this PPA:
> https:/
>
> Please let me know if that would work fine for you, then we can consider
> to start the SRU process
>
> ** Bug watch added: Red Hat Bugzilla #1594985
> https:/
>
> ** Changed in: libvirt (Ubuntu Bionic)
> Status: Confirmed => Triaged
>
> ** Tags added: sever-next
>
> --
> 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:/
>