Re: [Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

[Christian Ehrhardt ]

> Hi Chhristian.
>
> I am going to try to install the ppa on a different Ubuntu 18.04 server
> and will let you know my findings.

Thanks in advance

> The only difference from the preduction servers and my test server is
> the following:
>
> Production servers were upgraded from Ubuntu 16.04 to Ubuntu 18.04 and
> the production servers are sitting behind a proxy server.

Thanks for letting me know, but in this case that should (tm) not make
a difference.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921325

Title:
  VM will not auto-start automatically when server is rebooted after
  virsh domrename

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

[Francisco Menchaca]

Hi Chhristian.

I am going to try to install the ppa on a different Ubuntu 18.04 server
and will let you know my findings.

The only difference from the preduction servers and my test server is
the following:

Production servers were upgraded from Ubuntu 16.04 to Ubuntu 18.04 and
the production servers are sitting behind a proxy server.

Cheers.

Francisco

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921325

Title:
  VM will not auto-start automatically when server is rebooted after
  virsh domrename

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

[Christian Ehrhardt ]

On Tue, May 11, 2021 at 1:35 AM Francisco Menchaca
<1921...@bugs.launchpad.net> wrote:
>
> 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.

I didn't have to do it in any of my tests either, all I was saying was
"whatever it is maybe it helps there".
As I said I'm lost on options a bit, I could get the fix prepared to
get into Ubuntu as-is, but since you seem to have a more complex issue
underneath in your prod environment we need to find if there the fix
a) doesn't help at all
b) only helps after guest autostart off/on
c) only helps after (b) plus service or even system restart
d) ??? something else ???

Since only your environment is affected by this new special behavior I
can't really debug/help much until we know what the difference is :-/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921325

Title:
  VM will not auto-start automatically when server is rebooted after
  virsh domrename

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

[Francisco Menchaca]

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,
FRANCISCO MENCHACASALES ENGINEER | https://about.me/francisco.menchaca
fxm...@gmail.com | +61 406 204 483

  


On Mon, 10 May 2021 at 22:31, Christian Ehrhardt  <
1921...@bugs.launchpad.net> 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
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921325

Title:
  VM will not auto-start automatically when server is rebooted after
  virsh domrename

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

[Christian Ehrhardt ]

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 a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921325

Title:
  VM will not auto-start automatically when server is rebooted after
  virsh domrename

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

[Francisco Menchaca]

Hi Christian,

I fixed our time synch issue and install the ppa in our dev server where it 
seemed to work.
I can reboot the VMs and they will auto start automatically.

However last night we tried to install the ppa's on two production
Ubuntu 18.04.5 servers and the patch did not seem to work. We also tried
creating a symlink pointed to /etc/libvirt/qemu/autostart and the new VM
name was already there.

pladmin@EQX-ESM-PRE-01:~$ ll /etc/libvirt/qemu/autostart
total 8
drwxr-xr-x 2 root root 4096 May  6 16:12 ./
drwxr-xr-x 4 root root 4096 May  6 16:03 ../
lrwxrwxrwx 1 root root   37 May  6 16:12 EQX-ESM-vPRE-01.xml -> 
/etc/libvirt/qemu/EQX-ESM-vPRE-01.xml

See below libvirt log on one of the servers:

pladmin@EQX-ESM-PRE-01:/var/log/libvirt/qemu$ sudo cat EQX-ESM-vPRE-01.log
2021-05-06 16:01:56.444+: shutting down, reason=failed
2021-05-06 16:10:14.867+: starting up libvirt version: 4.0.0, package: 
1ubuntu8.20~bionicppa1 (Christian Ehrhardt  
Fri, 26 Mar 2021 10:21:27 +0100), qemu version: 2.11.1(Debian 
1:2.11+dfsg-1ubuntu7.36), hostname: EQX-ESM-PRE-01
LC_ALL=C 
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin 
QEMU_AUDIO_DRV=none /usr/bin/kvm-spice -name 
guest=EQX-ESM-vPRE-01,debug-threads=on -S -object 
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-2-EQX-ESM-vPRE-01/master-key.aes
 -machine pc-i440fx-bionic,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off 
-cpu host -m 327680 -realtime mlock=off -smp 68,sockets=2,cores=17,threads=2 
-object 
memory-backend-file,id=ram-node0,prealloc=yes,mem-path=/dev/hugepages/libvirt/qemu/2-EQX-ESM-vPRE-01,size=171798691840,host-nodes=0,policy=bind
 -numa node,nodeid=0,cpus=0-33,memdev=ram-node0 -object 
memory-backend-file,id=ram-node1,prealloc=yes,mem-path=/dev/hugepages/libvirt/qemu/2-EQX-ESM-vPRE-01,size=171798691840,host-nodes=1,policy=bind
 -numa node,nodeid=1,cpus=34-67,memdev=ram-node1 -uuid 
840d50b7-de45-4743-84d0-a62aa72e476b -display none -no-user-config -nodefaults 
-chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-2-EQX-ESM-vPRE-01/monitor.sock,server,nowait
 -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew 
-global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -global 
PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device 
pxb,bus_nr=180,id=pci.1,numa_node=0,bus=pci.0,addr=0xe -device 
pxb,bus_nr=200,id=pci.2,numa_node=1,bus=pci.0,addr=0xf -device 
ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x4.0x7 -device 
ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x4 
-device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x4.0x1 
-device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x4.0x2 
-drive 
file=/opt/VM/vpre/vpre.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none
 -device 
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
 -netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=28 -device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:5c:8c:15,bus=pci.0,addr=0x2 
-netdev tap,fd=29,id=hostnet1,vhost=on,vhostfd=30 -device 
virtio-net-pci,netdev=hostnet1,id=net1,mac=52:54:00:93:88:db,bus=pci.0,addr=0x3 
-chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 
-device vfio-pci,host=19:02.0,id=hostdev0,bus=pci.1,addr=0x1 -device 
vfio-pci,host=19:0a.0,id=hostdev1,bus=pci.1,addr=0x2 -device 
vfio-pci,host=3b:02.0,id=hostdev2,bus=pci.1,addr=0x3 -device 
vfio-pci,host=3b:0a.0,id=hostdev3,bus=pci.1,addr=0x4 -device 
vfio-pci,host=5e:02.0,id=hostdev4,bus=pci.1,addr=0x5 -device 
vfio-pci,host=5e:0a.0,id=hostdev5,bus=pci.1,addr=0x6 -device 
vfio-pci,host=60:02.0,id=hostdev6,bus=pci.1,addr=0x7 -device 
vfio-pci,host=60:0a.0,id=hostdev7,bus=pci.1,addr=0x8 -device 
vfio-pci,host=86:02.0,id=hostdev8,bus=pci.2,addr=0x1 -device 
vfio-pci,host=86:0a.0,id=hostdev9,bus=pci.2,addr=0x2 -device 
vfio-pci,host=88:02.0,id=hostdev10,bus=pci.2,addr=0x3 -device 
vfio-pci,host=88:0a.0,id=hostdev11,bus=pci.2,addr=0x4 -device 
vfio-pci,host=d8:02.0,id=hostdev12,bus=pci.2,addr=0x5 -device 
vfio-pci,host=d8:0a.0,id=hostdev13,bus=pci.2,addr=0x6 -object 
rng-random,id=objrng0,filename=/dev/urandom -device 
virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.0,addr=0x6 -msg timestamp=on
2021-05-06 16:10:14.867+: Domain id=2 is tainted: host-cpu
2021-05-06T16:10:14.892182Z qemu-system-x86_64: -chardev pty,id=charserial0: 
char device redirected to /dev/pts/2 (label charserial0)
2021-05-06 16:21:54.059+: shutting down, reason=failed
2021-05-06 16:26:34.240+: starting up libvirt version: 4.0.0, package: 
1ubuntu8.20~bionicppa1 (Christian Ehrhardt  
Fri, 26 Mar 2021 10:21:27 +0100), qemu version: 2.11.1(Debian 
1:2.11+dfsg-1ubuntu7.36), hostname: EQX-ESM-PRE-01
LC_ALL=C 
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin 
QEMU_AUDIO_DRV=none /usr/bin/kvm-spice -name 
guest=EQX-ESM-vPRE-01,debug-threads=on -S -object 

[Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

[Christian Ehrhardt ]

I see two problems

#1
The new PPA is 4529 which seems to work in your output.
But you still have the old (deleted) one configured as well.
You'll probably want to clear that old one out:
$ sudo rm /etc/apt/sources.list.d/ci-train-ppa-service-4503-bionic.list
$ sudo apt update
(I have guessed the filenme, but it will be that or very similar)

#2 it seems your system is very much "out of time"
" is not valid yet (invalid for another 13d 22h 14min 55s)."
You'd have to have a valid system time for most things to work (cryptography, 
updates, ...)
I'm not sure but could it be so easy as "set your time right"?
Please check
$ date
if it is anywhere close to real time

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921325

Title:
  VM will not auto-start automatically when server is rebooted after
  virsh domrename

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

[Francisco Menchaca]

Hi Christian,

An update I tried reinstalling the ppa again and received the following
error:

Can you please advise what I'm doing wrong?


pladmin@maser-devtest-kvm:~$ sudo apt-get update

Hit:1 http://au.archive.ubuntu.com/ubuntu bionic InRelease

Err:3 http://ppa.launchpad.net/ci-train-ppa-service/4503/ubuntu bionic
InRelease

  403  Forbidden [IP: 91.189.95.85 80]

Get:4 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7
kB]


Get:2 http://au.archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]


Get:5 http://au.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6
kB]

Get:6 http://ppa.launchpad.net/ci-train-ppa-service/4529/ubuntu bionic
InRelease [20.8 kB]

Reading package lists... Done

E: Failed to fetch
http://ppa.launchpad.net/ci-train-ppa-service/4503/ubuntu/dists/bionic/InRelease
403  Forbidden [IP: 91.189.95.85 80]

E: The repository 'http://ppa.launchpad.net/ci-train-ppa-service/4503/ubuntu
bionic InRelease' is no longer signed.

N: Updating from such a repository can't be done securely, and is therefore
disabled by default.

N: See apt-secure(8) manpage for repository creation and user configuration
details.

E: Release file for
http://au.archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease is not
valid yet (invalid for another 13d 20h 8min 41s). Updates for this
repository will not be applied.

E: Release file for
http://au.archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease is not
valid yet (invalid for another 13d 20h 9min 42s). Updates for this
repository will not be applied.

E: Release file for
http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease is not
valid yet (invalid for another 13d 22h 14min 55s). Updates for this
repository will not be applied.

E: Release file for
http://ppa.launchpad.net/ci-train-ppa-service/4529/ubuntu/dists/bionic/InRelease
is not valid yet (invalid for another 9d 3h 57min 50s). Updates for this
repository will not be applied.
FRANCISCO MENCHACASALES ENGINEER | https://about.me/francisco.menchaca
fxm...@gmail.com | +61 406 204 483

  


On Tue, 20 Apr 2021 at 01:41, Paco Menchaca  wrote:

> Hi Christian,
>
> We tried installing the build you supplied:
>
> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4529
>
> In two different systems running Ubuntu 18.04.5 and we received this error:
>
> pladmin@maser-devtest-kvm:~$ sudo add-apt-repository
> ppa:ci-train-ppa-service/4529
>
> [sudo] password for pladmin:
>
> Cannot add PPA: 'ppa:~ci-train-ppa-service/ubuntu/4529'.
>
> ERROR: '~ci-train-ppa-service' user or team does not exist.
>
>
>
>
>
>
>
>
>
> Also , is there a way to install the ppa manually??
>
> Thanks in advance.
>
> FRANCISCO MENCHACASALES ENGINEER | https://about.me/francisco.menchaca
> fxm...@gmail.com | +61 406 204 483
> 
>
>
> On Fri, 16 Apr 2021 at 16:15, Christian Ehrhardt  <
> 1921...@bugs.launchpad.net> 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
>>
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

Re: [Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

[Francisco Menchaca]

Hi Christian,

We tried installing the build you supplied:

https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4529

In two different systems running Ubuntu 18.04.5 and we received this
error:

pladmin@maser-devtest-kvm:~$ sudo add-apt-repository
ppa:ci-train-ppa-service/4529

[sudo] password for pladmin:

Cannot add PPA: 'ppa:~ci-train-ppa-service/ubuntu/4529'.

ERROR: '~ci-train-ppa-service' user or team does not exist.





Also , is there a way to install the ppa manually??

Thanks in advance.

FRANCISCO MENCHACASALES ENGINEER | https://about.me/francisco.menchaca
fxm...@gmail.com | +61 406 204 483



On Fri, 16 Apr 2021 at 16:15, Christian Ehrhardt  <
1921...@bugs.launchpad.net> 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
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921325

Title:
  VM will not auto-start automatically when server is rebooted after
  virsh domrename

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

[Francisco Menchaca]

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 , <
1921...@bugs.launchpad.net> 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
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921325

Title:
  VM will not auto-start automatically when server is rebooted after
  virsh domrename

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

[Christian Ehrhardt ]

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 a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921325

Title:
  VM will not auto-start automatically when server is rebooted after
  virsh domrename

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

[Francisco Menchaca]

Hi Christian,

Thank you very much for your help.

I tried creating the symlink manually and that worked.  However, I tried to
install the build from the launchpad
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4503/ and is
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  <
1921...@bugs.launchpad.net> 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
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921325

Title:
  VM will not auto-start automatically when server is rebooted after
  virsh domrename

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

[Christian Ehrhardt ]

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 a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921325

Title:
  VM will not auto-start automatically when server is rebooted after
  virsh domrename

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

[Christian Ehrhardt ]

Interestingly after manually creating the symlink it works again.


root@b:~# virsh autostart --disable h-test-newname
Domain h-test-newname unmarked as autostarted

root@b:~# ll /etc/libvirt/qemu/autostart/
total 2
drwxr-xr-x 2 root root 2 Mar 26 09:16 ./
drwxr-xr-x 4 root root 5 Mar 26 09:13 ../
root@b:~# virsh autostart h-test-newname
Domain h-test-newname marked as autostarted

root@b:~# ll /etc/libvirt/qemu/autostart/
total 3
drwxr-xr-x 2 root root  3 Mar 26 09:17 ./
drwxr-xr-x 4 root root  5 Mar 26 09:13 ../
lrwxrwxrwx 1 root root 36 Mar 26 09:17 h-test-newname.xml -> 
/etc/libvirt/qemu/h-test-newname.xml

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921325

Title:
  VM will not auto-start automatically when server is rebooted after
  virsh domrename

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

[Christian Ehrhardt ]

Bionic seems indeed broken in this use case

root@b:~# virsh domrename h-test h-test-newname
Domain successfully renamed

root@b:~# ll /etc/libvirt/qemu/autostart/
total 3
drwxr-xr-x 2 root root  3 Mar 26 08:56 ./
drwxr-xr-x 4 root root  5 Mar 26 09:13 ../
lrwxrwxrwx 1 root root 28 Mar 26 08:56 h-test.xml -> 
/etc/libvirt/qemu/h-test.xml


You already mentioned that you issue "virsh autostart" again after the rename, 
which in newer releases isn't needed anymore.


Indeed this will now fail to create the matching link
root@b:~# virsh autostart h-test-newname
Domain h-test-newname marked as autostarted

root@b:~# ll /etc/libvirt/qemu/autostart/
total 3
drwxr-xr-x 2 root root  3 Mar 26 08:56 ./
drwxr-xr-x 4 root root  5 Mar 26 09:13 ../
lrwxrwxrwx 1 root root 28 Mar 26 08:56 h-test.xml -> 
/etc/libvirt/qemu/h-test.xml


Until I've found the fix (if it is backportable at all) this will be an easy 
workaround:
root@b:~# ln -s /etc/libvirt/qemu/h-test-newname.xml 
/etc/libvirt/qemu/autostart/
root@b:~# ll /etc/libvirt/qemu/autostart/
total 3
drwxr-xr-x 2 root root  3 Mar 26 09:15 ./
drwxr-xr-x 4 root root  5 Mar 26 09:13 ../
lrwxrwxrwx 1 root root 36 Mar 26 09:15 h-test-newname.xml -> 
/etc/libvirt/qemu/h-test-newname.xml

** Changed in: libvirt (Ubuntu Bionic)
   Status: New => Confirmed

** Changed in: libvirt (Ubuntu Focal)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921325

Title:
  VM will not auto-start automatically when server is rebooted after
  virsh domrename

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

[Christian Ehrhardt ]

Focal is ok

root@f:~# virsh domrename h-test h-test-newname
Domain successfully renamed

root@f:~# ll /etc/libvirt/qemu/autostart/
total 3
drwxr-xr-x 2 root root  3 Mar 26 09:13 ./
drwxr-xr-x 4 root root  5 Mar 26 09:13 ../
lrwxrwxrwx 1 root root 36 Mar 26 09:13 h-test-newname.xml -> 
/etc/libvirt/qemu/h-test-newname.xml
root@f:~# reboot
root@f:~# [✗=129]─[paelzer@Keschdeichel ~]──[203673]──[10:13 Fr Mär 26]──
$ lxc exec f bash
root@f:~# virsh list
 Id   Name State

 1h-test-newname   running

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921325

Title:
  VM will not auto-start automatically when server is rebooted after
  virsh domrename

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

[Christian Ehrhardt ]

I tried Bionic and Focal.
Setting autostart as well as seeing the effect on reboot worked just the same 
there:

oot@b:~# virsh autostart h-test
Domain h-test marked as autostarted

root@b:~# ll /etc/libvirt/qemu/autostart/
total 2
drwxr-xr-x 2 root root  3 Mar 26 08:56 ./
drwxr-xr-x 4 root root  5 Mar 26 08:56 ../
lrwxrwxrwx 1 root root 28 Mar 26 08:56 h-test.xml -> 
/etc/libvirt/qemu/h-test.xml
root@b:~# virsh shutdown h-test
Domain h-test is being shutdown

root@b:~# reboot
root@b:~# [✗=129]─[paelzer@Keschdeichel ~]──[203538]──[09:57 Fr Mär 26]──
$ lxc exec b bash
root@b:~# virsh list
 IdName   State

 1 h-test running


root@f:~# virsh autostart h-test
Domain h-test marked as autostarted

root@f:~# ll /etc/libvirt/qemu/autostart/
total 2
drwxr-xr-x 2 root root  3 Mar 26 08:56 ./
drwxr-xr-x 4 root root  5 Mar 26 08:56 ../
lrwxrwxrwx 1 root root 28 Mar 26 08:56 h-test.xml -> 
/etc/libvirt/qemu/h-test.xml
root@f:~# virsh shutdown h-test
Domain h-test is being shutdown

root@f:~# reboot
root@f:~# [✗=129]─[paelzer@Keschdeichel ~]──[203673]──[09:57 Fr Mär 26]──
$ lxc exec f bash
root@f:~# virsh list
 Id   Name State

 1h-test   running



Now trying the rename ...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921325

Title:
  VM will not auto-start automatically when server is rebooted after
  virsh domrename

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

[Christian Ehrhardt ]

For qemu/kvm domains that comes down to the function
qemuDomainSetAutostart and that just creates a symlink.

So for example:
$ virsh autostart h-test1
Domain 'h-test1' marked as autostarted

Actually creates:
root@h:~# ll /etc/libvirt/qemu/autostart/
total 3
drwxr-xr-x 2 root root  3 Mar 26 08:24 ./
drwxr-xr-x 4 root root  6 Mar 26 08:24 ../
lrwxrwxrwx 1 root root 29 Mar 26 08:24 h-test1.xml -> 
/etc/libvirt/qemu/h-test1.xml


Now if after that I rename (which only works if it is inactive) it 
automatically also renames the symlink.

root@h:~# virsh domrename h-test1 h-test1-newname
error: Requested operation is not valid: cannot rename active domain

root@h:~# virsh shutdown h-test1
Domain 'h-test1' is being shutdown

root@h:~# virsh domrename h-test1 h-test1-newname
Domain successfully renamed

root@h:~# ll /etc/libvirt/qemu/autostart/
total 3
drwxr-xr-x 2 root root  3 Mar 26 08:32 ./
drwxr-xr-x 4 root root  6 Mar 26 08:32 ../
lrwxrwxrwx 1 root root 37 Mar 26 08:32 h-test1-newname.xml -> 
/etc/libvirt/qemu/h-test1-newname.xml

I've tested that with the latest libvirt in Ubuntu which is 7.0.0-2ubuntu1
Now chances are still that this was broken in the past ... let me try that as 
well

** Also affects: libvirt (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: libvirt (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: libvirt (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921325

Title:
  VM will not auto-start automatically when server is rebooted after
  virsh domrename

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs