Mailing List Archive

Hi,

any ideas or hints to progress?

Regards
Volker

Am 12.01.24 um 11:39 schrieb Volker Weber:
> Hi,
>
> i can't start any guests on a fresh installed debian 12 system. xl
> create fails after ~10s with timeout accessing console tty:
>
> $ sudo xl create /opt/inexso-xen/hosts/btest.webertest.inexso.intra.cfg
> Parsing config from /opt/inexso-xen/hosts/btest.webertest.inexso.intra.cfg
> libxl: error: libxl_create.c:1976:console_xswait_callback: domain 1
> console tty: timed out
> libxl: error: libxl_domain.c:1183:libxl__destroy_domid: Domain
> 1:Non-existant domain
> libxl: error: libxl_domain.c:1137:domain_destroy_callback: Domain
> 1:Unable to destroy guest
> libxl: error: libxl_domain.c:1064:domain_destroy_cb: Domain
> 1:Destruction of domain failed
>
>
> trying to debug this i found xenconsoled crashed after first try to
> start an vm.
>
> Before xl create, just after fresh reboot:
>
> $ ps auxf | grep xen
> root          65  0.0  0.0      0     0 ?        S    14:31   0:00  \_
> [xenbus]
> root          66  0.0  0.0      0     0 ?        S    14:31   0:00  \_
> [xenwatch]
> root          76  0.0  0.0      0     0 ?        S    14:31   0:00  \_
> [xen-balloon]
> root        1066  0.0  0.0  11692  3932 ?        S    14:31   0:00
> /usr/lib/xen-4.17/bin/oxenstored --pid-file /run/xenstore.pid
> root        1076  0.0  0.0  68448  1716 ?        Sl   14:31   0:00
> /usr/lib/xen-4.17/bin/xenconsoled --pid-file /run/xenconsoled.pid
> root        1096  0.0  0.0 244484 12612 ?        Sl   14:31   0:00
> /usr/libexec/xen-qemu-system-i386 -xen-domid 0 -xen-attach -name dom0
> -nographic -M xenpv -daemonize -monitor none -serial none -parallel none
> -pidfile /run/qemu-dom0.pid
>
> Some seconds after xl create:
>
> $ ps auxf | grep xen
> root          65  0.0  0.0      0     0 ?        S    14:31   0:00  \_
> [xenbus]
> root          66  0.0  0.0      0     0 ?        S    14:31   0:00  \_
> [xenwatch]
> root          76  0.8  0.0      0     0 ?        S    14:31   0:01  \_
> [xen-balloon]
> root        1066  0.0  0.0  11696  5076 ?        S    14:31   0:00
> /usr/lib/xen-4.17/bin/oxenstored --pid-file /run/xenstore.pid
> root        1076  0.0  0.0      0     0 ?        Zl   14:31   0:00
> [xenconsoled] <defunct>
> root        1096  0.0  0.0 244484 12612 ?        Sl   14:31   0:00
> /usr/libexec/xen-qemu-system-i386 -xen-domid 0 -xen-attach -name dom0
> -nographic -M xenpv -daemonize -monitor none -serial none -parallel none
> -pidfile /run/qemu-dom0.pid
> root        3344  0.0  0.0  10128  4796 pts/0    S+   14:33   0:00  |
>        \_ sudo xl create
> /opt/inexso-xen/hosts/btest.webertest.inexso.intra.cfg
> root        3345  0.0  0.0  10260   508 pts/4    Ss   14:33   0:00  |
>            \_ sudo xl create
> /opt/inexso-xen/hosts/btest.webertest.inexso.intra.cfg
> root        3346 24.1  0.1 114228 47284 pts/4    Sl+  14:33   0:01  |
>                \_ /usr/lib/xen-4.17/bin/xl create
> /opt/inexso-xen/hosts/btest.webertest.inexso.intra.cfg
>
>
> the xenconsoled is crashed.
>
>
> Some additional information, in /var/log/xen/xenstored-access.log i found:
>
> [20240110T14:10:18.476Z]  A9           write /local/domain/1/console/tty
> /dev/pts/4
>
> and (here are the 10s timeout)
>
> [20240111T12:44:15.414Z]  A9           watch /local/domain/1/console/tty
> 2/4
> [20240111T12:44:15.414Z]  A9           w event
> /local/domain/1/console/tty 2/4
> [20240111T12:44:25.424Z]  A9           unwatch
> /local/domain/1/console/tty 2/4
>
>
> at this point there is no /dev/pts/4. Before xl create there are pst 0,
> 1 and 2, during xl create hangs there is also a pts 3.
>
> I can reproduce this at every reboot.
>
> Any Ideas how to solve this?
>
> Regards,
>
>   Volker Weber
>
>
>
>
>

Hello,

https://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=tools/hotplug/Linux/init.d/xencommons.in;h=7fd6903b9868e27f855ba797a2529e6e2171d089;hb=refs/heads/staging-4.17

It seems your distro xen-4.17 uses the init scripts for xen services, not
systemd. The above branch in xen.git shows where/how xenconsoled is
started. It does
write a PID for xenconsoled.

Note that the systemd service for xenconsoled has no such PID. However, I
suspect you have a stale PID for xenconsoled, check the write time against
the other xen PID's.

>ps aux | grep xen
root 41 0.0 0.0 0 0 ? S 17:15 0:00 [xenbus]
root 42 0.0 0.0 0 0 ? S 17:15 0:00
[xenwatch]
root 52 0.0 0.0 0 0 ? S 17:15 0:00
[xen-balloon]
root 721 0.5 0.2 7508 3444 ? S 17:15 0:00
/usr/sbin/xenstored --pid-file /var/run/xen/xenstored.pid
root 729 0.0 0.1 68784 2280 ? Ssl 17:15 0:00
/usr/sbin/xenconsoled -i --log=none --log-dir=/var/log/xen/console
root 738 0.0 1.1 254580 16236 ? Sl 17:15 0:00
/usr/bin/qemu-system-i386 -xen-domid 0 -xen-attach -name dom0 -nographic -M
xenpv -daemonize -monitor /dev/null -serial /dev/null -parallel /dev/null
-nodefaults -no-user-config -pidfile /var/run/xen/qemu-dom0.pid
root 1032 0.0 0.1 72136 2612 ? Ssl 17:15 0:00
/usr/lib/xen-4.17/bin/xl create --quiet --defconfig /etc/xen/auto/a_jam22
root 1526 0.0 0.1 72136 2512 ? Ssl 17:15 0:00
/usr/lib/xen-4.17/bin/xl create --quiet --defconfig /etc/xen/auto/b_booky
root 1899 0.0 0.1 72136 2660 ? Ssl 17:15 0:00
/usr/lib/xen-4.17/bin/xl create --quiet --defconfig /etc/xen/auto/c_al9pv
root 2306 0.0 0.1 72136 2436 ? Ssl 17:15 0:00
/usr/lib/xen-4.17/bin/xl create --quiet --defconfig /etc/xen/auto/d_al8pv
root 2732 0.0 0.1 72136 2552 ? Ssl 17:15 0:00
/usr/lib/xen-4.17/bin/xl create --quiet --defconfig /etc/xen/auto/e_fc37cnv
root 3070 0.0 0.1 72136 2512 ? Ssl 17:15 0:00
/usr/lib/xen-4.17/bin/xl create --quiet --defconfig /etc/xen/auto/h_pvbully
root 3545 0.0 0.1 72136 2664 ? Ssl 17:15 0:00
/usr/lib/xen-4.17/bin/xl create --quiet --defconfig /etc/xen/auto/j_ub2204
root 3928 0.0 0.1 72136 2464 ? Ssl 17:15 0:00
/usr/lib/xen-4.17/bin/xl create --quiet --defconfig /etc/xen/auto/k_noble1
root 3938 0.0 0.0 2788 172 ? Ss 17:15 0:00
/usr/sbin/xenwatchdogd 30 15
root 4101 0.0 0.3 10004 4444 pts/4 S+ 17:17 0:00 sudo
./dump_xen_trace.multi.4h tlviewer
root 4102 0.0 0.1 2576 1652 pts/4 S+ 17:17 0:00 sh
./dump_xen_trace.multi.4h tlviewer
root 4169 0.0 0.1 6652 2120 pts/4 S+ 17:17 0:00 grep xen

I have a build of xen-4.17.3 running on Bookworm that uses the systemd
services. See above.
https://repo.dynavirt.com/xen/debian/bookworm-nmu/4hx-q724/setup/xl-info-deb12.multi.html

cheers,
PryMar56

Hi,

yes, systemd uses the init.d xen scripts, but the PIDs in the files are
correct:

$ systemctl status xen
? xen.service - LSB: Xen daemons
Loaded: loaded (/etc/init.d/xen; generated)
Active: active (running) since Thu 2024-01-25 14:11:42 CET; 13min ago
Docs: man:systemd-sysv-generator(8)
Process: 1203 ExecStart=/etc/init.d/xen start (code=exited,
status=0/SUCCESS)
Tasks: 7 (limit: 46177)
Memory: 28.9M
CPU: 130ms
CGroup: /system.slice/xen.service
??1279 /usr/lib/xen-4.17/bin/oxenstored --pid-file
/run/xenstore.pid
??1290 /usr/lib/xen-4.17/bin/xenconsoled --pid-file
/run/xenconsoled.pid
??1309 /usr/libexec/xen-qemu-system-i386 -xen-domid 0
-xen-attach -name dom0 -nographic -M xenpv -daemonize -monitor none
-serial none -parallel none -pidfile /run/qemu-dom0.pid

Jan 25 14:11:42 osiris systemd[1]: Starting xen.service - LSB: Xen
daemons...
Jan 25 14:11:42 osiris xen[1203]: Starting Xen daemons: xenfs xenstored
xenconsoled qemu.
Jan 25 14:11:42 osiris systemd[1]: Started xen.service - LSB: Xen daemons.

$ sudo cat /run/xenstore.pid /run/xenconsoled.pid /run/qemu-dom0.pid
1279
1290
1309


I can't find any xen 4.17.3 packages in debian bookworm, from which
repro did you get them?

regards
Volker




Am 24.01.24 um 22:12 schrieb Pry Mar:
> Hello,
>
> https://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=tools/hotplug/Linux/init.d/xencommons.in;h=7fd6903b9868e27f855ba797a2529e6e2171d089;hb=refs/heads/staging-4.17 <https://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=tools/hotplug/Linux/init.d/xencommons.in;h=7fd6903b9868e27f855ba797a2529e6e2171d089;hb=refs/heads/staging-4.17>
>
> It seems your distro xen-4.17 uses the init scripts for xen services,
> not systemd. The above branch in xen.git shows where/how xenconsoled is
> started. It does
> write a PID for xenconsoled.
>
> Note that the systemd service for xenconsoled has no such PID. However,
> I suspect you have a stale PID for xenconsoled, check the write time
> against the other xen PID's.
>
> >ps aux | grep xen
> root          41  0.0  0.0      0     0 ?        S    17:15   0:00 [xenbus]
> root          42  0.0  0.0      0     0 ?        S    17:15   0:00
> [xenwatch]
> root          52  0.0  0.0      0     0 ?        S    17:15   0:00
> [xen-balloon]
> root         721  0.5  0.2   7508  3444 ?        S    17:15   0:00
> /usr/sbin/xenstored --pid-file /var/run/xen/xenstored.pid
> root         729  0.0  0.1  68784  2280 ?        Ssl  17:15   0:00
> /usr/sbin/xenconsoled -i --log=none --log-dir=/var/log/xen/console
> root         738  0.0  1.1 254580 16236 ?        Sl   17:15   0:00
> /usr/bin/qemu-system-i386 -xen-domid 0 -xen-attach -name dom0 -nographic
> -M xenpv -daemonize -monitor /dev/null -serial /dev/null -parallel
> /dev/null -nodefaults -no-user-config -pidfile /var/run/xen/qemu-dom0.pid
> root        1032  0.0  0.1  72136  2612 ?        Ssl  17:15   0:00
> /usr/lib/xen-4.17/bin/xl create --quiet --defconfig /etc/xen/auto/a_jam22
> root        1526  0.0  0.1  72136  2512 ?        Ssl  17:15   0:00
> /usr/lib/xen-4.17/bin/xl create --quiet --defconfig /etc/xen/auto/b_booky
> root        1899  0.0  0.1  72136  2660 ?        Ssl  17:15   0:00
> /usr/lib/xen-4.17/bin/xl create --quiet --defconfig /etc/xen/auto/c_al9pv
> root        2306  0.0  0.1  72136  2436 ?        Ssl  17:15   0:00
> /usr/lib/xen-4.17/bin/xl create --quiet --defconfig /etc/xen/auto/d_al8pv
> root        2732  0.0  0.1  72136  2552 ?        Ssl  17:15   0:00
> /usr/lib/xen-4.17/bin/xl create --quiet --defconfig /etc/xen/auto/e_fc37cnv
> root        3070  0.0  0.1  72136  2512 ?        Ssl  17:15   0:00
> /usr/lib/xen-4.17/bin/xl create --quiet --defconfig /etc/xen/auto/h_pvbully
> root        3545  0.0  0.1  72136  2664 ?        Ssl  17:15   0:00
> /usr/lib/xen-4.17/bin/xl create --quiet --defconfig /etc/xen/auto/j_ub2204
> root        3928  0.0  0.1  72136  2464 ?        Ssl  17:15   0:00
> /usr/lib/xen-4.17/bin/xl create --quiet --defconfig /etc/xen/auto/k_noble1
> root        3938  0.0  0.0   2788   172 ?        Ss   17:15   0:00
> /usr/sbin/xenwatchdogd 30 15
> root        4101  0.0  0.3  10004  4444 pts/4    S+   17:17   0:00 sudo
> ./dump_xen_trace.multi.4h tlviewer
> root        4102  0.0  0.1   2576  1652 pts/4    S+   17:17   0:00 sh
> ./dump_xen_trace.multi.4h tlviewer
> root        4169  0.0  0.1   6652  2120 pts/4    S+   17:17   0:00 grep xen
>
> I have a build of xen-4.17.3 running on Bookworm that uses the systemd
> services. See above.
> https://repo.dynavirt.com/xen/debian/bookworm-nmu/4hx-q724/setup/xl-info-deb12.multi.html <https://repo.dynavirt.com/xen/debian/bookworm-nmu/4hx-q724/setup/xl-info-deb12.multi.html>
>
> cheers,
> PryMar56

Hi,

i find out a little bit more this weekend.

I did manny test installations with debian11 and debian12 on different
hardware.

With an old system i could install both debian versions with running xen
guests.

With the relavant laptop (lenovo thinkpad) i got debian11 working, bud
debian12 fails to start pvguests with defunct xenconsoled after first try.

I found a kernelbug message in dmesg. Is this a xen problem, or should i
reprort to debian maintainers?

Any help appreciated.

Regards

volker

[ 654.248294] ------------[ cut here ]------------
[ 654.248294] kernel BUG at arch/x86/xen/p2m.c:542!
[ 654.248294] invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
[ 654.248294] CPU: 3 PID: 699 Comm: xenconsoled Not tainted
6.1.0-17-amd64 #1 Debian 6.1.69-1
[ 654.248294] Hardware name: LENOVO 20T6000JGE/20T6000JGE, BIOS
R1AET32W (1.08 ) 08/14/2020
[ 654.248294] RIP: e030:xen_alloc_p2m_entry+0x596/0x880
[ 654.248565] Code: 3d 97 b1 c1 01 73 5d 48 8b 05 96 b1 c1 01 48 8b 04
f8 48 83 f8 ff 74 59 48 bf ff ff ff ff ff ff ff 3f 48 21 c7 e9 59 fb ff
ff <0f> 0b 49 8d 7e 08 4c 89 f1 48 c7 c0 ff ff ff ff 49 c7 06 ff ff ff
[ 654.248565] RSP: e02b:ffffc900412efca8 EFLAGS: 00010246
[ 654.248565] RAX: 0000000000000000 RBX: 0000000010007fff RCX:
ffffffff82a10000
[ 654.248565] RDX: 0000000000000000 RSI: ffffc9008003fff8 RDI:
0000000a0a20a067
[ 654.248565] RBP: ffffc900412efd50 R08: ffffea0000000000 R09:
0000000000000000
[ 654.248565] R10: 0000000000000000 R11: ffff898088000000 R12:
ffffc9008003fff8
[ 654.248565] R13: 0000000000000000 R14: 0000000010008000 R15:
0000000010008000
[ 654.248784] FS: 00007f43d8220740(0000) GS:ffff8889e88c0000(0000)
knlGS:0000000000000000
[ 654.248784] CS: e030 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 654.248784] CR2: 00005605b4be73c0 CR3: 0000000104006000 CR4:
0000000000050660
[ 654.248871] Call Trace:
[ 654.248871] <TASK>
[ 654.248871] ? __die_body.cold+0x1a/0x1f
[ 654.248871] ? die+0x2a/0x50
[ 654.248871] ? do_trap+0xc5/0x110
[ 654.248871] ? xen_alloc_p2m_entry+0x596/0x880
[ 654.248871] ? do_error_trap+0x6a/0x90
[ 654.248871] ? xen_alloc_p2m_entry+0x596/0x880
[ 654.248871] ? exc_invalid_op+0x4c/0x60
[ 654.248871] ? xen_alloc_p2m_entry+0x596/0x880
[ 654.248871] ? asm_exc_invalid_op+0x16/0x20
[ 654.248871] ? xen_alloc_p2m_entry+0x596/0x880
[ 654.248871] ? xen_alloc_p2m_entry+0x46/0x880
[ 654.248871] xen_alloc_unpopulated_pages+0xa0/0x450
[ 654.248871] gnttab_alloc_pages+0x14/0x40
[ 654.248871] gntdev_alloc_map+0x1cf/0x2e0 [xen_gntdev]
[ 654.248871] gntdev_ioctl+0x2a3/0x5a0 [xen_gntdev]
[ 654.248871] __x64_sys_ioctl+0x90/0xd0
[ 654.248871] do_syscall_64+0x5b/0xc0
[ 654.248871] ? ksys_write+0xd4/0xf0
[ 654.248877] ? exit_to_user_mode_prepare+0x40/0x1e0
[ 654.248911] ? syscall_exit_to_user_mode+0x27/0x40
[ 654.248940] ? do_syscall_64+0x67/0xc0
[ 654.248962] ? ksys_write+0xd4/0xf0
[ 654.248981] ? exit_to_user_mode_prepare+0x40/0x1e0
[ 654.249005] ? syscall_exit_to_user_mode+0x27/0x40
[ 654.249027] ? do_syscall_64+0x67/0xc0
[ 654.249048] ? exit_to_user_mode_prepare+0x40/0x1e0
[ 654.249071] entry_SYSCALL_64_after_hwframe+0x64/0xce
[ 654.249096] RIP: 0033:0x7f43d8338b5b
[ 654.249120] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10
00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f
05 <89> c2 3d 00 f0 ff ff 77 1c 48 8b 44 24 18 64 48 2b 04 25 28 00 00
[ 654.249181] RSP: 002b:00007ffcf319c670 EFLAGS: 00000246 ORIG_RAX:
0000000000000010
[ 654.249222] RAX: ffffffffffffffda RBX: 0000000000001000 RCX:
00007f43d8338b5b
[ 654.249256] RDX: 00007ffcf319c6d0 RSI: 0000000000184700 RDI:
000000000000000a
[ 654.249281] RBP: 00007ffcf319c780 R08: 00007ffcf319c7ac R09:
00007ffcf319c6d0
[ 654.249307] R10: 0000000000000004 R11: 0000000000000246 R12:
00007ffcf319c6d0
[ 654.249336] R13: 0000000000000003 R14: 000000000000000a R15:
0000000000000001
[ 654.249895] </TASK>
[ 654.249897] Modules linked in: xen_netback xen_blkback bridge stp llc
hid_generic r8153_ecm cdc_ether usbnet snd_usb_audio usbhid
snd_usbmidi_lib hid snd_rawmidi snd_seq_device cmac algif_hash
algif_skcipher af_alg bnep xen_acpi_processor xen_gntdev xen_evtchn
xenfs xen_privcmd binfmt_misc nls_ascii nls_cp437 vfat fat r8152 mii
amdgpu iwlmvm snd_ctl_led intel_rapl_msr intel_rapl_common
snd_hda_codec_realtek ghash_clmulni_intel snd_hda_codec_generic mac80211
snd_hda_codec_hdmi sha256_ssse3 gpu_sched drm_buddy sha1_ssse3 libarc4
drm_display_helper snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi
uvcvideo cec snd_hda_codec videobuf2_vmalloc videobuf2_memops rc_core
videobuf2_v4l2 drm_ttm_helper videobuf2_common snd_hda_core
snd_pci_acp6x ttm snd_pci_acp5x snd_hwdep iwlwifi videodev
snd_rn_pci_acp3x snd_pcm snd_acp_config drm_kms_helper snd_soc_acpi mc
i2c_algo_bit ccp snd_pci_acp3x snd_timer ucsi_acpi thinkpad_acpi
aesni_intel nvram btusb typec_ucsi think_lmi platform_profile cfg80211
[ 654.249897] sp5100_tco btrtl crypto_simd roles ledtrig_audio cryptd
pcspkr wmi_bmof firmware_attributes_class k10temp btbcm watchdog typec
snd btintel btmtk soundcore ac bluetooth button joydev evdev serio_raw
jitterentropy_rng sha512_ssse3 sha512_generic ctr drbg ansi_cprng
ecdh_generic rfkill ecc drm fuse loop efi_pstore configfs efivarfs
ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic dm_mod
xhci_pci nvme crc32_pclmul xhci_hcd r8169 nvme_core realtek mdio_devres
t10_pi psmouse crc32c_intel usbcore libphy i2c_piix4 crc64_rocksoft
crc64 crc_t10dif usb_common crct10dif_generic crct10dif_pclmul
crct10dif_common video battery wmi i2c_scmi
[ 654.254301] ---[ end trace 0000000000000000 ]---


Am 25.01.24 um 15:17 schrieb Volker Weber:
> Hi,
>
> yes, systemd uses the init.d xen scripts, but the PIDs in the files are
> correct:
>
> $ systemctl status xen
> ? xen.service - LSB: Xen daemons
>      Loaded: loaded (/etc/init.d/xen; generated)
>      Active: active (running) since Thu 2024-01-25 14:11:42 CET; 13min ago
>        Docs: man:systemd-sysv-generator(8)
>     Process: 1203 ExecStart=/etc/init.d/xen start (code=exited,
> status=0/SUCCESS)
>       Tasks: 7 (limit: 46177)
>      Memory: 28.9M
>         CPU: 130ms
>      CGroup: /system.slice/xen.service
>              ??1279 /usr/lib/xen-4.17/bin/oxenstored --pid-file
> /run/xenstore.pid
>              ??1290 /usr/lib/xen-4.17/bin/xenconsoled --pid-file
> /run/xenconsoled.pid
>              ??1309 /usr/libexec/xen-qemu-system-i386 -xen-domid 0
> -xen-attach -name dom0 -nographic -M xenpv -daemonize -monitor none
> -serial none -parallel none -pidfile /run/qemu-dom0.pid
>
> Jan 25 14:11:42 osiris systemd[1]: Starting xen.service - LSB: Xen
> daemons...
> Jan 25 14:11:42 osiris xen[1203]: Starting Xen daemons: xenfs xenstored
> xenconsoled qemu.
> Jan 25 14:11:42 osiris systemd[1]: Started xen.service - LSB: Xen daemons.
>
> $ sudo cat /run/xenstore.pid /run/xenconsoled.pid /run/qemu-dom0.pid
> 1279
> 1290
> 1309
>
>
> I can't find any xen 4.17.3 packages in debian bookworm, from which
> repro did you get them?
>
> regards
>   Volker
>
>
>
>
> Am 24.01.24 um 22:12 schrieb Pry Mar:
>> Hello,
>>
>> https://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=tools/hotplug/Linux/init.d/xencommons.in;h=7fd6903b9868e27f855ba797a2529e6e2171d089;hb=refs/heads/staging-4.17 <https://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=tools/hotplug/Linux/init.d/xencommons.in;h=7fd6903b9868e27f855ba797a2529e6e2171d089;hb=refs/heads/staging-4.17>
>>
>> It seems your distro xen-4.17 uses the init scripts for xen services,
>> not systemd. The above branch in xen.git shows where/how xenconsoled
>> is started. It does
>> write a PID for xenconsoled.
>>
>> Note that the systemd service for xenconsoled has no such PID.
>> However, I suspect you have a stale PID for xenconsoled, check the
>> write time against the other xen PID's.
>>
>>  >ps aux | grep xen
>> root          41  0.0  0.0      0     0 ?        S    17:15   0:00
>> [xenbus]
>> root          42  0.0  0.0      0     0 ?        S    17:15   0:00
>> [xenwatch]
>> root          52  0.0  0.0      0     0 ?        S    17:15   0:00
>> [xen-balloon]
>> root         721  0.5  0.2   7508  3444 ?        S    17:15   0:00
>> /usr/sbin/xenstored --pid-file /var/run/xen/xenstored.pid
>> root         729  0.0  0.1  68784  2280 ?        Ssl  17:15   0:00
>> /usr/sbin/xenconsoled -i --log=none --log-dir=/var/log/xen/console
>> root         738  0.0  1.1 254580 16236 ?        Sl   17:15   0:00
>> /usr/bin/qemu-system-i386 -xen-domid 0 -xen-attach -name dom0
>> -nographic -M xenpv -daemonize -monitor /dev/null -serial /dev/null
>> -parallel /dev/null -nodefaults -no-user-config -pidfile
>> /var/run/xen/qemu-dom0.pid
>> root        1032  0.0  0.1  72136  2612 ?        Ssl  17:15   0:00
>> /usr/lib/xen-4.17/bin/xl create --quiet --defconfig /etc/xen/auto/a_jam22
>> root        1526  0.0  0.1  72136  2512 ?        Ssl  17:15   0:00
>> /usr/lib/xen-4.17/bin/xl create --quiet --defconfig /etc/xen/auto/b_booky
>> root        1899  0.0  0.1  72136  2660 ?        Ssl  17:15   0:00
>> /usr/lib/xen-4.17/bin/xl create --quiet --defconfig /etc/xen/auto/c_al9pv
>> root        2306  0.0  0.1  72136  2436 ?        Ssl  17:15   0:00
>> /usr/lib/xen-4.17/bin/xl create --quiet --defconfig /etc/xen/auto/d_al8pv
>> root        2732  0.0  0.1  72136  2552 ?        Ssl  17:15   0:00
>> /usr/lib/xen-4.17/bin/xl create --quiet --defconfig
>> /etc/xen/auto/e_fc37cnv
>> root        3070  0.0  0.1  72136  2512 ?        Ssl  17:15   0:00
>> /usr/lib/xen-4.17/bin/xl create --quiet --defconfig
>> /etc/xen/auto/h_pvbully
>> root        3545  0.0  0.1  72136  2664 ?        Ssl  17:15   0:00
>> /usr/lib/xen-4.17/bin/xl create --quiet --defconfig
>> /etc/xen/auto/j_ub2204
>> root        3928  0.0  0.1  72136  2464 ?        Ssl  17:15   0:00
>> /usr/lib/xen-4.17/bin/xl create --quiet --defconfig
>> /etc/xen/auto/k_noble1
>> root        3938  0.0  0.0   2788   172 ?        Ss   17:15   0:00
>> /usr/sbin/xenwatchdogd 30 15
>> root        4101  0.0  0.3  10004  4444 pts/4    S+   17:17   0:00
>> sudo ./dump_xen_trace.multi.4h tlviewer
>> root        4102  0.0  0.1   2576  1652 pts/4    S+   17:17   0:00 sh
>> ./dump_xen_trace.multi.4h tlviewer
>> root        4169  0.0  0.1   6652  2120 pts/4    S+   17:17   0:00
>> grep xen
>>
>> I have a build of xen-4.17.3 running on Bookworm that uses the systemd
>> services. See above.
>> https://repo.dynavirt.com/xen/debian/bookworm-nmu/4hx-q724/setup/xl-info-deb12.multi.html <https://repo.dynavirt.com/xen/debian/bookworm-nmu/4hx-q724/setup/xl-info-deb12.multi.html>
>>
>> cheers,
>> PryMar56
>