Public bug reported:

Last night I started a reboot without manually shutting down a qemu/kvm
guest first.   After X went down a bunch of I/O errors associated with a
network block device that contains a NTFS filesystem showed up on the
console.   I noticed that the umount.target had been reached but the
virt-guest-shutdown.target was still waiting for the guest to shut down,
until it timed out.

Wouldn't it be beneficial for all guests to be shutdown before
unmounting all filesystems?

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: systemd 246.6-1ubuntu1.3
ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18
Uname: Linux 5.8.0-49-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Apr 15 08:35:48 2021
InstallationDate: Installed on 2021-01-17 (88 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: HP HP ZBook 15u G6
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic 
root=UUID=25df7fed-1baf-421e-941e-7f7c280db6e8 ro iommu=pt intel_iommu=on 
default_hugepagesz=1G hugepagesz=1G hugepages=6 pcie_aspm.policy=performance
SourcePackage: systemd
UpgradeStatus: Upgraded to groovy on 2021-04-08 (6 days ago)
dmi.bios.date: 01/08/2021
dmi.bios.release: 8.1
dmi.bios.vendor: HP
dmi.bios.version: R70 Ver. 01.08.01
dmi.board.name: 8549
dmi.board.vendor: HP
dmi.board.version: KBC Version 52.67.00
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 82.103
dmi.modalias: 
dmi:bvnHP:bvrR70Ver.01.08.01:bd01/08/2021:br8.1:efr82.103:svnHP:pnHPZBook15uG6:pvr:rvnHP:rn8549:rvrKBCVersion52.67.00:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ZBook
dmi.product.name: HP ZBook 15u G6
dmi.product.sku: 9AP56LP#ABA
dmi.sys.vendor: HP

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug groovy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1924494

Title:
  Systemd shutdown order unmounts filesystem used by qemu/kvm guest
  before shutting down the guest

Status in systemd package in Ubuntu:
  New

Bug description:
  Last night I started a reboot without manually shutting down a
  qemu/kvm guest first.   After X went down a bunch of I/O errors
  associated with a network block device that contains a NTFS filesystem
  showed up on the console.   I noticed that the umount.target had been
  reached but the virt-guest-shutdown.target was still waiting for the
  guest to shut down, until it timed out.

  Wouldn't it be beneficial for all guests to be shutdown before
  unmounting all filesystems?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: systemd 246.6-1ubuntu1.3
  ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Apr 15 08:35:48 2021
  InstallationDate: Installed on 2021-01-17 (88 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: HP HP ZBook 15u G6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic 
root=UUID=25df7fed-1baf-421e-941e-7f7c280db6e8 ro iommu=pt intel_iommu=on 
default_hugepagesz=1G hugepagesz=1G hugepages=6 pcie_aspm.policy=performance
  SourcePackage: systemd
  UpgradeStatus: Upgraded to groovy on 2021-04-08 (6 days ago)
  dmi.bios.date: 01/08/2021
  dmi.bios.release: 8.1
  dmi.bios.vendor: HP
  dmi.bios.version: R70 Ver. 01.08.01
  dmi.board.name: 8549
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 52.67.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 82.103
  dmi.modalias: 
dmi:bvnHP:bvrR70Ver.01.08.01:bd01/08/2021:br8.1:efr82.103:svnHP:pnHPZBook15uG6:pvr:rvnHP:rn8549:rvrKBCVersion52.67.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook 15u G6
  dmi.product.sku: 9AP56LP#ABA
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to