Mailing List Archive

Update and error on QMP socket
Hello,

today i update (compile) my Debian Bullseye Server from xen 4.15.1 to
4.16.0 and i see a fail message when i start my DomU's.

Fail:

arsing config from /etc/xen/domU.cfg
libxl: error: libxl_qmp.c:1400:qmp_ev_fd_callback: Domain 1:error on QMP
socket: Connection reset by peer
libxl: error: libxl_qmp.c:1439:qmp_ev_fd_callback: Domain 1:Error
happened with the QMP connection to QEMU
libxl: error: libxl_dm.c:3351:device_model_postconfig_done: Domain
1:Post DM startup configs failed, rc=-26
libxl: error: libxl_create.c:1867:domcreate_devmodel_started: Domain
1:device model did not start: -26
libxl: error: libxl_aoutils.c:646:libxl__kill_xs_path: Device Model
already exited
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

With following steps:

- download xen-4.16.0.tar.gz

- untar

- ./configure --enable-systemd

- make PYTHON=/usr/bin/python3 -j8 dist

- make PYTHON=/usr/bin/python3 -j8 world

- stop the xen services (xen-qemu-dom0-disk-backend.service,
xen-init-dom0.service, xenconsoled.service, xenstored.service,
xendomains.service)

- make PYTHON=/usr/bin/python3 -j8 install

- reboot server

Have anyone a idea what is here happend? And the important question, how
can i solve the problem?

Thank you very much.
re: Update and error on QMP socket [ In reply to ]
Ronny,

<quote>
today i update (compile) my Debian Bullseye Server from xen 4.15.1 to
4.16.0 and i see a fail message when i start my DomU's.

Fail:

arsing config from /etc/xen/domU.cfg
libxl: error: libxl_qmp.c:1400:qmp_ev_fd_callback: Domain 1:error on QMP
</quote>

its a major version change to get to xen-4.16.0 from xen-4.15.1., not an update.
The qemu-xen build has a new meson build system, with extra build-deps.
You need: meson ninja-build liblzo2-dev

New is libxenstore.so.4, while your system might still have
libxenstore.so.3 in tree.

If xen-qemu-dom0-disk-backend.service never started you might get the
shown error.
systemctl status xen-qemu-dom0-disk-backend.service

In my Bullseye 4.16.0 build
qemu-system-i386 is 14.5 MB.

regards,
PryMar56