[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: xenconsoled defunct after xl create on fresh debian 12


  • To: xen-users@xxxxxxxxxxxxx
  • From: Volker Weber <volker@xxxxxxxxxxxxxxxxxx>
  • Date: Thu, 25 Jan 2024 15:17:12 +0100
  • Arc-authentication-results: i=1; strato.com; arc=none; dkim=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; t=1706192233; s=strato-dkim-0002; d=strato.com; h=In-Reply-To:References:To:Subject:From:Date:Message-ID:Cc:Date:From: Subject:Sender; bh=fGSjFw1Yw4OGqGF4ve9MQeU1RLqKz0LzOAMf6a+mQDg=; b=phwm8px5GJZ2KBh/O2UMdAAjvbr3Qu07JoYzNteEnjlwMFXBn1hKNEFjsOS/Z9abw2 ZthBrA2WNyv9tpZ1o+d0ZrD6bFq1JwZyKQ+SrXqTv80CrMvZox648nif34FPZ4iWU3dC J0Sy5fclB2XEJzSKnuNCPnX7f1j1s61KglSan+1Z9TaEnBVTOdWnOEpY0BbX4Y1LyiVW awD0h45bNdX6yeXNT24Qz5M47GMtNo2dKAtS5nvPXtPy8ejqLe4tEieOzpRi0DnEhhoW Llq1jJ9V89F9nU/Y93NL4tCFbYD+7Lsqpo4RaQJAlovyP0D0LJmFm53K4psN9//aVf7x BfGg==
  • Arc-seal: i=1; a=rsa-sha256; t=1706192233; cv=none; d=strato.com; s=strato-dkim-0002; b=JmRHBFfKkLA/CULUT0IxnhB92V0S8BAcdKwyMZPc4DszQtY8Xxm6GH4+Thc7AUkXru RPEbv38Q4+50A3kDValMgcR8LgDfkWnmBk17mc4yyIqDFQJK1nUWNcXiUy5xjQxKruWI NQ9uvqEAOtZB7S4o/ZdKPe2gcQCyC8PqcXz4GjxlIjJqMq3RvGGaK7lL60UeCp7S/fq1 oOKluFMbmVBlxNr1DOQscy3qvqxcUZkRf/mfLT0rA2ciRdqNmtTfy6zIFO0Ko+/HQ4/j Siac41DWw8fg4Xf4obY86hi0bAM5kYytwTov0XVE7Bzf1zCYVtcVfGoF+z6kf5C2lVip A1oQ==
  • Delivery-date: Fri, 26 Jan 2024 16:13:05 +0000
  • List-id: Xen user discussion <xen-users.lists.xenproject.org>

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



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.