Comment 8 for bug 2051153

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Verification:

1. check old behavior. I did so twice with a sleep in between to show that it resets the unit and the time

root@j-vm:~# apt-cache policy qemu-block-extra; apt install -y --reinstall qemu-block-extra; systemctl status run-qemu.mount; ls -laF /run/qemu/
qemu-block-extra:
  Installed: 1:6.2+dfsg-2ubuntu6.16
  Candidate: 1:6.2+dfsg-2ubuntu6.16
  Version table:
 *** 1:6.2+dfsg-2ubuntu6.16 500
        500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
        100 /var/lib/dpkg/status
     1:6.2+dfsg-2ubuntu6 500
        500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 68.1 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 qemu-block-extra amd64 1:6.2+dfsg-2ubuntu6.16 [68.1 kB]
Fetched 68.1 kB in 0s (460 kB/s)
(Reading database ... 72988 files and directories currently installed.)
Preparing to unpack .../qemu-block-extra_1%3a6.2+dfsg-2ubuntu6.16_amd64.deb ...
Unpacking qemu-block-extra (1:6.2+dfsg-2ubuntu6.16) over (1:6.2+dfsg-2ubuntu6.16) ...
Setting up qemu-block-extra (1:6.2+dfsg-2ubuntu6.16) ...
Scanning processes...
Scanning linux images...

Running kernel seems to be up-to-date.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this host.
● run-qemu.mount - Prepare /run/qemu to allow still running qemu binaries of former builds (after package upgrades) to fallback-load modules from there
     Loaded: loaded (/proc/self/mountinfo; enabled; vendor preset: enabled)
     Active: active (mounted) since Mon 2024-02-05 10:39:27 UTC; 2s ago
      Where: /run/qemu
       What: tmpfs
      Tasks: 0 (limit: 1171)
     Memory: 8.0K
        CPU: 2ms
     CGroup: /system.slice/run-qemu.mount

Feb 05 10:39:27 j-vm systemd[1]: Mounting Prepare /run/qemu to allow still running qemu binaries of former builds (after package upgrades) to fallback-load modules from there...
Feb 05 10:39:27 j-vm systemd[1]: Mounted Prepare /run/qemu to allow still running qemu binaries of former builds (after package upgrades) to fallback-load modules from there.
total 0
drwxr-xr-x 2 root root 40 Feb 5 10:39 ./
drwxr-xr-x 29 root root 840 Feb 5 10:38 ../
root@j-vm:~#
root@j-vm:~# sleep 10s
root@j-vm:~# apt-cache policy qemu-block-extra; apt install -y --reinstall qemu-block-extra; systemctl status run-qemu.mount; ls -laF /run/qemu/
qemu-block-extra:
  Installed: 1:6.2+dfsg-2ubuntu6.16
  Candidate: 1:6.2+dfsg-2ubuntu6.16
  Version table:
 *** 1:6.2+dfsg-2ubuntu6.16 500
        500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
        100 /var/lib/dpkg/status
     1:6.2+dfsg-2ubuntu6 500
        500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 68.1 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 qemu-block-extra amd64 1:6.2+dfsg-2ubuntu6.16 [68.1 kB]
Fetched 68.1 kB in 0s (414 kB/s)
(Reading database ... 72988 files and directories currently installed.)
Preparing to unpack .../qemu-block-extra_1%3a6.2+dfsg-2ubuntu6.16_amd64.deb ...
Unpacking qemu-block-extra (1:6.2+dfsg-2ubuntu6.16) over (1:6.2+dfsg-2ubuntu6.16) ...
Setting up qemu-block-extra (1:6.2+dfsg-2ubuntu6.16) ...
Scanning processes...
Scanning linux images...

Running kernel seems to be up-to-date.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this host.
● run-qemu.mount - Prepare /run/qemu to allow still running qemu binaries of former builds (after package upgrades) to fallback-load modules from there
     Loaded: loaded (/proc/self/mountinfo; enabled; vendor preset: enabled)
     Active: active (mounted) since Mon 2024-02-05 10:40:29 UTC; 2s ago
      Where: /run/qemu
       What: tmpfs
      Tasks: 0 (limit: 1171)
     Memory: 8.0K
        CPU: 2ms
     CGroup: /system.slice/run-qemu.mount

Feb 05 10:40:29 j-vm systemd[1]: Mounting Prepare /run/qemu to allow still running qemu binaries of former builds (after package upgrades) to fallback-load modules from there...
Feb 05 10:40:29 j-vm systemd[1]: Mounted Prepare /run/qemu to allow still running qemu binaries of former builds (after package upgrades) to fallback-load modules from there.
total 0
drwxr-xr-x 2 root root 40 Feb 5 10:40 ./
drwxr-xr-x 29 root root 840 Feb 5 10:38 ../