Giuseppe Sacco
2015-Dec-21 15:31 UTC
[Pkg-xen-devel] Bug#808624: Invalid argument while starting daemon
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
Ian Campbell
2016-Jan-20 11:06 UTC
[Pkg-xen-devel] Bug#808624: Bug#808624: Invalid argument while starting daemon
Control: merge?369042 808624 On Mon, 2015-12-21 at 16:31 +0100, Giuseppe Sacco wrote:> 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.Unfortunately this is not a combination supported by Xen. Supported options are: 64-bit Xen, 64-bit dom0 kernel, 64-bit dom0 userspace 64-bit Xen, 32-bit dom0 kernel, 32-bit dom0 userspace You are using: 64-bit Xen, 64-bit dom0 kernel, 32-bit dom0 userspace which causes...> dic 21 15:29:04 centrum xen[28167]: Starting Xen daemons: xenstored > xenconsoled init-dom0FATAL: Failed to initialize dom0 state: > Inappropriate ioctl for device.... xenstored not to start, which in turn causes ...>? > and this xenstore-write command that take forever is the reason for > systemd setting the status as "timeout".... xenstore-write to hang trying to talk to the daemon. Therefore this is the same issue as #369042 (therefore merging). With this being unsupported upstream your options within Debian are either to switch to a 32-bit dom0 kernel (easiest) or to cross-grade your userspace to 64-bit (harder). Outside of Debian I'm not sure what fixes would be required to make this work upstream but I suppose you could try (by far the hardest option, not on the roadmap upstream AFAIK) Ian.
Debian Bug Tracking System
2016-Jan-20 11:09 UTC
[Pkg-xen-devel] Processed (with 1 error): Re: Bug#808624: Invalid argument while starting daemon
Processing control commands:> merge?369042 808624Bug #369042 [src:xen] 32-bit toolstack does not work on 64-bit kernel+hypervisor Bug #503287 [src:xen] 32-bit toolstack does not work on 64-bit kernel+hypervisor Bug #737613 [src:xen] 32-bit toolstack does not work on 64-bit kernel+hypervisor Unable to merge bugs because: severity of #808624 is 'important' not 'normal' package of #808624 is 'xen-hypervisor-4.4-amd64' not 'src:xen' Failed to merge 369042: Did not alter merged bugs. -- 369042: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=369042 503287: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503287 737613: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737613 808624: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808624 Debian Bug Tracking System Contact owner at bugs.debian.org with problems
Apparently Analagous Threads
- Processed: reassign 808624 to src:xen, forcibly merging 369042 808624
- Bug#737613: xen-hypervisor-4.3-amd: Xen not loading dom0 on Jessie - FATAL error on running /etc/init.d/xen
- Bug#737613: [Fwd: Debian Bug 737613]
- Bug#737613: Debian Bug 737613: Xen not loading dom0 on Jessie - FATAL error on running /etc/init.d/xen
- Processed: forcibly merging 369042 503287 ...