xenconsoled defunct after xl create on fresh debian 12

[Volker Weber <xen-users@xxxxxxxxxxxxxxxxxx>]

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