* [PATCH v3] expand-on-first-boot: Ensure that /tmp is writable
@ 2024-07-25 14:17 'Clara Kowalsky' via isar-users
2024-07-31 6:46 ` Uladzimir Bely
2024-08-13 9:17 ` Uladzimir Bely
0 siblings, 2 replies; 11+ messages in thread
From: 'Clara Kowalsky' via isar-users @ 2024-07-25 14:17 UTC (permalink / raw)
To: isar-users; +Cc: quirin.gylstorff, Clara Kowalsky
By setting PrivateTmp, a new file system namespace is created for this
service and private /tmp/<service>/tmp and /var/tmp/<service>/tmp
subdirectories are mounted, which are only used for processes of this
namespace. The service unit receives a mount unit dependency for all
mounts required to access /tmp and /var/tmp.
This ensures that the /tmp directory is writable for the service, as
mktemp is used in expand-last-partition.sh and creates a temporary file.
Signed-off-by: Clara Kowalsky <clara.kowalsky@siemens.com>
---
.../expand-on-first-boot/files/expand-on-first-boot.service | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-support/expand-on-first-boot/files/expand-on-first-boot.service b/meta/recipes-support/expand-on-first-boot/files/expand-on-first-boot.service
index 90c92a39..8e76998b 100644
--- a/meta/recipes-support/expand-on-first-boot/files/expand-on-first-boot.service
+++ b/meta/recipes-support/expand-on-first-boot/files/expand-on-first-boot.service
@@ -16,6 +16,7 @@ Type=oneshot
ExecStart=/usr/share/expand-on-first-boot/expand-last-partition.sh
ExecStartPost=-/bin/systemctl disable expand-on-first-boot.service
ExecStopPost=-/bin/systemctl disable expand-on-first-boot.service
+PrivateTmp=true
[Install]
WantedBy=sysinit.target
--
2.45.2
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/20240725141729.1344298-1-clara.kowalsky%40siemens.com.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH v3] expand-on-first-boot: Ensure that /tmp is writable
2024-07-25 14:17 [PATCH v3] expand-on-first-boot: Ensure that /tmp is writable 'Clara Kowalsky' via isar-users
@ 2024-07-31 6:46 ` Uladzimir Bely
2024-08-13 9:17 ` Uladzimir Bely
1 sibling, 0 replies; 11+ messages in thread
From: Uladzimir Bely @ 2024-07-31 6:46 UTC (permalink / raw)
To: Clara Kowalsky, isar-users
On Thu, 2024-07-25 at 16:17 +0200, 'Clara Kowalsky' via isar-users
wrote:
> By setting PrivateTmp, a new file system namespace is created for
> this
> service and private /tmp/<service>/tmp and /var/tmp/<service>/tmp
> subdirectories are mounted, which are only used for processes of this
> namespace. The service unit receives a mount unit dependency for all
> mounts required to access /tmp and /var/tmp.
> This ensures that the /tmp directory is writable for the service, as
> mktemp is used in expand-last-partition.sh and creates a temporary
> file.
>
> Signed-off-by: Clara Kowalsky <clara.kowalsky@siemens.com>
> ---
> .../expand-on-first-boot/files/expand-on-first-boot.service | 1
> +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-support/expand-on-first-boot/files/expand-
> on-first-boot.service b/meta/recipes-support/expand-on-first-
> boot/files/expand-on-first-boot.service
> index 90c92a39..8e76998b 100644
> --- a/meta/recipes-support/expand-on-first-boot/files/expand-on-
> first-boot.service
> +++ b/meta/recipes-support/expand-on-first-boot/files/expand-on-
> first-boot.service
> @@ -16,6 +16,7 @@ Type=oneshot
> ExecStart=/usr/share/expand-on-first-boot/expand-last-partition.sh
> ExecStartPost=-/bin/systemctl disable expand-on-first-boot.service
> ExecStopPost=-/bin/systemctl disable expand-on-first-boot.service
> +PrivateTmp=true
>
> [Install]
> WantedBy=sysinit.target
> --
> 2.45.2
>
Applied to next, thanks.
--
Best regards,
Uladzimir.
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/e227148add94c87e5066242bc01b82c18a907a5a.camel%40ilbers.de.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH v3] expand-on-first-boot: Ensure that /tmp is writable
2024-07-25 14:17 [PATCH v3] expand-on-first-boot: Ensure that /tmp is writable 'Clara Kowalsky' via isar-users
2024-07-31 6:46 ` Uladzimir Bely
@ 2024-08-13 9:17 ` Uladzimir Bely
2024-08-13 9:24 ` 'MOESSBAUER, Felix' via isar-users
1 sibling, 1 reply; 11+ messages in thread
From: Uladzimir Bely @ 2024-08-13 9:17 UTC (permalink / raw)
To: Clara Kowalsky, isar-users
[-- Attachment #1: Type: text/plain, Size: 2869 bytes --]
On Thu, 2024-07-25 at 16:17 +0200, 'Clara Kowalsky' via isar-users
wrote:
> By setting PrivateTmp, a new file system namespace is created for
> this
> service and private /tmp/<service>/tmp and /var/tmp/<service>/tmp
> subdirectories are mounted, which are only used for processes of this
> namespace. The service unit receives a mount unit dependency for all
> mounts required to access /tmp and /var/tmp.
> This ensures that the /tmp directory is writable for the service, as
> mktemp is used in expand-last-partition.sh and creates a temporary
> file.
>
> Signed-off-by: Clara Kowalsky <clara.kowalsky@siemens.com>
> ---
> .../expand-on-first-boot/files/expand-on-first-boot.service | 1
> +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-support/expand-on-first-boot/files/expand-
> on-first-boot.service b/meta/recipes-support/expand-on-first-
> boot/files/expand-on-first-boot.service
> index 90c92a39..8e76998b 100644
> --- a/meta/recipes-support/expand-on-first-boot/files/expand-on-
> first-boot.service
> +++ b/meta/recipes-support/expand-on-first-boot/files/expand-on-
> first-boot.service
> @@ -16,6 +16,7 @@ Type=oneshot
> ExecStart=/usr/share/expand-on-first-boot/expand-last-partition.sh
> ExecStartPost=-/bin/systemctl disable expand-on-first-boot.service
> ExecStopPost=-/bin/systemctl disable expand-on-first-boot.service
> +PrivateTmp=true
>
> [Install]
> WantedBy=sysinit.target
> --
> 2.45.2
>
Hello all.
After few days having this patch merged we at least twice faced the
issue in CI with running qemuamd64 machine, probably related to the
applied patch.
Error message is "ERROR| No resize output while expected". E.g., there
is no btrfs resize output in VM boot log.
The reason of non-running expand-on-first-boot serivce is:
```
[ 5.578636] systemd[1]: local-fs-pre.target: Job expand-on-first-
boot.service/start deleted to break ordering cycle starting with local-
fs-pre.target/start
```
I'm currently debugging the issue, but for now I'll attach two logs
when the same image was run twice - with and without an error.
Maybe someone have some ideas about the issue.
Actually, in case expand-on-first-boot runs OK, there is another target
systemd disables:
```
[ 5.507289] systemd[1]: local-fs.target: Job local-fs-
pre.target/start deleted to break ordering cycle starting with local-
fs.target/start
```
--
Best regards,
Uladzimir.
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/b05e4a8c808ec3112bb4fc401c46f3995a883283.camel%40ilbers.de.
[-- Attachment #2: resize_ok.txt --]
[-- Type: text/plain, Size: 45112 bytes --]
EFI stub: Loaded initrd from command line option
[ 0.000000] Linux version 5.10.0-32-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.223-1 (2024-08-10)
[ 0.000000] Command line: initrd=\initrd.img-5.10.0-32-amd64 LABEL=Boot root=PARTUUID=8b8f5ee9-daaf-443f-b6b8-41bbd63d7784 rootwait console=ttyS0,115200 console=tty0
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000007fffff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000000800000-0x0000000000807fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x0000000000808000-0x000000000080afff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000080b000-0x000000000080bfff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x000000000080c000-0x000000000080ffff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000000810000-0x00000000008fffff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x0000000000900000-0x000000003eab6fff] usable
[ 0.000000] BIOS-e820: [mem 0x000000003eab7000-0x000000003eb77fff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000003eb78000-0x000000003f4ecfff] usable
[ 0.000000] BIOS-e820: [mem 0x000000003f4ed000-0x000000003f76cfff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000003f76d000-0x000000003f77efff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x000000003f77f000-0x000000003f7fefff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x000000003f7ff000-0x000000003ff57fff] usable
[ 0.000000] BIOS-e820: [mem 0x000000003ff58000-0x000000003ff77fff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000003ff78000-0x000000003fffffff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000b0000000-0x00000000bfffffff] reserved
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] extended physical RAM map:
[ 0.000000] reserve setup_data: [mem 0x0000000000000000-0x000000000009ffff] usable
[ 0.000000] reserve setup_data: [mem 0x0000000000100000-0x00000000007fffff] usable
[ 0.000000] reserve setup_data: [mem 0x0000000000800000-0x0000000000807fff] ACPI NVS
[ 0.000000] reserve setup_data: [mem 0x0000000000808000-0x000000000080afff] usable
[ 0.000000] reserve setup_data: [mem 0x000000000080b000-0x000000000080bfff] ACPI NVS
[ 0.000000] reserve setup_data: [mem 0x000000000080c000-0x000000000080ffff] usable
[ 0.000000] reserve setup_data: [mem 0x0000000000810000-0x00000000008fffff] ACPI NVS
[ 0.000000] reserve setup_data: [mem 0x0000000000900000-0x000000003c00c017] usable
[ 0.000000] reserve setup_data: [mem 0x000000003c00c018-0x000000003c049057] usable
[ 0.000000] reserve setup_data: [mem 0x000000003c049058-0x000000003c04a017] usable
[ 0.000000] reserve setup_data: [mem 0x000000003c04a018-0x000000003c053c57] usable
[ 0.000000] reserve setup_data: [mem 0x000000003c053c58-0x000000003eab6fff] usable
[ 0.000000] reserve setup_data: [mem 0x000000003eab7000-0x000000003eb77fff] reserved
[ 0.000000] reserve setup_data: [mem 0x000000003eb78000-0x000000003f4ecfff] usable
[ 0.000000] reserve setup_data: [mem 0x000000003f4ed000-0x000000003f76cfff] reserved
[ 0.000000] reserve setup_data: [mem 0x000000003f76d000-0x000000003f77efff] ACPI data
[ 0.000000] reserve setup_data: [mem 0x000000003f77f000-0x000000003f7fefff] ACPI NVS
[ 0.000000] reserve setup_data: [mem 0x000000003f7ff000-0x000000003ff57fff] usable
[ 0.000000] reserve setup_data: [mem 0x000000003ff58000-0x000000003ff77fff] reserved
[ 0.000000] reserve setup_data: [mem 0x000000003ff78000-0x000000003fffffff] ACPI NVS
[ 0.000000] reserve setup_data: [mem 0x00000000b0000000-0x00000000bfffffff] reserved
[ 0.000000] efi: EFI v2.70 by EDK II
[ 0.000000] efi: SMBIOS=0x3f518000 ACPI=0x3f77e000 ACPI 2.0=0x3f77e014 MEMATTR=0x3de90018
[ 0.000000] secureboot: Secure boot disabled
[ 0.000000] SMBIOS 2.8 present.
[ 0.000000] DMI: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015
[ 0.000000] tsc: Fast TSC calibration using PIT
[ 0.000000] tsc: Detected 3792.795 MHz processor
[ 0.001658] AGP: No AGP bridge found
[ 0.001781] last_pfn = 0x3ff58 max_arch_pfn = 0x400000000
[ 0.002542] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT
[ 0.024187] RAMDISK: [mem 0x3c054000-0x3dc1ffff]
[ 0.024420] ACPI: Early table checksum verification disabled
[ 0.024634] ACPI: RSDP 0x000000003F77E014 000024 (v02 BOCHS )
[ 0.024775] ACPI: XSDT 0x000000003F77D0E8 000054 (v01 BOCHS BXPC 00000001 01000013)
[ 0.025068] ACPI: FACP 0x000000003F779000 0000F4 (v03 BOCHS BXPC 00000001 BXPC 00000001)
[ 0.025393] ACPI: DSDT 0x000000003F77A000 002087 (v01 BOCHS BXPC 00000001 BXPC 00000001)
[ 0.025442] ACPI: FACS 0x000000003F7DD000 000040
[ 0.025474] ACPI: APIC 0x000000003F778000 000078 (v01 BOCHS BXPC 00000001 BXPC 00000001)
[ 0.025493] ACPI: HPET 0x000000003F777000 000038 (v01 BOCHS BXPC 00000001 BXPC 00000001)
[ 0.025510] ACPI: MCFG 0x000000003F776000 00003C (v01 BOCHS BXPC 00000001 BXPC 00000001)
[ 0.025527] ACPI: WAET 0x000000003F775000 000028 (v01 BOCHS BXPC 00000001 BXPC 00000001)
[ 0.025544] ACPI: BGRT 0x000000003F774000 000038 (v01 INTEL EDK2 00000002 01000013)
[ 0.025590] ACPI: Reserving FACP table memory at [mem 0x3f779000-0x3f7790f3]
[ 0.025605] ACPI: Reserving DSDT table memory at [mem 0x3f77a000-0x3f77c086]
[ 0.025612] ACPI: Reserving FACS table memory at [mem 0x3f7dd000-0x3f7dd03f]
[ 0.025617] ACPI: Reserving APIC table memory at [mem 0x3f778000-0x3f778077]
[ 0.025623] ACPI: Reserving HPET table memory at [mem 0x3f777000-0x3f777037]
[ 0.025628] ACPI: Reserving MCFG table memory at [mem 0x3f776000-0x3f77603b]
[ 0.025634] ACPI: Reserving WAET table memory at [mem 0x3f775000-0x3f775027]
[ 0.025639] ACPI: Reserving BGRT table memory at [mem 0x3f774000-0x3f774037]
[ 0.026907] No NUMA configuration found
[ 0.026923] Faking a node at [mem 0x0000000000000000-0x000000003ff57fff]
[ 0.027336] NODE_DATA(0) allocated [mem 0x3feb1000-0x3fedafff]
[ 0.029853] Zone ranges:
[ 0.029887] DMA [mem 0x0000000000001000-0x0000000000ffffff]
[ 0.029913] DMA32 [mem 0x0000000001000000-0x000000003ff57fff]
[ 0.029922] Normal empty
[ 0.029933] Device empty
[ 0.029943] Movable zone start for each node
[ 0.029965] Early memory node ranges
[ 0.029983] node 0: [mem 0x0000000000001000-0x000000000009ffff]
[ 0.030048] node 0: [mem 0x0000000000100000-0x00000000007fffff]
[ 0.030054] node 0: [mem 0x0000000000808000-0x000000000080afff]
[ 0.030059] node 0: [mem 0x000000000080c000-0x000000000080ffff]
[ 0.030064] node 0: [mem 0x0000000000900000-0x000000003eab6fff]
[ 0.030081] node 0: [mem 0x000000003eb78000-0x000000003f4ecfff]
[ 0.030087] node 0: [mem 0x000000003f7ff000-0x000000003ff57fff]
[ 0.030205] Initmem setup node 0 [mem 0x0000000000001000-0x000000003ff57fff]
[ 0.030687] On node 0, zone DMA: 1 pages in unavailable ranges
[ 0.030815] On node 0, zone DMA: 96 pages in unavailable ranges
[ 0.030824] On node 0, zone DMA: 8 pages in unavailable ranges
[ 0.030829] On node 0, zone DMA: 1 pages in unavailable ranges
[ 0.030907] On node 0, zone DMA: 240 pages in unavailable ranges
[ 0.032875] On node 0, zone DMA32: 193 pages in unavailable ranges
[ 0.032933] On node 0, zone DMA32: 786 pages in unavailable ranges
[ 0.032958] On node 0, zone DMA32: 168 pages in unavailable ranges
[ 0.033161] ACPI: PM-Timer IO Port: 0x608
[ 0.033413] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
[ 0.033624] IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
[ 0.033686] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.033824] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
[ 0.033841] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.033894] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
[ 0.033901] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
[ 0.034013] Using ACPI (MADT) for SMP configuration information
[ 0.034040] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[ 0.034622] smpboot: Allowing 1 CPUs, 0 hotplug CPUs
[ 0.035189] PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
[ 0.035214] PM: hibernation: Registered nosave memory: [mem 0x000a0000-0x000fffff]
[ 0.035223] PM: hibernation: Registered nosave memory: [mem 0x00800000-0x00807fff]
[ 0.035231] PM: hibernation: Registered nosave memory: [mem 0x0080b000-0x0080bfff]
[ 0.035239] PM: hibernation: Registered nosave memory: [mem 0x00810000-0x008fffff]
[ 0.035247] PM: hibernation: Registered nosave memory: [mem 0x3c00c000-0x3c00cfff]
[ 0.035255] PM: hibernation: Registered nosave memory: [mem 0x3c049000-0x3c049fff]
[ 0.035267] PM: hibernation: Registered nosave memory: [mem 0x3c04a000-0x3c04afff]
[ 0.035275] PM: hibernation: Registered nosave memory: [mem 0x3c053000-0x3c053fff]
[ 0.035286] PM: hibernation: Registered nosave memory: [mem 0x3dc61000-0x3dc69fff]
[ 0.035295] PM: hibernation: Registered nosave memory: [mem 0x3eab7000-0x3eb77fff]
[ 0.035303] PM: hibernation: Registered nosave memory: [mem 0x3f4ed000-0x3f76cfff]
[ 0.035308] PM: hibernation: Registered nosave memory: [mem 0x3f76d000-0x3f77efff]
[ 0.035313] PM: hibernation: Registered nosave memory: [mem 0x3f77f000-0x3f7fefff]
[ 0.035378] [mem 0x40000000-0xafffffff] available for PCI devices
[ 0.035403] Booting paravirtualized kernel on bare hardware
[ 0.035609] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
[ 0.041322] setup_percpu: NR_CPUS:8192 nr_cpumask_bits:1 nr_cpu_ids:1 nr_node_ids:1
[ 0.044580] percpu: Embedded 63 pages/cpu s221184 r8192 d28672 u2097152
[ 0.045682] Built 1 zonelists, mobility grouping on. Total pages: 254748
[ 0.045693] Policy zone: DMA32
[ 0.045782] Kernel command line: initrd=\initrd.img-5.10.0-32-amd64 LABEL=Boot root=PARTUUID=8b8f5ee9-daaf-443f-b6b8-41bbd63d7784 rootwait console=ttyS0,115200 console=tty0
[ 0.047584] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[ 0.048202] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
[ 0.049059] mem auto-init: stack:off, heap alloc:on, heap free:off
[ 0.049245] AGP: Checking aperture...
[ 0.049993] AGP: No AGP bridge found
[ 0.067839] Memory: 248124K/1042604K available (12295K kernel code, 2538K rwdata, 7632K rodata, 2676K init, 17700K bss, 140008K reserved, 0K cma-reserved)
[ 0.072356] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.073574] ftrace: allocating 36690 entries in 144 pages
[ 0.117782] ftrace: allocated 144 pages with 2 groups
[ 0.122201] rcu: Hierarchical RCU implementation.
[ 0.122220] rcu: RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=1.
[ 0.122270] Rude variant of Tasks RCU enabled.
[ 0.122275] Tracing variant of Tasks RCU enabled.
[ 0.122324] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[ 0.122344] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
[ 0.137439] NR_IRQS: 524544, nr_irqs: 256, preallocated irqs: 16
[ 0.143271] Console: colour dummy device 80x25
[ 0.144644] printk: console [tty0] enabled
[ 0.171594] printk: console [ttyS0] enabled
[ 0.172268] ACPI: Core revision 20200925
[ 0.174909] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604467 ns
[ 0.177169] APIC: Switch to symmetric I/O mode setup
[ 0.180402] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.199850] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x6d5783c9cee, max_idle_ns: 881590743177 ns
[ 0.200356] Calibrating delay loop (skipped), value calculated using timer frequency.. 7585.59 BogoMIPS (lpj=15171180)
[ 0.201849] process: using AMD E400 aware idle routine
[ 0.202131] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
[ 0.202317] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
[ 0.202641] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
[ 0.202950] Spectre V2 : Mitigation: Retpolines
[ 0.203075] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
[ 0.203300] Spectre V2 : Spectre v2 / SpectreRSB : Filling RSB on VMEXIT
[ 0.205272] x86/fpu: x87 FPU will use FXSAVE
[ 0.362406] Freeing SMP alternatives memory: 32K
[ 0.371296] pid_max: default: 32768 minimum: 301
[ 0.384852] LSM: Security Framework initializing
[ 0.385629] Yama: disabled by default; enable with sysctl kernel.yama.*
[ 0.387711] AppArmor: AppArmor initialized
[ 0.387867] TOMOYO Linux initialized
[ 0.388537] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes, linear)
[ 0.388812] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes, linear)
[ 0.510310] smpboot: CPU0: AMD QEMU Virtual CPU version 2.5+ (family: 0xf, model: 0x6b, stepping: 0x1)
[ 0.512225] Performance Events: PMU not available due to virtualization, using software events only.
[ 0.512432] rcu: Hierarchical SRCU implementation.
[ 0.514984] NMI watchdog: Perf NMI watchdog permanently disabled
[ 0.516073] smp: Bringing up secondary CPUs ...
[ 0.516272] smp: Brought up 1 node, 1 CPU
[ 0.516413] smpboot: Max logical packages: 1
[ 0.516572] smpboot: Total of 1 processors activated (7585.59 BogoMIPS)
[ 0.525579] node 0 deferred pages initialised in 8ms
[ 0.531822] devtmpfs: initialized
[ 0.533621] x86/mm: Memory block size: 128MB
[ 0.537090] PM: Registering ACPI NVS region [mem 0x00800000-0x00807fff] (32768 bytes)
[ 0.537572] PM: Registering ACPI NVS region [mem 0x0080b000-0x0080bfff] (4096 bytes)
[ 0.537794] PM: Registering ACPI NVS region [mem 0x00810000-0x008fffff] (983040 bytes)
[ 0.539082] PM: Registering ACPI NVS region [mem 0x3f77f000-0x3f7fefff] (524288 bytes)
[ 0.539861] PM: Registering ACPI NVS region [mem 0x3ff78000-0x3fffffff] (557056 bytes)
[ 0.541119] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[ 0.541556] futex hash table entries: 256 (order: 2, 16384 bytes, linear)
[ 0.543290] pinctrl core: initialized pinctrl subsystem
[ 0.549864] NET: Registered protocol family 16
[ 0.551587] DMA: preallocated 128 KiB GFP_KERNEL pool for atomic allocations
[ 0.551891] DMA: preallocated 128 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[ 0.552156] DMA: preallocated 128 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[ 0.552429] audit: initializing netlink subsys (disabled)
[ 0.556261] thermal_sys: Registered thermal governor 'fair_share'
[ 0.556277] thermal_sys: Registered thermal governor 'bang_bang'
[ 0.556464] thermal_sys: Registered thermal governor 'step_wise'
[ 0.556642] thermal_sys: Registered thermal governor 'user_space'
[ 0.556789] thermal_sys: Registered thermal governor 'power_allocator'
[ 0.557103] cpuidle: using governor ladder
[ 0.557434] cpuidle: using governor menu
[ 0.558189] ACPI: bus type PCI registered
[ 0.558373] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[ 0.559721] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xb0000000-0xbfffffff] (base 0xb0000000)
[ 0.560200] PCI: MMCONFIG at [mem 0xb0000000-0xbfffffff] reserved in E820
[ 0.560630] audit: type=2000 audit(1723539496.376:1): state=initialized audit_enabled=0 res=1
[ 0.561801] PCI: Using configuration type 1 for base access
[ 0.566822] Kprobes globally optimized
[ 0.568054] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[ 0.772219] ACPI: Added _OSI(Module Device)
[ 0.772363] ACPI: Added _OSI(Processor Device)
[ 0.772466] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.772570] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.772762] ACPI: Added _OSI(Linux-Dell-Video)
[ 0.772903] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[ 0.773046] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
[ 0.781937] ACPI: 1 ACPI AML tables successfully acquired and loaded
[ 0.789657] ACPI: Interpreter enabled
[ 0.790129] ACPI: (supports S0 S3 S4 S5)
[ 0.790270] ACPI: Using IOAPIC for interrupt routing
[ 0.790879] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.791772] ACPI: Enabled 2 GPEs in block 00 to 3F
[ 0.802527] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[ 0.802959] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3]
[ 0.803934] acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug LTR]
[ 0.804483] acpi PNP0A08:00: _OSC: OS now controls [SHPCHotplug PME AER PCIeCapability]
[ 0.806395] PCI host bridge to bus 0000:00
[ 0.806647] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window]
[ 0.806820] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window]
[ 0.806989] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
[ 0.807167] pci_bus 0000:00: root bus resource [mem 0x40000000-0xafffffff window]
[ 0.807349] pci_bus 0000:00: root bus resource [mem 0xc0000000-0xfebfffff window]
[ 0.807525] pci_bus 0000:00: root bus resource [mem 0x100000000-0x8ffffffff window]
[ 0.807801] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.808478] pci 0000:00:00.0: [8086:29c0] type 00 class 0x060000
[ 0.810300] pci 0000:00:01.0: [1234:1111] type 00 class 0x030000
[ 0.810985] pci 0000:00:01.0: reg 0x10: [mem 0xc0000000-0xc0ffffff pref]
[ 0.811871] pci 0000:00:01.0: reg 0x18: [mem 0xc1061000-0xc1061fff]
[ 0.813355] pci 0000:00:01.0: reg 0x30: [mem 0xffff0000-0xffffffff pref]
[ 0.813626] pci 0000:00:01.0: BAR 0: assigned to efifb
[ 0.814056] pci 0000:00:02.0: [8086:100e] type 00 class 0x020000
[ 0.814664] pci 0000:00:02.0: reg 0x10: [mem 0xc1040000-0xc105ffff]
[ 0.815264] pci 0000:00:02.0: reg 0x14: [io 0x6040-0x607f]
[ 0.817227] pci 0000:00:02.0: reg 0x30: [mem 0xfffc0000-0xffffffff pref]
[ 0.817679] pci 0000:00:1f.0: [8086:2918] type 00 class 0x060100
[ 0.818059] pci 0000:00:1f.0: quirk: [io 0x0600-0x067f] claimed by ICH6 ACPI/GPIO/TCO
[ 0.818644] pci 0000:00:1f.2: [8086:2922] type 00 class 0x010601
[ 0.821017] pci 0000:00:1f.2: reg 0x20: [io 0x6080-0x609f]
[ 0.821603] pci 0000:00:1f.2: reg 0x24: [mem 0xc1060000-0xc1060fff]
[ 0.822429] pci 0000:00:1f.3: [8086:2930] type 00 class 0x0c0500
[ 0.823635] pci 0000:00:1f.3: reg 0x20: [io 0x6000-0x603f]
[ 0.825891] ACPI: PCI Interrupt Link [LNKA] (IRQs 5 *10 11)
[ 0.826353] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11)
[ 0.826667] ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11)
[ 0.826997] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 10 *11)
[ 0.827316] ACPI: PCI Interrupt Link [LNKE] (IRQs 5 *10 11)
[ 0.827632] ACPI: PCI Interrupt Link [LNKF] (IRQs 5 *10 11)
[ 0.828399] ACPI: PCI Interrupt Link [LNKG] (IRQs 5 10 *11)
[ 0.828719] ACPI: PCI Interrupt Link [LNKH] (IRQs 5 10 *11)
[ 0.828948] ACPI: PCI Interrupt Link [GSIA] (IRQs *16)
[ 0.829110] ACPI: PCI Interrupt Link [GSIB] (IRQs *17)
[ 0.829259] ACPI: PCI Interrupt Link [GSIC] (IRQs *18)
[ 0.829434] ACPI: PCI Interrupt Link [GSID] (IRQs *19)
[ 0.829638] ACPI: PCI Interrupt Link [GSIE] (IRQs *20)
[ 0.829819] ACPI: PCI Interrupt Link [GSIF] (IRQs *21)
[ 0.830008] ACPI: PCI Interrupt Link [GSIG] (IRQs *22)
[ 0.830183] ACPI: PCI Interrupt Link [GSIH] (IRQs *23)
[ 0.831631] iommu: Default domain type: Translated
[ 0.833410] pci 0000:00:01.0: vgaarb: setting as boot VGA device
[ 0.833634] pci 0000:00:01.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
[ 0.833894] pci 0000:00:01.0: vgaarb: bridge control possible
[ 0.834106] vgaarb: loaded
[ 0.834772] EDAC MC: Ver: 3.0.0
[ 0.835455] Registered efivars operations
[ 0.841020] NetLabel: Initializing
[ 0.841139] NetLabel: domain hash size = 128
[ 0.841272] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO
[ 0.841806] NetLabel: unlabeled traffic allowed by default
[ 0.841968] PCI: Using ACPI for IRQ routing
[ 0.843863] hpet: 3 channels of 0 reserved for per-cpu timers
[ 0.844156] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[ 0.844245] hpet0: 3 comparators, 64-bit 100.000000 MHz counter
[ 0.847917] clocksource: Switched to clocksource tsc-early
[ 0.877247] VFS: Disk quotas dquot_6.6.0
[ 0.877491] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 0.879633] AppArmor: AppArmor Filesystem Enabled
[ 0.880041] pnp: PnP ACPI init
[ 0.881799] system 00:05: [mem 0xb0000000-0xbfffffff window] has been reserved
[ 0.882603] pnp: PnP ACPI: found 6 devices
[ 0.892435] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[ 0.893144] NET: Registered protocol family 2
[ 0.893714] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear)
[ 0.898784] tcp_listen_portaddr_hash hash table entries: 512 (order: 1, 8192 bytes, linear)
[ 0.899181] TCP established hash table entries: 8192 (order: 4, 65536 bytes, linear)
[ 0.899522] TCP bind hash table entries: 8192 (order: 5, 131072 bytes, linear)
[ 0.899802] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.900434] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
[ 0.900725] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
[ 0.901516] NET: Registered protocol family 1
[ 0.901889] NET: Registered protocol family 44
[ 0.902082] pci 0000:00:01.0: can't claim BAR 6 [mem 0xffff0000-0xffffffff pref]: no compatible bridge window
[ 0.902370] pci 0000:00:02.0: can't claim BAR 6 [mem 0xfffc0000-0xffffffff pref]: no compatible bridge window
[ 0.903222] pci 0000:00:02.0: BAR 6: assigned [mem 0x40000000-0x4003ffff pref]
[ 0.903530] pci 0000:00:01.0: BAR 6: assigned [mem 0x40040000-0x4004ffff pref]
[ 0.903840] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window]
[ 0.904019] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff window]
[ 0.904202] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
[ 0.904392] pci_bus 0000:00: resource 7 [mem 0x40000000-0xafffffff window]
[ 0.904604] pci_bus 0000:00: resource 8 [mem 0xc0000000-0xfebfffff window]
[ 0.904778] pci_bus 0000:00: resource 9 [mem 0x100000000-0x8ffffffff window]
[ 0.905350] pci 0000:00:01.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
[ 0.905655] PCI: CLS 0 bytes, default 64
[ 0.907546] Trying to unpack rootfs image as initramfs...
[ 1.564931] Freeing initrd memory: 28464K
[ 1.567592] Initialise system trusted keyrings
[ 1.568538] Key type blacklist registered
[ 1.569076] workingset: timestamp_bits=36 max_order=18 bucket_order=0
[ 1.573175] zbud: loaded
[ 1.575259] integrity: Platform Keyring initialized
[ 1.575421] Key type asymmetric registered
[ 1.575558] Asymmetric key parser 'x509' registered
[ 1.575796] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[ 1.576332] io scheduler mq-deadline registered
[ 1.578367] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 1.578705] efifb: probing for efifb
[ 1.579104] efifb: framebuffer at 0xc0000000, using 4000k, total 4000k
[ 1.579309] efifb: mode is 1280x800x32, linelength=5120, pages=1
[ 1.579473] efifb: scrolling: redraw
[ 1.579608] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 1.586964] Console: switching to colour frame buffer device 160x50
[ 1.591348] fb0: EFI VGA frame buffer device
[ 1.593092] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 1.596979] 00:03: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
[ 1.599683] Linux agpgart interface v0.103
[ 1.600511] AMD-Vi: AMD IOMMUv2 functionality not available on this system - This is not a bug.
[ 1.602211] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
[ 1.603859] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 1.604151] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 1.605075] mousedev: PS/2 mouse device common for all mice
[ 1.606827] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
[ 1.608583] rtc_cmos 00:04: RTC can wake from S4
[ 1.610120] rtc_cmos 00:04: registered as rtc0
[ 1.610557] rtc_cmos 00:04: setting system clock to 2024-08-13T08:58:18 UTC (1723539498)
[ 1.611402] rtc_cmos 00:04: alarms up to one day, y3k, 242 bytes nvram, hpet irqs
[ 1.611869] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.613084] NET: Registered protocol family 10
[ 1.708924] Segment Routing with IPv6
[ 1.709323] mip6: Mobile IPv6
[ 1.709502] NET: Registered protocol family 17
[ 1.709897] mpls_gso: MPLS GSO support
[ 1.710961] IPI shorthand broadcast: enabled
[ 1.711336] sched_clock: Marking stable (1676037696, 34829644)->(1716015285, -5147945)
[ 1.712371] registered taskstats version 1
[ 1.712585] Loading compiled-in X.509 certificates
[ 1.754927] Loaded X.509 cert 'Debian Secure Boot CA: 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1'
[ 1.757147] Loaded X.509 cert 'Debian Secure Boot Signer 2022 - linux: 14011249c2675ea8e5148542202005810584b25f'
[ 1.759390] zswap: loaded using pool lzo/zbud
[ 1.761767] Key type .fscrypt registered
[ 1.763460] Key type fscrypt-provisioning registered
[ 1.765634] AppArmor: AppArmor sha1 policy hashing enabled
[ 1.768754] clk: Disabling unused clocks
[ 1.777033] Freeing unused decrypted memory: 2036K
[ 1.819647] Freeing unused kernel image (initmem) memory: 2676K
[ 1.821459] Write protecting the kernel read-only data: 22528k
[ 1.824265] Freeing unused kernel image (text/rodata gap) memory: 2040K
[ 1.826213] Freeing unused kernel image (rodata/data gap) memory: 560K
[ 1.909702] x86/mm: Checked W+X mappings: passed, no W+X pages found.
[ 1.911409] Run /init as init process
[ 2.341996] lpc_ich 0000:00:1f.0: I/O space for GPIO uninitialized
[ 2.351230] PCI Interrupt Link [GSIA] enabled at IRQ 16
[ 2.354040] i801_smbus 0000:00:1f.3: Enabling SMBus device
[ 2.362795] e1000: Intel(R) PRO/1000 Network Driver
[ 2.364470] e1000: Copyright (c) 1999-2006 Intel Corporation.
[ 2.383829] SCSI subsystem initialized
[ 2.392909] PCI Interrupt Link [GSIG] enabled at IRQ 22
[ 2.395077] i801_smbus 0000:00:1f.3: SMBus using PCI interrupt
[ 2.397692] i2c i2c-0: 1/1 memory slots populated (from DMI)
[ 2.399319] i2c i2c-0: Memory type 0x07 not supported yet, not instantiating SPD
[ 2.537234] ahci 0000:00:1f.2: AHCI 0001.0000 32 slots 6 ports 1.5 Gbps 0x3f impl SATA mode
[ 2.539148] ahci 0000:00:1f.2: flags: 64bit ncq only
[ 2.568084] scsi host0: ahci
[ 2.579098] tsc: Refined TSC clocksource calibration: 3792.775 MHz
[ 2.580923] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x6d575dd7e6b, max_idle_ns: 881591001401 ns
[ 2.583106] clocksource: Switched to clocksource tsc
[ 2.584854] scsi host1: ahci
[ 2.587997] scsi host2: ahci
[ 2.598044] scsi host3: ahci
[ 2.607974] scsi host4: ahci
[ 2.614264] scsi host5: ahci
[ 2.617286] ata1: SATA max UDMA/133 abar m4096@0xc1060000 port 0xc1060100 irq 24
[ 2.619005] ata2: SATA max UDMA/133 abar m4096@0xc1060000 port 0xc1060180 irq 24
[ 2.620535] ata3: SATA max UDMA/133 abar m4096@0xc1060000 port 0xc1060200 irq 24
[ 2.622055] ata4: SATA max UDMA/133 abar m4096@0xc1060000 port 0xc1060280 irq 24
[ 2.623563] ata5: SATA max UDMA/133 abar m4096@0xc1060000 port 0xc1060300 irq 24
[ 2.625035] ata6: SATA max UDMA/133 abar m4096@0xc1060000 port 0xc1060380 irq 24
[ 2.846092] e1000 0000:00:02.0 eth0: (PCI:33MHz:32-bit) 52:54:00:12:34:56
[ 2.847751] e1000 0000:00:02.0 eth0: Intel(R) PRO/1000 Network Connection
[ 2.946067] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 2.948617] ata2: SATA link down (SStatus 0 SControl 300)
[ 2.950340] ata5: SATA link down (SStatus 0 SControl 300)
[ 2.951752] ata6: SATA link down (SStatus 0 SControl 300)
[ 2.953131] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 2.955006] ata3.00: ATAPI: QEMU DVD-ROM, 2.5+, max UDMA/100
[ 2.956394] ata3.00: applying bridge limits
[ 2.957992] ata4: SATA link down (SStatus 0 SControl 300)
[ 2.959593] ata1.00: ATA-7: QEMU HARDDISK, 2.5+, max UDMA/100
[ 2.960967] ata1.00: 3196962 sectors, multi 16: LBA48 NCQ (depth 32)
[ 2.962357] ata1.00: applying bridge limits
[ 2.963956] ata3.00: configured for UDMA/100
[ 2.965827] ata1.00: configured for UDMA/100
[ 2.971700] scsi 0:0:0:0: Direct-Access ATA QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5
[ 2.976312] scsi 2:0:0:0: CD-ROM QEMU QEMU DVD-ROM 2.5+ PQ: 0 ANSI: 5
[ 3.013190] e1000 0000:00:02.0 enp0s2: renamed from eth0
[ 3.036674] sr 2:0:0:0: [sr0] scsi3-mmc drive: 4x/4x cd/rw xa/form2 tray
[ 3.038223] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 3.043983] sd 0:0:0:0: [sda] 3196962 512-byte logical blocks: (1.64 GB/1.52 GiB)
[ 3.045837] sd 0:0:0:0: [sda] Write Protect is off
[ 3.047479] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 3.057374] sda: sda1 sda2
[ 3.075396] sd 0:0:0:0: [sda] Attached SCSI disk
[ 3.231495] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input2
[ 3.398892] raid6: sse2x4 gen() 2133 MB/s
[ 3.466881] raid6: sse2x4 xor() 1367 MB/s
[ 3.534887] raid6: sse2x2 gen() 1756 MB/s
[ 3.602874] raid6: sse2x2 xor() 1136 MB/s
[ 3.670879] raid6: sse2x1 gen() 1786 MB/s
[ 3.738874] raid6: sse2x1 xor() 790 MB/s
[ 3.740121] raid6: using algorithm sse2x4 gen() 2133 MB/s
[ 3.741398] raid6: .... xor() 1367 MB/s, rmw enabled
[ 3.742681] raid6: using intx1 recovery algorithm
[ 3.746622] xor: measuring software checksum speed
[ 3.754110] prefetch64-sse : 1680 MB/sec
[ 3.761363] generic_sse : 1672 MB/sec
[ 3.762609] xor: using function: prefetch64-sse (1680 MB/sec)
[ 3.883217] Btrfs loaded, crc32c=crc32c-generic
[ 3.998450] BTRFS: device label platform devid 1 transid 6 /dev/sda2 scanned by btrfs (133)
[ 4.072180] BTRFS info (device sda2): using crc32c (crc32c-generic) checksum algorithm
[ 4.074048] BTRFS info (device sda2): flagging fs with big metadata feature
[ 4.075662] BTRFS info (device sda2): disk space caching is enabled
[ 4.077180] BTRFS info (device sda2): has skinny extents
[ 4.214175] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist.
[ 4.336265] systemd[1]: Inserted module 'autofs4'
[ 4.408754] systemd[1]: systemd 247.3-7+deb11u5 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified)
[ 4.413483] systemd[1]: Detected virtualization qemu.
[ 4.415309] systemd[1]: Detected architecture x86-64.
[ 4.417086] systemd[1]: Detected first boot.
[ 4.425935] systemd[1]: Set hostname to <isar>.
[ 4.428501] random: systemd: uninitialized urandom read (16 bytes read)
[ 4.430264] systemd[1]: Initializing machine ID from random generator.
[ 5.290784] systemd[1]: Invalid unit wpa_supplicant-nl80211@.service symlink multi-user.target.wants/wpa_supplicant-nl80211@.service.
[ 5.295522] systemd[1]: Invalid unit wpa_supplicant@.service symlink multi-user.target.wants/wpa_supplicant@.service.
[ 5.298307] systemd[1]: Invalid unit wpa_supplicant-wired@.service symlink multi-user.target.wants/wpa_supplicant-wired@.service.
[ 5.301110] systemd[1]: Failed to populate /etc with preset unit settings, ignoring: Read-only file system
[ 5.499978] systemd[1]: local-fs.target: Found ordering cycle on local-fs-pre.target/start
[ 5.501907] systemd[1]: local-fs.target: Found dependency on expand-on-first-boot.service/start
[ 5.503728] systemd[1]: local-fs.target: Found dependency on systemd-tmpfiles-setup.service/start
[ 5.505516] systemd[1]: local-fs.target: Found dependency on local-fs.target/start
[ 5.507289] systemd[1]: local-fs.target: Job local-fs-pre.target/start deleted to break ordering cycle starting with local-fs.target/start
[ 5.513068] systemd[1]: Queued start job for default target Graphical Interface.
[ 5.517723] random: systemd: uninitialized urandom read (16 bytes read)
[ 5.528737] systemd[1]: Created slice system-getty.slice.
[ 5.532792] random: systemd: uninitialized urandom read (16 bytes read)
[ 5.535421] systemd[1]: Created slice system-modprobe.slice.
[ 5.539106] random: systemd: uninitialized urandom read (16 bytes read)
[ 5.541777] systemd[1]: Created slice system-serial\x2dgetty.slice.
[ 5.546256] systemd[1]: Created slice User and Session Slice.
[ 5.551303] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[ 5.555535] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ 5.561251] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ 5.565858] systemd[1]: Reached target Local Encrypted Volumes.
[ 5.570006] systemd[1]: Reached target Paths.
[ 5.574000] systemd[1]: Reached target Remote File Systems.
[ 5.578045] systemd[1]: Reached target Slices.
[ 5.582146] systemd[1]: Reached target Swap.
[ 5.587049] systemd[1]: Listening on initctl Compatibility Named Pipe.
[ 5.592741] systemd[1]: Listening on Journal Audit Socket.
[ 5.597244] systemd[1]: Listening on Journal Socket (/dev/log).
[ 5.601578] systemd[1]: Listening on Journal Socket.
[ 5.606411] systemd[1]: Listening on udev Control Socket.
[ 5.610662] systemd[1]: Listening on udev Kernel Socket.
[ 5.619468] systemd[1]: Mounting Huge Pages File System...
[ 5.632970] systemd[1]: Mounting POSIX Message Queue File System...
[ 5.655107] systemd[1]: Mounting Kernel Debug File System...
[ 5.685927] systemd[1]: Mounting Kernel Trace File System...
[ 5.727748] systemd[1]: Starting Create list of static device nodes for the current kernel...
[ 5.759344] systemd[1]: Starting Load Kernel Module configfs...
[ 5.787420] systemd[1]: Starting Load Kernel Module drm...
[ 5.811825] systemd[1]: Starting Load Kernel Module fuse...
[ 5.831479] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
[ 5.887182] systemd[1]: Starting Journal Service...
[ 5.925261] systemd[1]: Starting Load Kernel Modules...
[ 5.941023] fuse: init (API version 7.32)
[ 5.959849] systemd[1]: Starting Remount Root and Kernel File Systems...
[ 5.999806] systemd[1]: Starting Coldplug All udev Devices...
[ 6.016055] ACPI: bus type drm_connector registered
[ 6.079291] systemd[1]: Mounted Huge Pages File System.
[ 6.099923] systemd[1]: Mounted POSIX Message Queue File System.
[ 6.129423] systemd[1]: Mounted Kernel Debug File System.
[ 6.138470] example_module: loading out-of-tree module taints kernel.
[ 6.154963] example_module: module verification failed: signature and/or required key missing - tainting kernel
[ 6.157225] Just an example
[ 6.171604] systemd[1]: Mounted Kernel Trace File System.
[ 6.235207] systemd[1]: Finished Create list of static device nodes for the current kernel.
[ 6.278219] systemd[1]: modprobe@configfs.service: Succeeded.
[ 6.328127] systemd[1]: Finished Load Kernel Module configfs.
[ 6.349048] BTRFS info (device sda2): disk space caching is enabled
[ 6.395431] systemd[1]: modprobe@drm.service: Succeeded.
[ 6.403462] systemd[1]: Finished Load Kernel Module drm.
[ 6.412293] systemd[1]: modprobe@fuse.service: Succeeded.
[ 6.419277] systemd[1]: Finished Load Kernel Module fuse.
[ 6.428392] systemd[1]: Finished Load Kernel Modules.
[ 6.437464] systemd[1]: Finished Remount Root and Kernel File Systems.
[ 6.456686] systemd[1]: Mounting FUSE Control File System...
[ 6.491178] systemd[1]: Mounting Kernel Configuration File System...
[ 6.515409] systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
[ 6.517572] systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped.
[ 6.539086] random: systemd: uninitialized urandom read (16 bytes read)
[ 6.559428] systemd[1]: Starting Load/Save Random Seed...
[ 6.583576] random: systemd: uninitialized urandom read (16 bytes read)
[ 6.604306] systemd[1]: Starting Apply Kernel Variables...
[ 6.623289] random: systemd: uninitialized urandom read (16 bytes read)
[ 6.651578] systemd[1]: Starting Create System Users...
[ 6.686034] systemd[1]: Mounted FUSE Control File System.
[ 6.714741] systemd[1]: Mounted Kernel Configuration File System.
[ 6.804659] systemd[1]: Finished Apply Kernel Variables.
[ 6.824442] systemd[1]: Started Journal Service.
[ 6.999330] systemd-journald[196]: Received client request to flush runtime journal.
[ 7.005261] systemd-journald[196]: Creating journal file /var/log/journal/c0c67c6efadd45f8b08509a61a6decd1/system.journal on a btrfs file system, and copy-on-write is enabled. This is likely to slow down journal access substantially, please consider turning off the copy-on-write file attribute on the journal directory, using chattr +C.
[ 7.307852] random: crng init done
[ 7.309731] random: 55 urandom warning(s) missed due to ratelimiting
[ 9.052291] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
[ 9.102289] ACPI: Power Button [PWRF]
[ 9.157492] parport_pc 00:02: reported by Plug and Play ACPI
[ 9.187489] iTCO_vendor_support: vendor-support=0
[ 9.209816] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
[ 9.238497] pstore: Using crash dump compression: deflate
[ 9.261848] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 9.266083] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[ 9.268664] pstore: Registered efi as persistent store backend
[ 9.271930] input: PC Speaker as /devices/platform/pcspkr/input/input4
[ 9.274122] sr 2:0:0:0: Attached scsi generic sg1 type 5
[ 9.283213] iTCO_wdt: Found a ICH9 TCO device (Version=2, TCOBASE=0x0660)
[ 9.339538] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[ 9.627958] fb0: switching to bochsdrmfb from EFI VGA
[ 9.669500] Console: switching to colour dummy device 80x25
[ 9.670131] bochs-drm 0000:00:01.0: vgaarb: deactivate vga console
[ 9.683692] [drm] Found bochs VGA, ID 0xb0c5.
[ 9.683855] [drm] Framebuffer size 16384 kB @ 0xc0000000, mmio @ 0xc1061000.
[ 9.697980] [TTM] Zone kernel: Available graphics memory: 490952 KiB
[ 9.698201] [TTM] Initializing pool allocator
[ 9.698409] [TTM] Initializing DMA pool allocator
[ 9.700853] [drm] Found EDID data blob.
[ 9.751396] [drm] Initialized bochs-drm 1.0.0 20130925 for 0000:00:01.0 on minor 0
[ 9.840195] fbcon: bochs-drmdrmfb (fb0) is primary device
[ 9.870405] Console: switching to colour frame buffer device 160x50
[ 9.947349] bochs-drm 0000:00:01.0: [drm] fb0: bochs-drmdrmfb frame buffer device
[ 10.011008] ppdev: user-space parallel port driver
[ 10.147773] kvm: Nested Virtualization enabled
[ 10.148104] SVM: kvm: Nested Paging disabled
[ 10.165845] powernow_k8: Power state transitions not supported
[ 12.598993] e1000: enp0s2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[ 12.602576] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s2: link becomes ready
[ 12.897909] BTRFS info (device sda2): resize device /dev/sda2 (devid 1) from 1313865728 to 1582301184
Debian GNU/Linux 11 isar ttyS0
isar login: root
Password:
Linux isar 5.10.0-32-amd64 #1 SMP Debian 5.10.223-1 (2024-08-10) x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
root@isar:~# journalctl -u expand-on-first-boot | cat
-- Journal begins at Tue 2024-08-13 08:58:23 UTC, ends at Tue 2024-08-13 09:00:54 UTC. --
Aug 13 08:58:27 isar systemd[1]: Starting Expand last partition...
Aug 13 08:58:28 isar expand-last-partition.sh[287]: 1+0 records in
Aug 13 08:58:28 isar expand-last-partition.sh[287]: 1+0 records out
Aug 13 08:58:28 isar expand-last-partition.sh[287]: 512 bytes copied, 0.0279161 s, 18.3 kB/s
Aug 13 08:58:28 isar expand-last-partition.sh[299]: Checking that no-one is using this disk right now ... FAILED
Aug 13 08:58:28 isar expand-last-partition.sh[299]: This disk is currently in use - repartitioning is probably a bad idea.
Aug 13 08:58:28 isar expand-last-partition.sh[299]: Umount all file systems, and swapoff all swap partitions on this disk.
Aug 13 08:58:28 isar expand-last-partition.sh[299]: Use the --no-reread flag to suppress this check.
Aug 13 08:58:28 isar expand-last-partition.sh[299]: Disk /dev/sda: 1.52 GiB, 1636844544 bytes, 3196962 sectors
Aug 13 08:58:28 isar expand-last-partition.sh[299]: Disk model: QEMU HARDDISK
Aug 13 08:58:28 isar expand-last-partition.sh[299]: Units: sectors of 1 * 512 = 512 bytes
Aug 13 08:58:28 isar expand-last-partition.sh[299]: Sector size (logical/physical): 512 bytes / 512 bytes
Aug 13 08:58:28 isar expand-last-partition.sh[299]: I/O size (minimum/optimal): 512 bytes / 512 bytes
Aug 13 08:58:28 isar expand-last-partition.sh[299]: Disklabel type: gpt
Aug 13 08:58:28 isar expand-last-partition.sh[299]: Disk identifier: 00000000-0000-0000-0000-000065E5E543
Aug 13 08:58:28 isar expand-last-partition.sh[299]: Old situation:
Aug 13 08:58:28 isar expand-last-partition.sh[299]: Device Start End Sectors Size Type
Aug 13 08:58:28 isar expand-last-partition.sh[299]: /dev/sda1 2048 106241 104194 50.9M EFI System
Aug 13 08:58:28 isar expand-last-partition.sh[299]: /dev/sda2 106496 2672639 2566144 1.2G Linux filesystem
Aug 13 08:58:28 isar expand-last-partition.sh[299]: >>> Script header accepted.
Aug 13 08:58:28 isar expand-last-partition.sh[299]: >>> Script header accepted.
Aug 13 08:58:28 isar expand-last-partition.sh[299]: >>> Script header accepted.
Aug 13 08:58:28 isar expand-last-partition.sh[299]: >>> Script header accepted.
Aug 13 08:58:28 isar expand-last-partition.sh[299]: >>> Script header accepted.
Aug 13 08:58:28 isar expand-last-partition.sh[299]: >>> Script header accepted.
Aug 13 08:58:28 isar expand-last-partition.sh[299]: >>> Created a new GPT disklabel (GUID: 00000000-0000-0000-0000-000065E5E543).
Aug 13 08:58:28 isar expand-last-partition.sh[299]: /dev/sda1: Created a new partition 1 of type 'EFI System' and of size 50.9 MiB.
Aug 13 08:58:28 isar expand-last-partition.sh[299]: Partition #1 contains a vfat signature.
Aug 13 08:58:28 isar expand-last-partition.sh[299]: /dev/sda2: Created a new partition 2 of type 'Linux filesystem' and of size 1.5 GiB.
Aug 13 08:58:28 isar expand-last-partition.sh[299]: Partition #2 contains a btrfs signature.
Aug 13 08:58:29 isar expand-last-partition.sh[299]: /dev/sda3: Done.
Aug 13 08:58:29 isar expand-last-partition.sh[299]: New situation:
Aug 13 08:58:29 isar expand-last-partition.sh[299]: Disklabel type: gpt
Aug 13 08:58:29 isar expand-last-partition.sh[299]: Disk identifier: 00000000-0000-0000-0000-000065E5E543
Aug 13 08:58:29 isar expand-last-partition.sh[299]: Device Start End Sectors Size Type
Aug 13 08:58:29 isar expand-last-partition.sh[299]: /dev/sda1 2048 106241 104194 50.9M EFI System
Aug 13 08:58:29 isar expand-last-partition.sh[299]: /dev/sda2 106496 3196928 3090433 1.5G Linux filesystem
Aug 13 08:58:29 isar expand-last-partition.sh[299]: The partition table has been altered.
Aug 13 08:58:29 isar expand-last-partition.sh[299]: Calling ioctl() to re-read partition table.
Aug 13 08:58:29 isar expand-last-partition.sh[299]: Re-reading the partition table failed.: Device or resource busy
Aug 13 08:58:29 isar expand-last-partition.sh[299]: The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or partx(8).
Aug 13 08:58:29 isar expand-last-partition.sh[299]: Syncing disks.
Aug 13 08:58:29 isar expand-last-partition.sh[305]: 1+0 records in
Aug 13 08:58:29 isar expand-last-partition.sh[305]: 1+0 records out
Aug 13 08:58:29 isar expand-last-partition.sh[305]: 512 bytes copied, 0.00838725 s, 61.0 kB/s
Aug 13 08:58:29 isar expand-last-partition.sh[318]: Resize '/tmp/expand-last-partition.sh.i37yhlzOqG' of 'max'
Aug 13 08:58:29 isar systemctl[321]: Removed /etc/systemd/system/sysinit.target.wants/expand-on-first-boot.service.
Aug 13 08:58:32 isar systemd[1]: expand-on-first-boot.service: Succeeded.
Aug 13 08:58:32 isar systemd[1]: Finished Expand last partition.
root@isar:~#
[-- Attachment #3: resize_no.txt --]
[-- Type: text/plain, Size: 40514 bytes --]
EFI stub: Loaded initrd from command line option
[ 0.000000] Linux version 5.10.0-32-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.223-1 (2024-08-10)
[ 0.000000] Command line: initrd=\initrd.img-5.10.0-32-amd64 LABEL=Boot root=PARTUUID=8b8f5ee9-daaf-443f-b6b8-41bbd63d7784 rootwait console=ttyS0,115200 console=tty0
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000007fffff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000000800000-0x0000000000807fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x0000000000808000-0x000000000080afff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000080b000-0x000000000080bfff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x000000000080c000-0x000000000080ffff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000000810000-0x00000000008fffff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x0000000000900000-0x000000003eab6fff] usable
[ 0.000000] BIOS-e820: [mem 0x000000003eab7000-0x000000003eb77fff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000003eb78000-0x000000003f4ecfff] usable
[ 0.000000] BIOS-e820: [mem 0x000000003f4ed000-0x000000003f76cfff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000003f76d000-0x000000003f77efff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x000000003f77f000-0x000000003f7fefff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x000000003f7ff000-0x000000003ff57fff] usable
[ 0.000000] BIOS-e820: [mem 0x000000003ff58000-0x000000003ff77fff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000003ff78000-0x000000003fffffff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000b0000000-0x00000000bfffffff] reserved
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] extended physical RAM map:
[ 0.000000] reserve setup_data: [mem 0x0000000000000000-0x000000000009ffff] usable
[ 0.000000] reserve setup_data: [mem 0x0000000000100000-0x00000000007fffff] usable
[ 0.000000] reserve setup_data: [mem 0x0000000000800000-0x0000000000807fff] ACPI NVS
[ 0.000000] reserve setup_data: [mem 0x0000000000808000-0x000000000080afff] usable
[ 0.000000] reserve setup_data: [mem 0x000000000080b000-0x000000000080bfff] ACPI NVS
[ 0.000000] reserve setup_data: [mem 0x000000000080c000-0x000000000080ffff] usable
[ 0.000000] reserve setup_data: [mem 0x0000000000810000-0x00000000008fffff] ACPI NVS
[ 0.000000] reserve setup_data: [mem 0x0000000000900000-0x000000003c00c017] usable
[ 0.000000] reserve setup_data: [mem 0x000000003c00c018-0x000000003c049057] usable
[ 0.000000] reserve setup_data: [mem 0x000000003c049058-0x000000003c04a017] usable
[ 0.000000] reserve setup_data: [mem 0x000000003c04a018-0x000000003c053c57] usable
[ 0.000000] reserve setup_data: [mem 0x000000003c053c58-0x000000003eab6fff] usable
[ 0.000000] reserve setup_data: [mem 0x000000003eab7000-0x000000003eb77fff] reserved
[ 0.000000] reserve setup_data: [mem 0x000000003eb78000-0x000000003f4ecfff] usable
[ 0.000000] reserve setup_data: [mem 0x000000003f4ed000-0x000000003f76cfff] reserved
[ 0.000000] reserve setup_data: [mem 0x000000003f76d000-0x000000003f77efff] ACPI data
[ 0.000000] reserve setup_data: [mem 0x000000003f77f000-0x000000003f7fefff] ACPI NVS
[ 0.000000] reserve setup_data: [mem 0x000000003f7ff000-0x000000003ff57fff] usable
[ 0.000000] reserve setup_data: [mem 0x000000003ff58000-0x000000003ff77fff] reserved
[ 0.000000] reserve setup_data: [mem 0x000000003ff78000-0x000000003fffffff] ACPI NVS
[ 0.000000] reserve setup_data: [mem 0x00000000b0000000-0x00000000bfffffff] reserved
[ 0.000000] efi: EFI v2.70 by EDK II
[ 0.000000] efi: SMBIOS=0x3f518000 ACPI=0x3f77e000 ACPI 2.0=0x3f77e014 MEMATTR=0x3de90018
[ 0.000000] secureboot: Secure boot disabled
[ 0.000000] SMBIOS 2.8 present.
[ 0.000000] DMI: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015
[ 0.000000] tsc: Fast TSC calibration using PIT
[ 0.000000] tsc: Detected 3792.771 MHz processor
[ 0.001653] AGP: No AGP bridge found
[ 0.001777] last_pfn = 0x3ff58 max_arch_pfn = 0x400000000
[ 0.002546] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT
[ 0.024491] RAMDISK: [mem 0x3c054000-0x3dc1ffff]
[ 0.024729] ACPI: Early table checksum verification disabled
[ 0.024945] ACPI: RSDP 0x000000003F77E014 000024 (v02 BOCHS )
[ 0.025090] ACPI: XSDT 0x000000003F77D0E8 000054 (v01 BOCHS BXPC 00000001 01000013)
[ 0.025390] ACPI: FACP 0x000000003F779000 0000F4 (v03 BOCHS BXPC 00000001 BXPC 00000001)
[ 0.025713] ACPI: DSDT 0x000000003F77A000 002087 (v01 BOCHS BXPC 00000001 BXPC 00000001)
[ 0.025760] ACPI: FACS 0x000000003F7DD000 000040
[ 0.025792] ACPI: APIC 0x000000003F778000 000078 (v01 BOCHS BXPC 00000001 BXPC 00000001)
[ 0.025810] ACPI: HPET 0x000000003F777000 000038 (v01 BOCHS BXPC 00000001 BXPC 00000001)
[ 0.025827] ACPI: MCFG 0x000000003F776000 00003C (v01 BOCHS BXPC 00000001 BXPC 00000001)
[ 0.025844] ACPI: WAET 0x000000003F775000 000028 (v01 BOCHS BXPC 00000001 BXPC 00000001)
[ 0.025860] ACPI: BGRT 0x000000003F774000 000038 (v01 INTEL EDK2 00000002 01000013)
[ 0.025906] ACPI: Reserving FACP table memory at [mem 0x3f779000-0x3f7790f3]
[ 0.025922] ACPI: Reserving DSDT table memory at [mem 0x3f77a000-0x3f77c086]
[ 0.025928] ACPI: Reserving FACS table memory at [mem 0x3f7dd000-0x3f7dd03f]
[ 0.025934] ACPI: Reserving APIC table memory at [mem 0x3f778000-0x3f778077]
[ 0.025939] ACPI: Reserving HPET table memory at [mem 0x3f777000-0x3f777037]
[ 0.025945] ACPI: Reserving MCFG table memory at [mem 0x3f776000-0x3f77603b]
[ 0.025950] ACPI: Reserving WAET table memory at [mem 0x3f775000-0x3f775027]
[ 0.025956] ACPI: Reserving BGRT table memory at [mem 0x3f774000-0x3f774037]
[ 0.027217] No NUMA configuration found
[ 0.027233] Faking a node at [mem 0x0000000000000000-0x000000003ff57fff]
[ 0.027642] NODE_DATA(0) allocated [mem 0x3feb1000-0x3fedafff]
[ 0.030178] Zone ranges:
[ 0.030213] DMA [mem 0x0000000000001000-0x0000000000ffffff]
[ 0.030238] DMA32 [mem 0x0000000001000000-0x000000003ff57fff]
[ 0.030247] Normal empty
[ 0.030258] Device empty
[ 0.030267] Movable zone start for each node
[ 0.030288] Early memory node ranges
[ 0.030306] node 0: [mem 0x0000000000001000-0x000000000009ffff]
[ 0.030370] node 0: [mem 0x0000000000100000-0x00000000007fffff]
[ 0.030376] node 0: [mem 0x0000000000808000-0x000000000080afff]
[ 0.030381] node 0: [mem 0x000000000080c000-0x000000000080ffff]
[ 0.030386] node 0: [mem 0x0000000000900000-0x000000003eab6fff]
[ 0.030402] node 0: [mem 0x000000003eb78000-0x000000003f4ecfff]
[ 0.030408] node 0: [mem 0x000000003f7ff000-0x000000003ff57fff]
[ 0.030526] Initmem setup node 0 [mem 0x0000000000001000-0x000000003ff57fff]
[ 0.031005] On node 0, zone DMA: 1 pages in unavailable ranges
[ 0.031132] On node 0, zone DMA: 96 pages in unavailable ranges
[ 0.031141] On node 0, zone DMA: 8 pages in unavailable ranges
[ 0.031146] On node 0, zone DMA: 1 pages in unavailable ranges
[ 0.031224] On node 0, zone DMA: 240 pages in unavailable ranges
[ 0.033157] On node 0, zone DMA32: 193 pages in unavailable ranges
[ 0.033216] On node 0, zone DMA32: 786 pages in unavailable ranges
[ 0.033248] On node 0, zone DMA32: 168 pages in unavailable ranges
[ 0.033450] ACPI: PM-Timer IO Port: 0x608
[ 0.033701] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
[ 0.033914] IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
[ 0.033976] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.034114] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
[ 0.034131] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.034184] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
[ 0.034192] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
[ 0.034302] Using ACPI (MADT) for SMP configuration information
[ 0.034330] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[ 0.034912] smpboot: Allowing 1 CPUs, 0 hotplug CPUs
[ 0.035481] PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
[ 0.035505] PM: hibernation: Registered nosave memory: [mem 0x000a0000-0x000fffff]
[ 0.035514] PM: hibernation: Registered nosave memory: [mem 0x00800000-0x00807fff]
[ 0.035522] PM: hibernation: Registered nosave memory: [mem 0x0080b000-0x0080bfff]
[ 0.035530] PM: hibernation: Registered nosave memory: [mem 0x00810000-0x008fffff]
[ 0.035538] PM: hibernation: Registered nosave memory: [mem 0x3c00c000-0x3c00cfff]
[ 0.035547] PM: hibernation: Registered nosave memory: [mem 0x3c049000-0x3c049fff]
[ 0.035558] PM: hibernation: Registered nosave memory: [mem 0x3c04a000-0x3c04afff]
[ 0.035566] PM: hibernation: Registered nosave memory: [mem 0x3c053000-0x3c053fff]
[ 0.035577] PM: hibernation: Registered nosave memory: [mem 0x3dc61000-0x3dc69fff]
[ 0.035586] PM: hibernation: Registered nosave memory: [mem 0x3eab7000-0x3eb77fff]
[ 0.035594] PM: hibernation: Registered nosave memory: [mem 0x3f4ed000-0x3f76cfff]
[ 0.035599] PM: hibernation: Registered nosave memory: [mem 0x3f76d000-0x3f77efff]
[ 0.035604] PM: hibernation: Registered nosave memory: [mem 0x3f77f000-0x3f7fefff]
[ 0.035669] [mem 0x40000000-0xafffffff] available for PCI devices
[ 0.035693] Booting paravirtualized kernel on bare hardware
[ 0.035898] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
[ 0.041729] setup_percpu: NR_CPUS:8192 nr_cpumask_bits:1 nr_cpu_ids:1 nr_node_ids:1
[ 0.044993] percpu: Embedded 63 pages/cpu s221184 r8192 d28672 u2097152
[ 0.046098] Built 1 zonelists, mobility grouping on. Total pages: 254748
[ 0.046109] Policy zone: DMA32
[ 0.046200] Kernel command line: initrd=\initrd.img-5.10.0-32-amd64 LABEL=Boot root=PARTUUID=8b8f5ee9-daaf-443f-b6b8-41bbd63d7784 rootwait console=ttyS0,115200 console=tty0
[ 0.048021] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[ 0.048641] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
[ 0.049506] mem auto-init: stack:off, heap alloc:on, heap free:off
[ 0.049697] AGP: Checking aperture...
[ 0.050454] AGP: No AGP bridge found
[ 0.067755] Memory: 248124K/1042604K available (12295K kernel code, 2538K rwdata, 7632K rodata, 2676K init, 17700K bss, 140008K reserved, 0K cma-reserved)
[ 0.071211] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.073692] ftrace: allocating 36690 entries in 144 pages
[ 0.118495] ftrace: allocated 144 pages with 2 groups
[ 0.122906] rcu: Hierarchical RCU implementation.
[ 0.122926] rcu: RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=1.
[ 0.122976] Rude variant of Tasks RCU enabled.
[ 0.122982] Tracing variant of Tasks RCU enabled.
[ 0.123031] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[ 0.123052] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
[ 0.138491] NR_IRQS: 524544, nr_irqs: 256, preallocated irqs: 16
[ 0.144533] Console: colour dummy device 80x25
[ 0.145913] printk: console [tty0] enabled
[ 0.176700] printk: console [ttyS0] enabled
[ 0.177399] ACPI: Core revision 20200925
[ 0.180070] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604467 ns
[ 0.182312] APIC: Switch to symmetric I/O mode setup
[ 0.185492] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.204980] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x6d575801769, max_idle_ns: 881591178932 ns
[ 0.205507] Calibrating delay loop (skipped), value calculated using timer frequency.. 7585.54 BogoMIPS (lpj=15171084)
[ 0.207049] process: using AMD E400 aware idle routine
[ 0.207342] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
[ 0.207525] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
[ 0.207842] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
[ 0.208183] Spectre V2 : Mitigation: Retpolines
[ 0.208330] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
[ 0.208598] Spectre V2 : Spectre v2 / SpectreRSB : Filling RSB on VMEXIT
[ 0.210184] x86/fpu: x87 FPU will use FXSAVE
[ 0.367585] Freeing SMP alternatives memory: 32K
[ 0.376154] pid_max: default: 32768 minimum: 301
[ 0.390083] LSM: Security Framework initializing
[ 0.390831] Yama: disabled by default; enable with sysctl kernel.yama.*
[ 0.392942] AppArmor: AppArmor initialized
[ 0.393098] TOMOYO Linux initialized
[ 0.393746] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes, linear)
[ 0.394039] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes, linear)
[ 0.515565] smpboot: CPU0: AMD QEMU Virtual CPU version 2.5+ (family: 0xf, model: 0x6b, stepping: 0x1)
[ 0.517376] Performance Events: PMU not available due to virtualization, using software events only.
[ 0.517550] rcu: Hierarchical SRCU implementation.
[ 0.520053] NMI watchdog: Perf NMI watchdog permanently disabled
[ 0.521117] smp: Bringing up secondary CPUs ...
[ 0.521384] smp: Brought up 1 node, 1 CPU
[ 0.521525] smpboot: Max logical packages: 1
[ 0.521689] smpboot: Total of 1 processors activated (7585.54 BogoMIPS)
[ 0.530779] node 0 deferred pages initialised in 8ms
[ 0.537019] devtmpfs: initialized
[ 0.538832] x86/mm: Memory block size: 128MB
[ 0.542296] PM: Registering ACPI NVS region [mem 0x00800000-0x00807fff] (32768 bytes)
[ 0.542796] PM: Registering ACPI NVS region [mem 0x0080b000-0x0080bfff] (4096 bytes)
[ 0.543030] PM: Registering ACPI NVS region [mem 0x00810000-0x008fffff] (983040 bytes)
[ 0.544339] PM: Registering ACPI NVS region [mem 0x3f77f000-0x3f7fefff] (524288 bytes)
[ 0.545146] PM: Registering ACPI NVS region [mem 0x3ff78000-0x3fffffff] (557056 bytes)
[ 0.546435] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[ 0.546895] futex hash table entries: 256 (order: 2, 16384 bytes, linear)
[ 0.548705] pinctrl core: initialized pinctrl subsystem
[ 0.555354] NET: Registered protocol family 16
[ 0.557134] DMA: preallocated 128 KiB GFP_KERNEL pool for atomic allocations
[ 0.557566] DMA: preallocated 128 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[ 0.557844] DMA: preallocated 128 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[ 0.558178] audit: initializing netlink subsys (disabled)
[ 0.561867] thermal_sys: Registered thermal governor 'fair_share'
[ 0.561884] thermal_sys: Registered thermal governor 'bang_bang'
[ 0.562092] thermal_sys: Registered thermal governor 'step_wise'
[ 0.562273] thermal_sys: Registered thermal governor 'user_space'
[ 0.562451] thermal_sys: Registered thermal governor 'power_allocator'
[ 0.562742] cpuidle: using governor ladder
[ 0.563104] cpuidle: using governor menu
[ 0.563886] ACPI: bus type PCI registered
[ 0.564057] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[ 0.565376] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xb0000000-0xbfffffff] (base 0xb0000000)
[ 0.565904] audit: type=2000 audit(1723539724.376:1): state=initialized audit_enabled=0 res=1
[ 0.566418] PCI: MMCONFIG at [mem 0xb0000000-0xbfffffff] reserved in E820
[ 0.567628] PCI: Using configuration type 1 for base access
[ 0.572645] Kprobes globally optimized
[ 0.573976] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[ 0.788692] ACPI: Added _OSI(Module Device)
[ 0.788819] ACPI: Added _OSI(Processor Device)
[ 0.788934] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.789063] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.789270] ACPI: Added _OSI(Linux-Dell-Video)
[ 0.789424] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[ 0.789584] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
[ 0.798616] ACPI: 1 ACPI AML tables successfully acquired and loaded
[ 0.806324] ACPI: Interpreter enabled
[ 0.806824] ACPI: (supports S0 S3 S4 S5)
[ 0.806974] ACPI: Using IOAPIC for interrupt routing
[ 0.807579] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.808510] ACPI: Enabled 2 GPEs in block 00 to 3F
[ 0.819338] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[ 0.819773] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3]
[ 0.820714] acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug LTR]
[ 0.821241] acpi PNP0A08:00: _OSC: OS now controls [SHPCHotplug PME AER PCIeCapability]
[ 0.823079] PCI host bridge to bus 0000:00
[ 0.823331] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window]
[ 0.823542] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window]
[ 0.823737] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
[ 0.823954] pci_bus 0000:00: root bus resource [mem 0x40000000-0xafffffff window]
[ 0.824181] pci_bus 0000:00: root bus resource [mem 0xc0000000-0xfebfffff window]
[ 0.824406] pci_bus 0000:00: root bus resource [mem 0x100000000-0x8ffffffff window]
[ 0.824712] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.825516] pci 0000:00:00.0: [8086:29c0] type 00 class 0x060000
[ 0.827362] pci 0000:00:01.0: [1234:1111] type 00 class 0x030000
[ 0.828062] pci 0000:00:01.0: reg 0x10: [mem 0xc0000000-0xc0ffffff pref]
[ 0.828952] pci 0000:00:01.0: reg 0x18: [mem 0xc1061000-0xc1061fff]
[ 0.830405] pci 0000:00:01.0: reg 0x30: [mem 0xffff0000-0xffffffff pref]
[ 0.830709] pci 0000:00:01.0: BAR 0: assigned to efifb
[ 0.831154] pci 0000:00:02.0: [8086:100e] type 00 class 0x020000
[ 0.831783] pci 0000:00:02.0: reg 0x10: [mem 0xc1040000-0xc105ffff]
[ 0.832397] pci 0000:00:02.0: reg 0x14: [io 0x6040-0x607f]
[ 0.834380] pci 0000:00:02.0: reg 0x30: [mem 0xfffc0000-0xffffffff pref]
[ 0.834863] pci 0000:00:1f.0: [8086:2918] type 00 class 0x060100
[ 0.835253] pci 0000:00:1f.0: quirk: [io 0x0600-0x067f] claimed by ICH6 ACPI/GPIO/TCO
[ 0.835834] pci 0000:00:1f.2: [8086:2922] type 00 class 0x010601
[ 0.837985] pci 0000:00:1f.2: reg 0x20: [io 0x6080-0x609f]
[ 0.838570] pci 0000:00:1f.2: reg 0x24: [mem 0xc1060000-0xc1060fff]
[ 0.839388] pci 0000:00:1f.3: [8086:2930] type 00 class 0x0c0500
[ 0.840607] pci 0000:00:1f.3: reg 0x20: [io 0x6000-0x603f]
[ 0.843067] ACPI: PCI Interrupt Link [LNKA] (IRQs 5 *10 11)
[ 0.843591] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11)
[ 0.843938] ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11)
[ 0.844273] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 10 *11)
[ 0.844645] ACPI: PCI Interrupt Link [LNKE] (IRQs 5 *10 11)
[ 0.845551] ACPI: PCI Interrupt Link [LNKF] (IRQs 5 *10 11)
[ 0.845889] ACPI: PCI Interrupt Link [LNKG] (IRQs 5 10 *11)
[ 0.846261] ACPI: PCI Interrupt Link [LNKH] (IRQs 5 10 *11)
[ 0.846509] ACPI: PCI Interrupt Link [GSIA] (IRQs *16)
[ 0.846712] ACPI: PCI Interrupt Link [GSIB] (IRQs *17)
[ 0.846901] ACPI: PCI Interrupt Link [GSIC] (IRQs *18)
[ 0.847093] ACPI: PCI Interrupt Link [GSID] (IRQs *19)
[ 0.847298] ACPI: PCI Interrupt Link [GSIE] (IRQs *20)
[ 0.847492] ACPI: PCI Interrupt Link [GSIF] (IRQs *21)
[ 0.847681] ACPI: PCI Interrupt Link [GSIG] (IRQs *22)
[ 0.847869] ACPI: PCI Interrupt Link [GSIH] (IRQs *23)
[ 0.849491] iommu: Default domain type: Translated
[ 0.850968] pci 0000:00:01.0: vgaarb: setting as boot VGA device
[ 0.851223] pci 0000:00:01.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
[ 0.851507] pci 0000:00:01.0: vgaarb: bridge control possible
[ 0.851740] vgaarb: loaded
[ 0.852413] EDAC MC: Ver: 3.0.0
[ 0.853107] Registered efivars operations
[ 0.857438] NetLabel: Initializing
[ 0.857561] NetLabel: domain hash size = 128
[ 0.857700] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO
[ 0.858268] NetLabel: unlabeled traffic allowed by default
[ 0.858474] PCI: Using ACPI for IRQ routing
[ 0.860462] hpet: 3 channels of 0 reserved for per-cpu timers
[ 0.860761] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[ 0.860948] hpet0: 3 comparators, 64-bit 100.000000 MHz counter
[ 0.863829] clocksource: Switched to clocksource tsc-early
[ 0.894879] VFS: Disk quotas dquot_6.6.0
[ 0.895107] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 0.897208] AppArmor: AppArmor Filesystem Enabled
[ 0.897605] pnp: PnP ACPI init
[ 0.899266] system 00:05: [mem 0xb0000000-0xbfffffff window] has been reserved
[ 0.900093] pnp: PnP ACPI: found 6 devices
[ 0.911287] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[ 0.911979] NET: Registered protocol family 2
[ 0.912555] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear)
[ 0.917425] tcp_listen_portaddr_hash hash table entries: 512 (order: 1, 8192 bytes, linear)
[ 0.917862] TCP established hash table entries: 8192 (order: 4, 65536 bytes, linear)
[ 0.918223] TCP bind hash table entries: 8192 (order: 5, 131072 bytes, linear)
[ 0.918623] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.919362] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
[ 0.919692] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
[ 0.920550] NET: Registered protocol family 1
[ 0.920959] NET: Registered protocol family 44
[ 0.921188] pci 0000:00:01.0: can't claim BAR 6 [mem 0xffff0000-0xffffffff pref]: no compatible bridge window
[ 0.921500] pci 0000:00:02.0: can't claim BAR 6 [mem 0xfffc0000-0xffffffff pref]: no compatible bridge window
[ 0.922402] pci 0000:00:02.0: BAR 6: assigned [mem 0x40000000-0x4003ffff pref]
[ 0.922716] pci 0000:00:01.0: BAR 6: assigned [mem 0x40040000-0x4004ffff pref]
[ 0.923039] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window]
[ 0.923228] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff window]
[ 0.923411] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
[ 0.923619] pci_bus 0000:00: resource 7 [mem 0x40000000-0xafffffff window]
[ 0.923822] pci_bus 0000:00: resource 8 [mem 0xc0000000-0xfebfffff window]
[ 0.924029] pci_bus 0000:00: resource 9 [mem 0x100000000-0x8ffffffff window]
[ 0.924613] pci 0000:00:01.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
[ 0.924923] PCI: CLS 0 bytes, default 64
[ 0.926889] Trying to unpack rootfs image as initramfs...
[ 1.591206] Freeing initrd memory: 28464K
[ 1.593849] Initialise system trusted keyrings
[ 1.594871] Key type blacklist registered
[ 1.595394] workingset: timestamp_bits=36 max_order=18 bucket_order=0
[ 1.599939] zbud: loaded
[ 1.601771] integrity: Platform Keyring initialized
[ 1.601956] Key type asymmetric registered
[ 1.602103] Asymmetric key parser 'x509' registered
[ 1.602321] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[ 1.602881] io scheduler mq-deadline registered
[ 1.604917] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 1.605280] efifb: probing for efifb
[ 1.605646] efifb: framebuffer at 0xc0000000, using 4000k, total 4000k
[ 1.605844] efifb: mode is 1280x800x32, linelength=5120, pages=1
[ 1.606026] efifb: scrolling: redraw
[ 1.606161] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 1.613646] Console: switching to colour frame buffer device 160x50
[ 1.617995] fb0: EFI VGA frame buffer device
[ 1.619819] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 1.621322] 00:03: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
[ 1.626484] Linux agpgart interface v0.103
[ 1.627344] AMD-Vi: AMD IOMMUv2 functionality not available on this system - This is not a bug.
[ 1.629082] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
[ 1.630820] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 1.631121] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 1.632037] mousedev: PS/2 mouse device common for all mice
[ 1.633756] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
[ 1.635457] rtc_cmos 00:04: RTC can wake from S4
[ 1.636992] rtc_cmos 00:04: registered as rtc0
[ 1.637431] rtc_cmos 00:04: setting system clock to 2024-08-13T09:02:06 UTC (1723539726)
[ 1.638254] rtc_cmos 00:04: alarms up to one day, y3k, 242 bytes nvram, hpet irqs
[ 1.638808] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.640000] NET: Registered protocol family 10
[ 1.734977] Segment Routing with IPv6
[ 1.735398] mip6: Mobile IPv6
[ 1.735572] NET: Registered protocol family 17
[ 1.735955] mpls_gso: MPLS GSO support
[ 1.736904] IPI shorthand broadcast: enabled
[ 1.737231] sched_clock: Marking stable (1696237203, 38670513)->(1739608786, -4701070)
[ 1.738177] registered taskstats version 1
[ 1.738363] Loading compiled-in X.509 certificates
[ 1.780986] Loaded X.509 cert 'Debian Secure Boot CA: 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1'
[ 1.783280] Loaded X.509 cert 'Debian Secure Boot Signer 2022 - linux: 14011249c2675ea8e5148542202005810584b25f'
[ 1.785403] zswap: loaded using pool lzo/zbud
[ 1.787856] Key type .fscrypt registered
[ 1.789509] Key type fscrypt-provisioning registered
[ 1.791736] AppArmor: AppArmor sha1 policy hashing enabled
[ 1.794871] clk: Disabling unused clocks
[ 1.803341] Freeing unused decrypted memory: 2036K
[ 1.846201] Freeing unused kernel image (initmem) memory: 2676K
[ 1.848063] Write protecting the kernel read-only data: 22528k
[ 1.850981] Freeing unused kernel image (text/rodata gap) memory: 2040K
[ 1.852989] Freeing unused kernel image (rodata/data gap) memory: 560K
[ 1.938943] x86/mm: Checked W+X mappings: passed, no W+X pages found.
[ 1.940689] Run /init as init process
[ 2.350078] lpc_ich 0000:00:1f.0: I/O space for GPIO uninitialized
[ 2.389104] SCSI subsystem initialized
[ 2.392397] PCI Interrupt Link [GSIA] enabled at IRQ 16
[ 2.400969] e1000: Intel(R) PRO/1000 Network Driver
[ 2.402663] e1000: Copyright (c) 1999-2006 Intel Corporation.
[ 2.431476] i801_smbus 0000:00:1f.3: Enabling SMBus device
[ 2.433355] i801_smbus 0000:00:1f.3: SMBus using PCI interrupt
[ 2.437092] PCI Interrupt Link [GSIG] enabled at IRQ 22
[ 2.464836] i2c i2c-0: 1/1 memory slots populated (from DMI)
[ 2.466505] i2c i2c-0: Memory type 0x07 not supported yet, not instantiating SPD
[ 2.562255] ahci 0000:00:1f.2: AHCI 0001.0000 32 slots 6 ports 1.5 Gbps 0x3f impl SATA mode
[ 2.564068] ahci 0000:00:1f.2: flags: 64bit ncq only
[ 2.598176] scsi host0: ahci
[ 2.616138] tsc: Refined TSC clocksource calibration: 3792.776 MHz
[ 2.617900] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x6d5760c31f0, max_idle_ns: 881590912636 ns
[ 2.619761] scsi host1: ahci
[ 2.622674] clocksource: Switched to clocksource tsc
[ 2.627955] scsi host2: ahci
[ 2.631130] scsi host3: ahci
[ 2.644417] scsi host4: ahci
[ 2.657388] scsi host5: ahci
[ 2.660450] ata1: SATA max UDMA/133 abar m4096@0xc1060000 port 0xc1060100 irq 24
[ 2.662120] ata2: SATA max UDMA/133 abar m4096@0xc1060000 port 0xc1060180 irq 24
[ 2.663696] ata3: SATA max UDMA/133 abar m4096@0xc1060000 port 0xc1060200 irq 24
[ 2.665203] ata4: SATA max UDMA/133 abar m4096@0xc1060000 port 0xc1060280 irq 24
[ 2.666682] ata5: SATA max UDMA/133 abar m4096@0xc1060000 port 0xc1060300 irq 24
[ 2.668143] ata6: SATA max UDMA/133 abar m4096@0xc1060000 port 0xc1060380 irq 24
[ 2.877830] e1000 0000:00:02.0 eth0: (PCI:33MHz:32-bit) 52:54:00:12:34:56
[ 2.879550] e1000 0000:00:02.0 eth0: Intel(R) PRO/1000 Network Connection
[ 2.989949] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 2.992642] ata2: SATA link down (SStatus 0 SControl 300)
[ 2.994474] ata4: SATA link down (SStatus 0 SControl 300)
[ 2.995930] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 2.997974] ata1.00: ATA-7: QEMU HARDDISK, 2.5+, max UDMA/100
[ 2.999434] ata1.00: 3196962 sectors, multi 16: LBA48 NCQ (depth 32)
[ 3.000921] ata1.00: applying bridge limits
[ 3.002637] ata5: SATA link down (SStatus 0 SControl 300)
[ 3.004006] ata6: SATA link down (SStatus 0 SControl 300)
[ 3.005516] ata3.00: ATAPI: QEMU DVD-ROM, 2.5+, max UDMA/100
[ 3.006918] ata3.00: applying bridge limits
[ 3.008505] ata3.00: configured for UDMA/100
[ 3.010433] ata1.00: configured for UDMA/100
[ 3.016526] scsi 0:0:0:0: Direct-Access ATA QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5
[ 3.021664] scsi 2:0:0:0: CD-ROM QEMU QEMU DVD-ROM 2.5+ PQ: 0 ANSI: 5
[ 3.059908] e1000 0000:00:02.0 enp0s2: renamed from eth0
[ 3.080637] sr 2:0:0:0: [sr0] scsi3-mmc drive: 4x/4x cd/rw xa/form2 tray
[ 3.082208] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 3.089862] sd 0:0:0:0: [sda] 3196962 512-byte logical blocks: (1.64 GB/1.52 GiB)
[ 3.091746] sd 0:0:0:0: [sda] Write Protect is off
[ 3.093478] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 3.103502] sda: sda1 sda2
[ 3.119842] sd 0:0:0:0: [sda] Attached SCSI disk
[ 3.251385] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input2
[ 3.454832] raid6: sse2x4 gen() 2137 MB/s
[ 3.522720] raid6: sse2x4 xor() 1365 MB/s
[ 3.590787] raid6: sse2x2 gen() 1760 MB/s
[ 3.658717] raid6: sse2x2 xor() 1134 MB/s
[ 3.726721] raid6: sse2x1 gen() 1789 MB/s
[ 3.794770] raid6: sse2x1 xor() 791 MB/s
[ 3.796064] raid6: using algorithm sse2x4 gen() 2137 MB/s
[ 3.797387] raid6: .... xor() 1365 MB/s, rmw enabled
[ 3.798806] raid6: using intx1 recovery algorithm
[ 3.802736] xor: measuring software checksum speed
[ 3.811468] prefetch64-sse : 1368 MB/sec
[ 3.818817] generic_sse : 1645 MB/sec
[ 3.820072] xor: using function: generic_sse (1645 MB/sec)
[ 3.942466] Btrfs loaded, crc32c=crc32c-generic
[ 4.050162] BTRFS: device label platform devid 1 transid 6 /dev/sda2 scanned by btrfs (133)
[ 4.124006] BTRFS info (device sda2): using crc32c (crc32c-generic) checksum algorithm
[ 4.125802] BTRFS info (device sda2): flagging fs with big metadata feature
[ 4.127395] BTRFS info (device sda2): disk space caching is enabled
[ 4.128930] BTRFS info (device sda2): has skinny extents
[ 4.268226] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist.
[ 4.388261] systemd[1]: Inserted module 'autofs4'
[ 4.466927] systemd[1]: systemd 247.3-7+deb11u5 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified)
[ 4.471499] systemd[1]: Detected virtualization qemu.
[ 4.473246] systemd[1]: Detected architecture x86-64.
[ 4.475104] systemd[1]: Detected first boot.
[ 4.483903] systemd[1]: Set hostname to <isar>.
[ 4.486402] random: systemd: uninitialized urandom read (16 bytes read)
[ 4.488225] systemd[1]: Initializing machine ID from random generator.
[ 5.357154] systemd[1]: Invalid unit wpa_supplicant-nl80211@.service symlink multi-user.target.wants/wpa_supplicant-nl80211@.service.
[ 5.361970] systemd[1]: Invalid unit wpa_supplicant@.service symlink multi-user.target.wants/wpa_supplicant@.service.
[ 5.364857] systemd[1]: Invalid unit wpa_supplicant-wired@.service symlink multi-user.target.wants/wpa_supplicant-wired@.service.
[ 5.367732] systemd[1]: Failed to populate /etc with preset unit settings, ignoring: Read-only file system
[ 5.569711] systemd[1]: local-fs-pre.target: Found ordering cycle on expand-on-first-boot.service/start
[ 5.571721] systemd[1]: local-fs-pre.target: Found dependency on systemd-tmpfiles-setup.service/start
[ 5.573478] systemd[1]: local-fs-pre.target: Found dependency on local-fs.target/start
[ 5.575236] systemd[1]: local-fs-pre.target: Found dependency on boot.mount/start
[ 5.576916] systemd[1]: local-fs-pre.target: Found dependency on local-fs-pre.target/start
[ 5.578636] systemd[1]: local-fs-pre.target: Job expand-on-first-boot.service/start deleted to break ordering cycle starting with local-fs-pre.target/start
[ 5.584457] systemd[1]: Queued start job for default target Graphical Interface.
[ 5.589171] random: systemd: uninitialized urandom read (16 bytes read)
[ 5.600072] systemd[1]: Created slice system-getty.slice.
[ 5.604153] random: systemd: uninitialized urandom read (16 bytes read)
[ 5.606857] systemd[1]: Created slice system-modprobe.slice.
[ 5.610552] random: systemd: uninitialized urandom read (16 bytes read)
[ 5.613310] systemd[1]: Created slice system-serial\x2dgetty.slice.
[ 5.617863] systemd[1]: Created slice User and Session Slice.
[ 5.622599] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[ 5.626870] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ 5.632599] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ 5.637152] systemd[1]: Reached target Local Encrypted Volumes.
[ 5.641293] systemd[1]: Reached target Paths.
[ 5.645320] systemd[1]: Reached target Remote File Systems.
[ 5.649372] systemd[1]: Reached target Slices.
[ 5.653399] systemd[1]: Reached target Swap.
[ 5.658227] systemd[1]: Listening on initctl Compatibility Named Pipe.
[ 5.664182] systemd[1]: Listening on Journal Audit Socket.
[ 5.668731] systemd[1]: Listening on Journal Socket (/dev/log).
[ 5.673081] systemd[1]: Listening on Journal Socket.
[ 5.677879] systemd[1]: Listening on udev Control Socket.
[ 5.682138] systemd[1]: Listening on udev Kernel Socket.
[ 5.690928] systemd[1]: Mounting Huge Pages File System...
[ 5.704206] systemd[1]: Mounting POSIX Message Queue File System...
[ 5.726947] systemd[1]: Mounting Kernel Debug File System...
[ 5.755666] systemd[1]: Mounting Kernel Trace File System...
[ 5.797637] systemd[1]: Starting Create list of static device nodes for the current kernel...
[ 5.831571] systemd[1]: Starting Load Kernel Module configfs...
[ 5.859270] systemd[1]: Starting Load Kernel Module drm...
[ 5.883201] systemd[1]: Starting Load Kernel Module fuse...
[ 5.899541] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
[ 5.957088] systemd[1]: Starting Journal Service...
[ 6.000027] systemd[1]: Starting Load Kernel Modules...
[ 6.011336] fuse: init (API version 7.32)
[ 6.030809] systemd[1]: Starting Remount Root and Kernel File Systems...
[ 6.067616] systemd[1]: Starting Coldplug All udev Devices...
[ 6.094885] ACPI: bus type drm_connector registered
[ 6.142859] systemd[1]: Mounted Huge Pages File System.
[ 6.159440] systemd[1]: Mounted POSIX Message Queue File System.
[ 6.179761] systemd[1]: Mounted Kernel Debug File System.
[ 6.216925] systemd[1]: Mounted Kernel Trace File System.
[ 6.222876] example_module: loading out-of-tree module taints kernel.
[ 6.224724] example_module: module verification failed: signature and/or required key missing - tainting kernel
[ 6.257100] Just an example
[ 6.287410] systemd[1]: Finished Create list of static device nodes for the current kernel.
[ 6.326398] systemd[1]: modprobe@configfs.service: Succeeded.
[ 6.371929] systemd[1]: Finished Load Kernel Module configfs.
[ 6.414604] systemd[1]: modprobe@drm.service: Succeeded.
[ 6.418663] BTRFS info (device sda2): disk space caching is enabled
[ 6.458991] systemd[1]: Finished Load Kernel Module drm.
[ 6.481738] systemd[1]: modprobe@fuse.service: Succeeded.
[ 6.487727] systemd[1]: Finished Load Kernel Module fuse.
[ 6.498945] systemd[1]: Finished Load Kernel Modules.
[ 6.507916] systemd[1]: Finished Remount Root and Kernel File Systems.
[ 6.533689] systemd[1]: Mounting FUSE Control File System...
[ 6.567623] systemd[1]: Mounting Kernel Configuration File System...
[ 6.591238] systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
[ 6.593392] systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped.
[ 6.610923] random: systemd: uninitialized urandom read (16 bytes read)
[ 6.633257] systemd[1]: Starting Load/Save Random Seed...
[ 6.663070] random: systemd: uninitialized urandom read (16 bytes read)
[ 6.679746] systemd[1]: Starting Apply Kernel Variables...
[ 6.696123] random: systemd: uninitialized urandom read (16 bytes read)
[ 6.716944] systemd[1]: Starting Create System Users...
[ 6.757983] systemd[1]: Mounted FUSE Control File System.
[ 6.788853] systemd[1]: Mounted Kernel Configuration File System.
[ 6.886372] systemd[1]: Finished Apply Kernel Variables.
[ 6.901190] systemd[1]: Started Journal Service.
[ 7.071137] systemd-journald[196]: Received client request to flush runtime journal.
[ 7.078485] systemd-journald[196]: Creating journal file /var/log/journal/000d7e1d579642e78eff3cb62deea43e/system.journal on a btrfs file system, and copy-on-write is enabled. This is likely to slow down journal access substantially, please consider turning off the copy-on-write file attribute on the journal directory, using chattr +C.
[ 7.322821] random: crng init done
[ 7.324736] random: 53 urandom warning(s) missed due to ratelimiting
[ 9.108343] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
[ 9.159146] ACPI: Power Button [PWRF]
[ 9.263811] parport_pc 00:02: reported by Plug and Play ACPI
[ 9.266103] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
[ 9.308732] iTCO_vendor_support: vendor-support=0
[ 9.348812] input: PC Speaker as /devices/platform/pcspkr/input/input4
[ 9.375272] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[ 9.377456] iTCO_wdt: Found a ICH9 TCO device (Version=2, TCOBASE=0x0660)
[ 9.379499] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 9.385771] pstore: Using crash dump compression: deflate
[ 9.402816] sr 2:0:0:0: Attached scsi generic sg1 type 5
[ 9.405956] pstore: Registered efi as persistent store backend
[ 9.430595] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[ 9.521979] fb0: switching to bochsdrmfb from EFI VGA
[ 9.563869] Console: switching to colour dummy device 80x25
[ 9.575351] bochs-drm 0000:00:01.0: vgaarb: deactivate vga console
[ 9.587606] [drm] Found bochs VGA, ID 0xb0c5.
[ 9.587783] [drm] Framebuffer size 16384 kB @ 0xc0000000, mmio @ 0xc1061000.
[ 9.612004] [TTM] Zone kernel: Available graphics memory: 490952 KiB
[ 9.612220] [TTM] Initializing pool allocator
[ 9.612420] [TTM] Initializing DMA pool allocator
[ 9.613645] [drm] Found EDID data blob.
[ 9.660824] [drm] Initialized bochs-drm 1.0.0 20130925 for 0000:00:01.0 on minor 0
[ 9.754329] fbcon: bochs-drmdrmfb (fb0) is primary device
[ 9.806651] Console: switching to colour frame buffer device 160x50
[ 9.836312] bochs-drm 0000:00:01.0: [drm] fb0: bochs-drmdrmfb frame buffer device
[ 10.112173] ppdev: user-space parallel port driver
[ 10.335082] kvm: Nested Virtualization enabled
[ 10.335438] SVM: kvm: Nested Paging disabled
[ 10.365273] powernow_k8: Power state transitions not supported
[ 12.374823] e1000: enp0s2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[ 12.378336] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s2: link becomes ready
Debian GNU/Linux 11 isar ttyS0
isar login: root
Password:
Linux isar 5.10.0-32-amd64 #1 SMP Debian 5.10.223-1 (2024-08-10) x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
root@isar:~# journalctl -u expand-on-first-boot | cat
-- Journal begins at Tue 2024-08-13 09:02:11 UTC, ends at Tue 2024-08-13 09:02:47 UTC. --
-- No entries --
root@isar:~#
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH v3] expand-on-first-boot: Ensure that /tmp is writable
2024-08-13 9:17 ` Uladzimir Bely
@ 2024-08-13 9:24 ` 'MOESSBAUER, Felix' via isar-users
2024-08-13 10:32 ` Uladzimir Bely
0 siblings, 1 reply; 11+ messages in thread
From: 'MOESSBAUER, Felix' via isar-users @ 2024-08-13 9:24 UTC (permalink / raw)
To: ubely, isar-users, Kowalsky, Clara
On Tue, 2024-08-13 at 12:17 +0300, Uladzimir Bely wrote:
> On Thu, 2024-07-25 at 16:17 +0200, 'Clara Kowalsky' via isar-users
> wrote:
> > By setting PrivateTmp, a new file system namespace is created for
> > this
> > service and private /tmp/<service>/tmp and /var/tmp/<service>/tmp
> > subdirectories are mounted, which are only used for processes of
> > this
> > namespace. The service unit receives a mount unit dependency for
> > all
> > mounts required to access /tmp and /var/tmp.
> > This ensures that the /tmp directory is writable for the service,
> > as
> > mktemp is used in expand-last-partition.sh and creates a temporary
> > file.
> >
> > Signed-off-by: Clara Kowalsky <clara.kowalsky@siemens.com>
> > ---
> > .../expand-on-first-boot/files/expand-on-first-boot.service |
> > 1
> > +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/meta/recipes-support/expand-on-first-
> > boot/files/expand-
> > on-first-boot.service b/meta/recipes-support/expand-on-first-
> > boot/files/expand-on-first-boot.service
> > index 90c92a39..8e76998b 100644
> > --- a/meta/recipes-support/expand-on-first-boot/files/expand-on-
> > first-boot.service
> > +++ b/meta/recipes-support/expand-on-first-boot/files/expand-on-
> > first-boot.service
> > @@ -16,6 +16,7 @@ Type=oneshot
> > ExecStart=/usr/share/expand-on-first-boot/expand-last-partition.sh
> > ExecStartPost=-/bin/systemctl disable expand-on-first-boot.service
> > ExecStopPost=-/bin/systemctl disable expand-on-first-boot.service
> > +PrivateTmp=true
> >
> > [Install]
> > WantedBy=sysinit.target
> > --
> > 2.45.2
> >
>
> Hello all.
>
> After few days having this patch merged we at least twice faced the
> issue in CI with running qemuamd64 machine, probably related to the
> applied patch.
>
> Error message is "ERROR| No resize output while expected". E.g.,
> there
> is no btrfs resize output in VM boot log.
>
> The reason of non-running expand-on-first-boot serivce is:
>
> ```
> [ 5.578636] systemd[1]: local-fs-pre.target: Job expand-on-first-
> boot.service/start deleted to break ordering cycle starting with
> local-
> fs-pre.target/start
> ```
Interesting, I observed this same issue as well, but thought it comes
from a downstream part. You're right, this cannot work:
Citing systemd.exec:
Similarly, units with PrivateTmp= enabled automatically get mount unit
dependencies for all mounts required to access /tmp/ and /var/tmp/.
They will also gain an automatic After= dependency on systemd-tmpfiles-
setup.service(8).
If /var is the partition to be resized, this will break.
Felix
>
> I'm currently debugging the issue, but for now I'll attach two logs
> when the same image was run twice - with and without an error.
>
> Maybe someone have some ideas about the issue.
>
> Actually, in case expand-on-first-boot runs OK, there is another
> target
> systemd disables:
>
> ```
> [ 5.507289] systemd[1]: local-fs.target: Job local-fs-
> pre.target/start deleted to break ordering cycle starting with local-
> fs.target/start
> ```
>
> --
> Best regards,
> Uladzimir.
>
--
Siemens AG, Technology
Linux Expert Center
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/14ba448c2f93d3aa98cf6326541d62c524c21831.camel%40siemens.com.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH v3] expand-on-first-boot: Ensure that /tmp is writable
2024-08-13 9:24 ` 'MOESSBAUER, Felix' via isar-users
@ 2024-08-13 10:32 ` Uladzimir Bely
2024-08-15 4:07 ` Uladzimir Bely
0 siblings, 1 reply; 11+ messages in thread
From: Uladzimir Bely @ 2024-08-13 10:32 UTC (permalink / raw)
To: MOESSBAUER, Felix, isar-users, Kowalsky, Clara
On Tue, 2024-08-13 at 09:24 +0000, MOESSBAUER, Felix wrote:
> On Tue, 2024-08-13 at 12:17 +0300, Uladzimir Bely wrote:
> > On Thu, 2024-07-25 at 16:17 +0200, 'Clara Kowalsky' via isar-users
> > wrote:
> > > By setting PrivateTmp, a new file system namespace is created for
> > > this
> > > service and private /tmp/<service>/tmp and /var/tmp/<service>/tmp
> > > subdirectories are mounted, which are only used for processes of
> > > this
> > > namespace. The service unit receives a mount unit dependency for
> > > all
> > > mounts required to access /tmp and /var/tmp.
> > > This ensures that the /tmp directory is writable for the service,
> > > as
> > > mktemp is used in expand-last-partition.sh and creates a
> > > temporary
> > > file.
> > >
> > > Signed-off-by: Clara Kowalsky <clara.kowalsky@siemens.com>
> > > ---
> > > .../expand-on-first-boot/files/expand-on-first-boot.service
> > > |
> > > 1
> > > +
> > > 1 file changed, 1 insertion(+)
> > >
> > > diff --git a/meta/recipes-support/expand-on-first-
> > > boot/files/expand-
> > > on-first-boot.service b/meta/recipes-support/expand-on-first-
> > > boot/files/expand-on-first-boot.service
> > > index 90c92a39..8e76998b 100644
> > > --- a/meta/recipes-support/expand-on-first-boot/files/expand-on-
> > > first-boot.service
> > > +++ b/meta/recipes-support/expand-on-first-boot/files/expand-on-
> > > first-boot.service
> > > @@ -16,6 +16,7 @@ Type=oneshot
> > > ExecStart=/usr/share/expand-on-first-boot/expand-last-
> > > partition.sh
> > > ExecStartPost=-/bin/systemctl disable expand-on-first-
> > > boot.service
> > > ExecStopPost=-/bin/systemctl disable expand-on-first-
> > > boot.service
> > > +PrivateTmp=true
> > >
> > > [Install]
> > > WantedBy=sysinit.target
> > > --
> > > 2.45.2
> > >
> >
> > Hello all.
> >
> > After few days having this patch merged we at least twice faced the
> > issue in CI with running qemuamd64 machine, probably related to the
> > applied patch.
> >
> > Error message is "ERROR| No resize output while expected". E.g.,
> > there
> > is no btrfs resize output in VM boot log.
> >
> > The reason of non-running expand-on-first-boot serivce is:
> >
> > ```
> > [ 5.578636] systemd[1]: local-fs-pre.target: Job expand-on-
> > first-
> > boot.service/start deleted to break ordering cycle starting with
> > local-
> > fs-pre.target/start
> > ```
>
> Interesting, I observed this same issue as well, but thought it comes
> from a downstream part. You're right, this cannot work:
>
> Citing systemd.exec:
>
> Similarly, units with PrivateTmp= enabled automatically get mount
> unit
> dependencies for all mounts required to access /tmp/ and /var/tmp/.
> They will also gain an automatic After= dependency on systemd-
> tmpfiles-
> setup.service(8).
>
> If /var is the partition to be resized, this will break.
>
> Felix
>
The dependency conflict seems to be here:
- expand-on-first-boot.service
Before=local-fs-pre.target
PrivateTmp=true # This means implicit "After=systemd-tmpfiles-
setup.service" dependency0, according to
https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html
- systemd-tmpfiles-setup.service
After=local-fs.target
- local-fs.target
After=local-fs-pre.target
> >
> > I'm currently debugging the issue, but for now I'll attach two logs
> > when the same image was run twice - with and without an error.
> >
> > Maybe someone have some ideas about the issue.
> >
> > Actually, in case expand-on-first-boot runs OK, there is another
> > target
> > systemd disables:
> >
> > ```
> > [ 5.507289] systemd[1]: local-fs.target: Job local-fs-
> > pre.target/start deleted to break ordering cycle starting with
> > local-
> > fs.target/start
> > ```
> >
> > --
> > Best regards,
> > Uladzimir.
> >
>
> --
> Siemens AG, Technology
> Linux Expert Center
>
>
--
Best regards,
Uladzimir.
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/28a07330fe14dadcf82f32290671ea922ab7150e.camel%40ilbers.de.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH v3] expand-on-first-boot: Ensure that /tmp is writable
2024-08-13 10:32 ` Uladzimir Bely
@ 2024-08-15 4:07 ` Uladzimir Bely
2024-09-03 7:20 ` 'MOESSBAUER, Felix' via isar-users
0 siblings, 1 reply; 11+ messages in thread
From: Uladzimir Bely @ 2024-08-15 4:07 UTC (permalink / raw)
To: MOESSBAUER, Felix, isar-users, Kowalsky, Clara
On Tue, 2024-08-13 at 13:32 +0300, Uladzimir Bely wrote:
> On Tue, 2024-08-13 at 09:24 +0000, MOESSBAUER, Felix wrote:
> > On Tue, 2024-08-13 at 12:17 +0300, Uladzimir Bely wrote:
> > > On Thu, 2024-07-25 at 16:17 +0200, 'Clara Kowalsky' via isar-
> > > users
> > > wrote:
> > > > By setting PrivateTmp, a new file system namespace is created
> > > > for
> > > > this
> > > > service and private /tmp/<service>/tmp and
> > > > /var/tmp/<service>/tmp
> > > > subdirectories are mounted, which are only used for processes
> > > > of
> > > > this
> > > > namespace. The service unit receives a mount unit dependency
> > > > for
> > > > all
> > > > mounts required to access /tmp and /var/tmp.
> > > > This ensures that the /tmp directory is writable for the
> > > > service,
> > > > as
> > > > mktemp is used in expand-last-partition.sh and creates a
> > > > temporary
> > > > file.
> > > >
> > > > Signed-off-by: Clara Kowalsky <clara.kowalsky@siemens.com>
> > > > ---
> > > > .../expand-on-first-boot/files/expand-on-first-
> > > > boot.service
> > > > >
> > > > 1
> > > > +
> > > > 1 file changed, 1 insertion(+)
> > > >
> > > > diff --git a/meta/recipes-support/expand-on-first-
> > > > boot/files/expand-
> > > > on-first-boot.service b/meta/recipes-support/expand-on-first-
> > > > boot/files/expand-on-first-boot.service
> > > > index 90c92a39..8e76998b 100644
> > > > --- a/meta/recipes-support/expand-on-first-boot/files/expand-
> > > > on-
> > > > first-boot.service
> > > > +++ b/meta/recipes-support/expand-on-first-boot/files/expand-
> > > > on-
> > > > first-boot.service
> > > > @@ -16,6 +16,7 @@ Type=oneshot
> > > > ExecStart=/usr/share/expand-on-first-boot/expand-last-
> > > > partition.sh
> > > > ExecStartPost=-/bin/systemctl disable expand-on-first-
> > > > boot.service
> > > > ExecStopPost=-/bin/systemctl disable expand-on-first-
> > > > boot.service
> > > > +PrivateTmp=true
> > > >
> > > > [Install]
> > > > WantedBy=sysinit.target
> > > > --
> > > > 2.45.2
> > > >
> > >
> > > Hello all.
> > >
> > > After few days having this patch merged we at least twice faced
> > > the
> > > issue in CI with running qemuamd64 machine, probably related to
> > > the
> > > applied patch.
> > >
> > > Error message is "ERROR| No resize output while expected". E.g.,
> > > there
> > > is no btrfs resize output in VM boot log.
> > >
> > > The reason of non-running expand-on-first-boot serivce is:
> > >
> > > ```
> > > [ 5.578636] systemd[1]: local-fs-pre.target: Job expand-on-
> > > first-
> > > boot.service/start deleted to break ordering cycle starting with
> > > local-
> > > fs-pre.target/start
> > > ```
> >
> > Interesting, I observed this same issue as well, but thought it
> > comes
> > from a downstream part. You're right, this cannot work:
> >
> > Citing systemd.exec:
> >
> > Similarly, units with PrivateTmp= enabled automatically get mount
> > unit
> > dependencies for all mounts required to access /tmp/ and /var/tmp/.
> > They will also gain an automatic After= dependency on systemd-
> > tmpfiles-
> > setup.service(8).
> >
> > If /var is the partition to be resized, this will break.
> >
> > Felix
> >
>
> The dependency conflict seems to be here:
>
> - expand-on-first-boot.service
> Before=local-fs-pre.target
> PrivateTmp=true # This means implicit "After=systemd-tmpfiles-
> setup.service" dependency0, according to
> https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html
>
> - systemd-tmpfiles-setup.service
> After=local-fs.target
>
> - local-fs.target
> After=local-fs-pre.target
>
>
Finally, does this all mean we need to revert this v3 patch and get
back to "[PATCH v2] expand-on-first-boot: Add /tmp to
ConditionPathIsReadWrite" variant?
> > >
> > > I'm currently debugging the issue, but for now I'll attach two
> > > logs
> > > when the same image was run twice - with and without an error.
> > >
> > > Maybe someone have some ideas about the issue.
> > >
> > > Actually, in case expand-on-first-boot runs OK, there is another
> > > target
> > > systemd disables:
> > >
> > > ```
> > > [ 5.507289] systemd[1]: local-fs.target: Job local-fs-
> > > pre.target/start deleted to break ordering cycle starting with
> > > local-
> > > fs.target/start
> > > ```
> > >
> > > --
> > > Best regards,
> > > Uladzimir.
> > >
> >
> > --
> > Siemens AG, Technology
> > Linux Expert Center
> >
> >
>
> --
> Best regards,
> Uladzimir.
>
--
Best regards,
Uladzimir.
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/5d23fe9e9adda350f5596f00d7b8bd1eb3c67ed6.camel%40ilbers.de.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH v3] expand-on-first-boot: Ensure that /tmp is writable
2024-08-15 4:07 ` Uladzimir Bely
@ 2024-09-03 7:20 ` 'MOESSBAUER, Felix' via isar-users
2024-09-03 9:05 ` 'Jan Kiszka' via isar-users
0 siblings, 1 reply; 11+ messages in thread
From: 'MOESSBAUER, Felix' via isar-users @ 2024-09-03 7:20 UTC (permalink / raw)
To: ubely, isar-users, Kowalsky, Clara; +Cc: Bezdeka, Florian
On Thu, 2024-08-15 at 07:07 +0300, Uladzimir Bely wrote:
> On Tue, 2024-08-13 at 13:32 +0300, Uladzimir Bely wrote:
> > On Tue, 2024-08-13 at 09:24 +0000, MOESSBAUER, Felix wrote:
> > > On Tue, 2024-08-13 at 12:17 +0300, Uladzimir Bely wrote:
> > > > On Thu, 2024-07-25 at 16:17 +0200, 'Clara Kowalsky' via isar-
> > > > users
> > > > wrote:
> > > > > By setting PrivateTmp, a new file system namespace is created
> > > > > for
> > > > > this
> > > > > service and private /tmp/<service>/tmp and
> > > > > /var/tmp/<service>/tmp
> > > > > subdirectories are mounted, which are only used for processes
> > > > > of
> > > > > this
> > > > > namespace. The service unit receives a mount unit dependency
> > > > > for
> > > > > all
> > > > > mounts required to access /tmp and /var/tmp.
> > > > > This ensures that the /tmp directory is writable for the
> > > > > service,
> > > > > as
> > > > > mktemp is used in expand-last-partition.sh and creates a
> > > > > temporary
> > > > > file.
> > > > >
> > > > > Signed-off-by: Clara Kowalsky <clara.kowalsky@siemens.com>
> > > > > ---
> > > > > .../expand-on-first-boot/files/expand-on-first-
> > > > > boot.service
> > > > > >
> > > > > 1
> > > > > +
> > > > > 1 file changed, 1 insertion(+)
> > > > >
> > > > > diff --git a/meta/recipes-support/expand-on-first-
> > > > > boot/files/expand-
> > > > > on-first-boot.service b/meta/recipes-support/expand-on-first-
> > > > > boot/files/expand-on-first-boot.service
> > > > > index 90c92a39..8e76998b 100644
> > > > > --- a/meta/recipes-support/expand-on-first-boot/files/expand-
> > > > > on-
> > > > > first-boot.service
> > > > > +++ b/meta/recipes-support/expand-on-first-boot/files/expand-
> > > > > on-
> > > > > first-boot.service
> > > > > @@ -16,6 +16,7 @@ Type=oneshot
> > > > > ExecStart=/usr/share/expand-on-first-boot/expand-last-
> > > > > partition.sh
> > > > > ExecStartPost=-/bin/systemctl disable expand-on-first-
> > > > > boot.service
> > > > > ExecStopPost=-/bin/systemctl disable expand-on-first-
> > > > > boot.service
> > > > > +PrivateTmp=true
> > > > >
> > > > > [Install]
> > > > > WantedBy=sysinit.target
> > > > > --
> > > > > 2.45.2
> > > > >
> > > >
> > > > Hello all.
> > > >
> > > > After few days having this patch merged we at least twice faced
> > > > the
> > > > issue in CI with running qemuamd64 machine, probably related to
> > > > the
> > > > applied patch.
> > > >
> > > > Error message is "ERROR| No resize output while expected".
> > > > E.g.,
> > > > there
> > > > is no btrfs resize output in VM boot log.
> > > >
> > > > The reason of non-running expand-on-first-boot serivce is:
> > > >
> > > > ```
> > > > [ 5.578636] systemd[1]: local-fs-pre.target: Job expand-on-
> > > > first-
> > > > boot.service/start deleted to break ordering cycle starting
> > > > with
> > > > local-
> > > > fs-pre.target/start
> > > > ```
> > >
> > > Interesting, I observed this same issue as well, but thought it
> > > comes
> > > from a downstream part. You're right, this cannot work:
> > >
> > > Citing systemd.exec:
> > >
> > > Similarly, units with PrivateTmp= enabled automatically get mount
> > > unit
> > > dependencies for all mounts required to access /tmp/ and
> > > /var/tmp/.
> > > They will also gain an automatic After= dependency on systemd-
> > > tmpfiles-
> > > setup.service(8).
> > >
> > > If /var is the partition to be resized, this will break.
> > >
> > > Felix
> > >
> >
> > The dependency conflict seems to be here:
> >
> > - expand-on-first-boot.service
> > Before=local-fs-pre.target
> > PrivateTmp=true # This means implicit "After=systemd-tmpfiles-
> > setup.service" dependency0, according to
> > https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html
> >
> > - systemd-tmpfiles-setup.service
> > After=local-fs.target
> >
> > - local-fs.target
> > After=local-fs-pre.target
> >
> >
>
> Finally, does this all mean we need to revert this v3 patch and get
> back to "[PATCH v2] expand-on-first-boot: Add /tmp to
> ConditionPathIsReadWrite" variant?
The conditions are evaluated right before the service starts. By that,
we might have non-deterministic behavior, depending on which service
mounts /tmp (if at all) and when it is started relative to the expand-
on-first-boot.
I'm wondering if we should better create our own tmpfs in combination
with TMPDIR, just for that service (and drop it after execution). For
obvious reasons, the expanding needs to happen VERY early, but at that
point in time not much can be assumed about the rootfs.
CC'ing Florian.
Felix
>
> > > >
> > > > I'm currently debugging the issue, but for now I'll attach two
> > > > logs
> > > > when the same image was run twice - with and without an error.
> > > >
> > > > Maybe someone have some ideas about the issue.
> > > >
> > > > Actually, in case expand-on-first-boot runs OK, there is
> > > > another
> > > > target
> > > > systemd disables:
> > > >
> > > > ```
> > > > [ 5.507289] systemd[1]: local-fs.target: Job local-fs-
> > > > pre.target/start deleted to break ordering cycle starting with
> > > > local-
> > > > fs.target/start
> > > > ```
> > > >
> > > > --
> > > > Best regards,
> > > > Uladzimir.
> > > >
> > >
> > > --
> > > Siemens AG, Technology
> > > Linux Expert Center
> > >
> > >
> >
> > --
> > Best regards,
> > Uladzimir.
> >
>
--
Siemens AG, Technology
Linux Expert Center
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/7009e44f4fb7730435f5f0d726f11448a94407d2.camel%40siemens.com.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH v3] expand-on-first-boot: Ensure that /tmp is writable
2024-09-03 7:20 ` 'MOESSBAUER, Felix' via isar-users
@ 2024-09-03 9:05 ` 'Jan Kiszka' via isar-users
2024-09-03 18:05 ` 'Florian Bezdeka' via isar-users
0 siblings, 1 reply; 11+ messages in thread
From: 'Jan Kiszka' via isar-users @ 2024-09-03 9:05 UTC (permalink / raw)
To: MOESSBAUER, Felix, ubely, isar-users, Kowalsky, Clara; +Cc: Bezdeka, Florian
On 03.09.24 09:20, 'MOESSBAUER, Felix' via isar-users wrote:
> On Thu, 2024-08-15 at 07:07 +0300, Uladzimir Bely wrote:
>> On Tue, 2024-08-13 at 13:32 +0300, Uladzimir Bely wrote:
>>> On Tue, 2024-08-13 at 09:24 +0000, MOESSBAUER, Felix wrote:
>>>> On Tue, 2024-08-13 at 12:17 +0300, Uladzimir Bely wrote:
>>>>> On Thu, 2024-07-25 at 16:17 +0200, 'Clara Kowalsky' via isar-
>>>>> users
>>>>> wrote:
>>>>>> By setting PrivateTmp, a new file system namespace is created
>>>>>> for
>>>>>> this
>>>>>> service and private /tmp/<service>/tmp and
>>>>>> /var/tmp/<service>/tmp
>>>>>> subdirectories are mounted, which are only used for processes
>>>>>> of
>>>>>> this
>>>>>> namespace. The service unit receives a mount unit dependency
>>>>>> for
>>>>>> all
>>>>>> mounts required to access /tmp and /var/tmp.
>>>>>> This ensures that the /tmp directory is writable for the
>>>>>> service,
>>>>>> as
>>>>>> mktemp is used in expand-last-partition.sh and creates a
>>>>>> temporary
>>>>>> file.
>>>>>>
>>>>>> Signed-off-by: Clara Kowalsky <clara.kowalsky@siemens.com>
>>>>>> ---
>>>>>> .../expand-on-first-boot/files/expand-on-first-
>>>>>> boot.service
>>>>>>>
>>>>>> 1
>>>>>> +
>>>>>> 1 file changed, 1 insertion(+)
>>>>>>
>>>>>> diff --git a/meta/recipes-support/expand-on-first-
>>>>>> boot/files/expand-
>>>>>> on-first-boot.service b/meta/recipes-support/expand-on-first-
>>>>>> boot/files/expand-on-first-boot.service
>>>>>> index 90c92a39..8e76998b 100644
>>>>>> --- a/meta/recipes-support/expand-on-first-boot/files/expand-
>>>>>> on-
>>>>>> first-boot.service
>>>>>> +++ b/meta/recipes-support/expand-on-first-boot/files/expand-
>>>>>> on-
>>>>>> first-boot.service
>>>>>> @@ -16,6 +16,7 @@ Type=oneshot
>>>>>> ExecStart=/usr/share/expand-on-first-boot/expand-last-
>>>>>> partition.sh
>>>>>> ExecStartPost=-/bin/systemctl disable expand-on-first-
>>>>>> boot.service
>>>>>> ExecStopPost=-/bin/systemctl disable expand-on-first-
>>>>>> boot.service
>>>>>> +PrivateTmp=true
>>>>>>
>>>>>> [Install]
>>>>>> WantedBy=sysinit.target
>>>>>> --
>>>>>> 2.45.2
>>>>>>
>>>>>
>>>>> Hello all.
>>>>>
>>>>> After few days having this patch merged we at least twice faced
>>>>> the
>>>>> issue in CI with running qemuamd64 machine, probably related to
>>>>> the
>>>>> applied patch.
>>>>>
>>>>> Error message is "ERROR| No resize output while expected".
>>>>> E.g.,
>>>>> there
>>>>> is no btrfs resize output in VM boot log.
>>>>>
>>>>> The reason of non-running expand-on-first-boot serivce is:
>>>>>
>>>>> ```
>>>>> [ 5.578636] systemd[1]: local-fs-pre.target: Job expand-on-
>>>>> first-
>>>>> boot.service/start deleted to break ordering cycle starting
>>>>> with
>>>>> local-
>>>>> fs-pre.target/start
>>>>> ```
>>>>
>>>> Interesting, I observed this same issue as well, but thought it
>>>> comes
>>>> from a downstream part. You're right, this cannot work:
>>>>
>>>> Citing systemd.exec:
>>>>
>>>> Similarly, units with PrivateTmp= enabled automatically get mount
>>>> unit
>>>> dependencies for all mounts required to access /tmp/ and
>>>> /var/tmp/.
>>>> They will also gain an automatic After= dependency on systemd-
>>>> tmpfiles-
>>>> setup.service(8).
>>>>
>>>> If /var is the partition to be resized, this will break.
>>>>
>>>> Felix
>>>>
>>>
>>> The dependency conflict seems to be here:
>>>
>>> - expand-on-first-boot.service
>>> Before=local-fs-pre.target
>>> PrivateTmp=true # This means implicit "After=systemd-tmpfiles-
>>> setup.service" dependency0, according to
>>> https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html
>>>
>>> - systemd-tmpfiles-setup.service
>>> After=local-fs.target
>>>
>>> - local-fs.target
>>> After=local-fs-pre.target
>>>
>>>
>>
>> Finally, does this all mean we need to revert this v3 patch and get
>> back to "[PATCH v2] expand-on-first-boot: Add /tmp to
>> ConditionPathIsReadWrite" variant?
>
> The conditions are evaluated right before the service starts. By that,
> we might have non-deterministic behavior, depending on which service
> mounts /tmp (if at all) and when it is started relative to the expand-
> on-first-boot.
>
> I'm wondering if we should better create our own tmpfs in combination
> with TMPDIR, just for that service (and drop it after execution). For
> obvious reasons, the expanding needs to happen VERY early, but at that
> point in time not much can be assumed about the rootfs.
>
> CC'ing Florian.
In many cases, expansion can ran also after the system is fully booted
and operational - unless it is then already complaining about too little
disk space ;)
Jan
--
Siemens AG, Technology
Linux Expert Center
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/bcda8148-e937-4f92-8551-a4e61626a568%40siemens.com.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH v3] expand-on-first-boot: Ensure that /tmp is writable
2024-09-03 9:05 ` 'Jan Kiszka' via isar-users
@ 2024-09-03 18:05 ` 'Florian Bezdeka' via isar-users
2024-09-03 19:49 ` 'Jan Kiszka' via isar-users
0 siblings, 1 reply; 11+ messages in thread
From: 'Florian Bezdeka' via isar-users @ 2024-09-03 18:05 UTC (permalink / raw)
To: Jan Kiszka, MOESSBAUER, Felix, ubely, Kowalsky, Clara; +Cc: isar-users
On Tue, 2024-09-03 at 11:05 +0200, Jan Kiszka wrote:
> On 03.09.24 09:20, 'MOESSBAUER, Felix' via isar-users wrote:
> > On Thu, 2024-08-15 at 07:07 +0300, Uladzimir Bely wrote:
> > > On Tue, 2024-08-13 at 13:32 +0300, Uladzimir Bely wrote:
> > > > On Tue, 2024-08-13 at 09:24 +0000, MOESSBAUER, Felix wrote:
> > > > > On Tue, 2024-08-13 at 12:17 +0300, Uladzimir Bely wrote:
> > > > > > On Thu, 2024-07-25 at 16:17 +0200, 'Clara Kowalsky' via isar-
> > > > > > users
> > > > > > wrote:
> > > > > > > By setting PrivateTmp, a new file system namespace is created
> > > > > > > for
> > > > > > > this
> > > > > > > service and private /tmp/<service>/tmp and
> > > > > > > /var/tmp/<service>/tmp
> > > > > > > subdirectories are mounted, which are only used for processes
> > > > > > > of
> > > > > > > this
> > > > > > > namespace. The service unit receives a mount unit dependency
> > > > > > > for
> > > > > > > all
> > > > > > > mounts required to access /tmp and /var/tmp.
> > > > > > > This ensures that the /tmp directory is writable for the
> > > > > > > service,
> > > > > > > as
> > > > > > > mktemp is used in expand-last-partition.sh and creates a
> > > > > > > temporary
> > > > > > > file.
> > > > > > >
> > > > > > > Signed-off-by: Clara Kowalsky <clara.kowalsky@siemens.com>
> > > > > > > ---
> > > > > > > .../expand-on-first-boot/files/expand-on-first-
> > > > > > > boot.service
> > > > > > > >
> > > > > > > 1
> > > > > > > +
> > > > > > > 1 file changed, 1 insertion(+)
> > > > > > >
> > > > > > > diff --git a/meta/recipes-support/expand-on-first-
> > > > > > > boot/files/expand-
> > > > > > > on-first-boot.service b/meta/recipes-support/expand-on-first-
> > > > > > > boot/files/expand-on-first-boot.service
> > > > > > > index 90c92a39..8e76998b 100644
> > > > > > > --- a/meta/recipes-support/expand-on-first-boot/files/expand-
> > > > > > > on-
> > > > > > > first-boot.service
> > > > > > > +++ b/meta/recipes-support/expand-on-first-boot/files/expand-
> > > > > > > on-
> > > > > > > first-boot.service
> > > > > > > @@ -16,6 +16,7 @@ Type=oneshot
> > > > > > > ExecStart=/usr/share/expand-on-first-boot/expand-last-
> > > > > > > partition.sh
> > > > > > > ExecStartPost=-/bin/systemctl disable expand-on-first-
> > > > > > > boot.service
> > > > > > > ExecStopPost=-/bin/systemctl disable expand-on-first-
> > > > > > > boot.service
> > > > > > > +PrivateTmp=true
> > > > > > >
> > > > > > > [Install]
> > > > > > > WantedBy=sysinit.target
> > > > > > > --
> > > > > > > 2.45.2
> > > > > > >
> > > > > >
> > > > > > Hello all.
> > > > > >
> > > > > > After few days having this patch merged we at least twice faced
> > > > > > the
> > > > > > issue in CI with running qemuamd64 machine, probably related to
> > > > > > the
> > > > > > applied patch.
> > > > > >
> > > > > > Error message is "ERROR| No resize output while expected".
> > > > > > E.g.,
> > > > > > there
> > > > > > is no btrfs resize output in VM boot log.
> > > > > >
> > > > > > The reason of non-running expand-on-first-boot serivce is:
> > > > > >
> > > > > > ```
> > > > > > [ 5.578636] systemd[1]: local-fs-pre.target: Job expand-on-
> > > > > > first-
> > > > > > boot.service/start deleted to break ordering cycle starting
> > > > > > with
> > > > > > local-
> > > > > > fs-pre.target/start
> > > > > > ```
> > > > >
> > > > > Interesting, I observed this same issue as well, but thought it
> > > > > comes
> > > > > from a downstream part. You're right, this cannot work:
> > > > >
> > > > > Citing systemd.exec:
> > > > >
> > > > > Similarly, units with PrivateTmp= enabled automatically get mount
> > > > > unit
> > > > > dependencies for all mounts required to access /tmp/ and
> > > > > /var/tmp/.
> > > > > They will also gain an automatic After= dependency on systemd-
> > > > > tmpfiles-
> > > > > setup.service(8).
> > > > >
> > > > > If /var is the partition to be resized, this will break.
> > > > >
> > > > > Felix
> > > > >
> > > >
> > > > The dependency conflict seems to be here:
> > > >
> > > > - expand-on-first-boot.service
> > > > Before=local-fs-pre.target
> > > > PrivateTmp=true # This means implicit "After=systemd-tmpfiles-
> > > > setup.service" dependency0, according to
> > > > https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html
> > > >
> > > > - systemd-tmpfiles-setup.service
> > > > After=local-fs.target
> > > >
> > > > - local-fs.target
> > > > After=local-fs-pre.target
> > > >
> > > >
> > >
> > > Finally, does this all mean we need to revert this v3 patch and get
> > > back to "[PATCH v2] expand-on-first-boot: Add /tmp to
> > > ConditionPathIsReadWrite" variant?
> >
> > The conditions are evaluated right before the service starts. By that,
> > we might have non-deterministic behavior, depending on which service
> > mounts /tmp (if at all) and when it is started relative to the expand-
> > on-first-boot.
> >
> > I'm wondering if we should better create our own tmpfs in combination
> > with TMPDIR, just for that service (and drop it after execution). For
> > obvious reasons, the expanding needs to happen VERY early, but at that
> > point in time not much can be assumed about the rootfs.
> >
> > CC'ing Florian.
>
> In many cases, expansion can ran also after the system is fully booted
> and operational - unless it is then already complaining about too little
> disk space ;)
Not sure if I can help here. expand-on-first-boot tends to explode
every time we touch it. It seems that we don't have tests for most of
the use cases (like encrypted disks, ...) which makes it hard to prove
the correctness.
Couple of things I noticed while scanning / looking at the code:
- Why do we require /etc to be writable? We only read /etc/fstab
right?
- I think all relevant file systems support growing the file system
while being active / online / mounted. Maybe we don't have to run
so early? Might help to reduce rootfs requirements.
- Do we still need expand-on-first-boot as it is right now? Seems
systemd provides x-systemd.growfs flags in /etc/fstab. Which use
cases are not supported by that systemd feature? Could we migrate?
- According to the patch description we need /tmp (or any tmpfs)
so that mktemp is working.
We use the generated tmp directory as mount point only. We never
add / write any files to it. Can't we just create any "random"
(in terms of hardcoded...) directory for that to get rid of the
systemd dependency?
Best regards,
Florian
>
> Jan
>
> --
> Siemens AG, Technology
> Linux Expert Center
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/9a103f6ae148f7183bea97c3493ee86e30da6b71.camel%40siemens.com.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH v3] expand-on-first-boot: Ensure that /tmp is writable
2024-09-03 18:05 ` 'Florian Bezdeka' via isar-users
@ 2024-09-03 19:49 ` 'Jan Kiszka' via isar-users
0 siblings, 0 replies; 11+ messages in thread
From: 'Jan Kiszka' via isar-users @ 2024-09-03 19:49 UTC (permalink / raw)
To: Florian Bezdeka, MOESSBAUER, Felix, ubely, Kowalsky, Clara; +Cc: isar-users
On 03.09.24 20:05, Florian Bezdeka wrote:
> On Tue, 2024-09-03 at 11:05 +0200, Jan Kiszka wrote:
>> On 03.09.24 09:20, 'MOESSBAUER, Felix' via isar-users wrote:
>>> On Thu, 2024-08-15 at 07:07 +0300, Uladzimir Bely wrote:
>>>> On Tue, 2024-08-13 at 13:32 +0300, Uladzimir Bely wrote:
>>>>> On Tue, 2024-08-13 at 09:24 +0000, MOESSBAUER, Felix wrote:
>>>>>> On Tue, 2024-08-13 at 12:17 +0300, Uladzimir Bely wrote:
>>>>>>> On Thu, 2024-07-25 at 16:17 +0200, 'Clara Kowalsky' via isar-
>>>>>>> users
>>>>>>> wrote:
>>>>>>>> By setting PrivateTmp, a new file system namespace is created
>>>>>>>> for
>>>>>>>> this
>>>>>>>> service and private /tmp/<service>/tmp and
>>>>>>>> /var/tmp/<service>/tmp
>>>>>>>> subdirectories are mounted, which are only used for processes
>>>>>>>> of
>>>>>>>> this
>>>>>>>> namespace. The service unit receives a mount unit dependency
>>>>>>>> for
>>>>>>>> all
>>>>>>>> mounts required to access /tmp and /var/tmp.
>>>>>>>> This ensures that the /tmp directory is writable for the
>>>>>>>> service,
>>>>>>>> as
>>>>>>>> mktemp is used in expand-last-partition.sh and creates a
>>>>>>>> temporary
>>>>>>>> file.
>>>>>>>>
>>>>>>>> Signed-off-by: Clara Kowalsky <clara.kowalsky@siemens.com>
>>>>>>>> ---
>>>>>>>> .../expand-on-first-boot/files/expand-on-first-
>>>>>>>> boot.service
>>>>>>>>>
>>>>>>>> 1
>>>>>>>> +
>>>>>>>> 1 file changed, 1 insertion(+)
>>>>>>>>
>>>>>>>> diff --git a/meta/recipes-support/expand-on-first-
>>>>>>>> boot/files/expand-
>>>>>>>> on-first-boot.service b/meta/recipes-support/expand-on-first-
>>>>>>>> boot/files/expand-on-first-boot.service
>>>>>>>> index 90c92a39..8e76998b 100644
>>>>>>>> --- a/meta/recipes-support/expand-on-first-boot/files/expand-
>>>>>>>> on-
>>>>>>>> first-boot.service
>>>>>>>> +++ b/meta/recipes-support/expand-on-first-boot/files/expand-
>>>>>>>> on-
>>>>>>>> first-boot.service
>>>>>>>> @@ -16,6 +16,7 @@ Type=oneshot
>>>>>>>> ExecStart=/usr/share/expand-on-first-boot/expand-last-
>>>>>>>> partition.sh
>>>>>>>> ExecStartPost=-/bin/systemctl disable expand-on-first-
>>>>>>>> boot.service
>>>>>>>> ExecStopPost=-/bin/systemctl disable expand-on-first-
>>>>>>>> boot.service
>>>>>>>> +PrivateTmp=true
>>>>>>>>
>>>>>>>> [Install]
>>>>>>>> WantedBy=sysinit.target
>>>>>>>> --
>>>>>>>> 2.45.2
>>>>>>>>
>>>>>>>
>>>>>>> Hello all.
>>>>>>>
>>>>>>> After few days having this patch merged we at least twice faced
>>>>>>> the
>>>>>>> issue in CI with running qemuamd64 machine, probably related to
>>>>>>> the
>>>>>>> applied patch.
>>>>>>>
>>>>>>> Error message is "ERROR| No resize output while expected".
>>>>>>> E.g.,
>>>>>>> there
>>>>>>> is no btrfs resize output in VM boot log.
>>>>>>>
>>>>>>> The reason of non-running expand-on-first-boot serivce is:
>>>>>>>
>>>>>>> ```
>>>>>>> [ 5.578636] systemd[1]: local-fs-pre.target: Job expand-on-
>>>>>>> first-
>>>>>>> boot.service/start deleted to break ordering cycle starting
>>>>>>> with
>>>>>>> local-
>>>>>>> fs-pre.target/start
>>>>>>> ```
>>>>>>
>>>>>> Interesting, I observed this same issue as well, but thought it
>>>>>> comes
>>>>>> from a downstream part. You're right, this cannot work:
>>>>>>
>>>>>> Citing systemd.exec:
>>>>>>
>>>>>> Similarly, units with PrivateTmp= enabled automatically get mount
>>>>>> unit
>>>>>> dependencies for all mounts required to access /tmp/ and
>>>>>> /var/tmp/.
>>>>>> They will also gain an automatic After= dependency on systemd-
>>>>>> tmpfiles-
>>>>>> setup.service(8).
>>>>>>
>>>>>> If /var is the partition to be resized, this will break.
>>>>>>
>>>>>> Felix
>>>>>>
>>>>>
>>>>> The dependency conflict seems to be here:
>>>>>
>>>>> - expand-on-first-boot.service
>>>>> Before=local-fs-pre.target
>>>>> PrivateTmp=true # This means implicit "After=systemd-tmpfiles-
>>>>> setup.service" dependency0, according to
>>>>> https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html
>>>>>
>>>>> - systemd-tmpfiles-setup.service
>>>>> After=local-fs.target
>>>>>
>>>>> - local-fs.target
>>>>> After=local-fs-pre.target
>>>>>
>>>>>
>>>>
>>>> Finally, does this all mean we need to revert this v3 patch and get
>>>> back to "[PATCH v2] expand-on-first-boot: Add /tmp to
>>>> ConditionPathIsReadWrite" variant?
>>>
>>> The conditions are evaluated right before the service starts. By that,
>>> we might have non-deterministic behavior, depending on which service
>>> mounts /tmp (if at all) and when it is started relative to the expand-
>>> on-first-boot.
>>>
>>> I'm wondering if we should better create our own tmpfs in combination
>>> with TMPDIR, just for that service (and drop it after execution). For
>>> obvious reasons, the expanding needs to happen VERY early, but at that
>>> point in time not much can be assumed about the rootfs.
>>>
>>> CC'ing Florian.
>>
>> In many cases, expansion can ran also after the system is fully booted
>> and operational - unless it is then already complaining about too little
>> disk space ;)
>
> Not sure if I can help here. expand-on-first-boot tends to explode
> every time we touch it. It seems that we don't have tests for most of
> the use cases (like encrypted disks, ...) which makes it hard to prove
> the correctness.
>
> Couple of things I noticed while scanning / looking at the code:
>
> - Why do we require /etc to be writable? We only read /etc/fstab
> right?
>
Was like that since day #1, and the original author forgot the reason.
> - I think all relevant file systems support growing the file system
> while being active / online / mounted. Maybe we don't have to run
> so early? Might help to reduce rootfs requirements.
>
Just found 7dff89e9a10b3b5d9fc07f73a74258e51a3fe2dd and
"Before=local-fs-pre.target" - seems we do need to be early in some cases.
> - Do we still need expand-on-first-boot as it is right now? Seems
> systemd provides x-systemd.growfs flags in /etc/fstab. Which use
> cases are not supported by that systemd feature? Could we migrate?
>
Henning and Tobias tried that and had to give up, see
35f9487a849a10e40d4fbb3d9b6f13a25d4a1f96.
> - According to the patch description we need /tmp (or any tmpfs)
> so that mktemp is working.
>
> We use the generated tmp directory as mount point only. We never
> add / write any files to it. Can't we just create any "random"
> (in terms of hardcoded...) directory for that to get rid of the
> systemd dependency?
/.expand-on-first-boot-mountpoint?
Jan
--
Siemens AG, Technology
Linux Expert Center
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/0176a32d-9d97-40f1-91cf-7e6a292cb6a3%40siemens.com.
^ permalink raw reply [flat|nested] 11+ messages in thread
* [PATCH v3] expand-on-first-boot: Ensure that /tmp is writable
@ 2024-07-24 13:39 'Clara Kowalsky' via isar-users
0 siblings, 0 replies; 11+ messages in thread
From: 'Clara Kowalsky' via isar-users @ 2024-07-24 13:39 UTC (permalink / raw)
To: isar-users; +Cc: quirin.gylstorff, Clara Kowalsky
By setting PrivateTmp, a new file system namespace is created for this
service and private /tmp/<service>/tmp and /var/tmp/<service>/tmp
subdirectories are mounted, which are only used for processes of this
namespace. The service unit receives a mount unit dependency for all
mounts required to access /tmp and /var/tmp.
This ensures that the /tmp directory is writable for the service, as
mktemp is used in expand-last-partition.sh and creates a temporary file.
---
.../expand-on-first-boot/files/expand-on-first-boot.service | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-support/expand-on-first-boot/files/expand-on-first-boot.service b/meta/recipes-support/expand-on-first-boot/files/expand-on-first-boot.service
index 90c92a39..8e76998b 100644
--- a/meta/recipes-support/expand-on-first-boot/files/expand-on-first-boot.service
+++ b/meta/recipes-support/expand-on-first-boot/files/expand-on-first-boot.service
@@ -16,6 +16,7 @@ Type=oneshot
ExecStart=/usr/share/expand-on-first-boot/expand-last-partition.sh
ExecStartPost=-/bin/systemctl disable expand-on-first-boot.service
ExecStopPost=-/bin/systemctl disable expand-on-first-boot.service
+PrivateTmp=true
[Install]
WantedBy=sysinit.target
--
2.45.2
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/20240724133938.1298789-1-clara.kowalsky%40siemens.com.
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2024-09-03 19:49 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-07-25 14:17 [PATCH v3] expand-on-first-boot: Ensure that /tmp is writable 'Clara Kowalsky' via isar-users
2024-07-31 6:46 ` Uladzimir Bely
2024-08-13 9:17 ` Uladzimir Bely
2024-08-13 9:24 ` 'MOESSBAUER, Felix' via isar-users
2024-08-13 10:32 ` Uladzimir Bely
2024-08-15 4:07 ` Uladzimir Bely
2024-09-03 7:20 ` 'MOESSBAUER, Felix' via isar-users
2024-09-03 9:05 ` 'Jan Kiszka' via isar-users
2024-09-03 18:05 ` 'Florian Bezdeka' via isar-users
2024-09-03 19:49 ` 'Jan Kiszka' via isar-users
-- strict thread matches above, loose matches on Subject: below --
2024-07-24 13:39 'Clara Kowalsky' via isar-users
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox