[Pkg-xen-devel] Bug#808624: Invalid argument while starting daemon

[Giuseppe Sacco]

Package: xen-hypervisor-4.4-amd64
Version: 4.4.1-9+deb8u3
Severity: important

I just upgraded a machine used for hosting a few VM with Xen. The
machine was running debian squeeze, so I updated to wheezy and then
jessie. Xen is now version 4.4, cpu is 64 bits, dom0 is 32 bits
userland with 64 bits kernel 3.16.0-4-amd64.

Grub correctly load Xen and dom-0, in fact:
# cd /sys/hypervisor/version; cat major minor extra
4
4
.1

During boot, Xen does not start. This is its status in systemd log:

# systemctl status xen.service
● xen.service - LSB: Xen daemons
   Loaded: loaded (/etc/init.d/xen)
   Active: failed (Result: timeout) since lun 2015-12-21 15:34:04 CET; 38min ago
  Process: 28167 ExecStart=/etc/init.d/xen start (code=killed, signal=TERM)

dic 21 15:29:04 centrum xenstored[28191]: Checking store ...
dic 21 15:29:04 centrum xenstored[28191]: Checking store complete.
dic 21 15:29:04 centrum xenstored[28191]: Checking store ...
dic 21 15:29:04 centrum xenstored[28191]: Checking store complete.
dic 21 15:29:04 centrum xen[28167]: Starting Xen daemons: xenstored xenconsoled init-dom0FATAL: Failed to initialize dom0 state: Inappropriate ioctl for device
dic 21 15:34:04 centrum systemd[1]: xen.service start operation timed out. Terminating.
dic 21 15:34:04 centrum systemd[1]: Failed to start LSB: Xen daemons.
dic 21 15:34:04 centrum systemd[1]: Unit xen.service entered failed state.

Log files in /var/log/xen aren't touched: no information has been
printed there after debian upgrade.

Some operation take forever, like
centrum:/tmp# time xenstore-write "/local/domain/0/name" "Domain-0"
(never return: I killed it after 30 minutes)

and this xenstore-write command that take forever is the reason for
systemd setting the status as "timeout".

How may I solve, or better debug, this problem?

Thank you very much,
Giuseppe