Xen - device model: spawn failed

joshdmiller · 2014-08-14 17:44:28

I have a Xen-based VM configuration which I've used without issue for well over a year. After running some updates and rebooting yesterday (either of which could be coincidental), the VM will no longer start:

# xl create leonids.xl.cfg 
Parsing config from leonids.xl.cfg
libxl: error: libxl_dm.c:1371:device_model_spawn_outcome: domain 1 device model: spawn failed (rc=-3)
libxl: error: libxl_create.c:1186:domcreate_devmodel_started: device model did not start: -3
libxl: error: libxl_dm.c:1475:kill_device_model: Device Model already exited

It probably shouldn't matter, but here's the basic config which I pared down in an attempt to resolve this issue:

name = "vm1"
memory = 3072
vif = [ 'bridge=xenbr0' ]
disk = [
  "phy:/dev/loop0p1,xvdb1,w"
]

builder = "hvm"
vnc = 1
vnclisten = '0.0.0.0'
vncdisplay = 1

And the loop device is created automatically by losetup after:

# modprobe loop max_parts=15

And I don't know if anything in this update would have caused it, but here's the pacman log anyway:

[2014-08-13 22:27] [PACMAN] Running 'pacman -Syu'
[2014-08-13 22:27] [PACMAN] synchronizing package lists
[2014-08-13 22:28] [PACMAN] starting full system upgrade
[2014-08-13 23:23] [PACMAN] upgraded bash (4.3.018-3 -> 4.3.022-1)
[2014-08-13 23:23] [PACMAN] upgraded chromium (36.0.1985.125-1 -> 36.0.1985.143-1)
[2014-08-13 23:23] [PACMAN] upgraded convertlit (1.8-6 -> 1.8-7)
[2014-08-13 23:23] [PACMAN] upgraded cracklib (2.9.0-2 -> 2.9.1-1)
[2014-08-13 23:23] [PACMAN] upgraded fakeroot (1.20-1 -> 1.20.1-1)
[2014-08-13 23:23] [PACMAN] upgraded gpgme (1.5.0-1 -> 1.5.1-1)
[2014-08-13 23:23] [PACMAN] upgraded kbd (2.0.1-1 -> 2.0.2-1)
[2014-08-13 23:23] [PACMAN] upgraded krb5 (1.12.1-1 -> 1.12.1-2)
[2014-08-13 23:23] [PACMAN] upgraded libiscsi (1.7.0-2 -> 1.12.0-1)
[2014-08-13 23:23] [PACMAN] upgraded libcacard (2.0.0-4 -> 2.1.0-2)
[2014-08-13 23:23] [PACMAN] upgraded libidn (1.28-2 -> 1.29-1)
[2014-08-13 23:23] [PACMAN] upgraded libmariadbclient (10.0.12-2 -> 10.0.13-1)
[2014-08-13 23:23] [PACMAN] upgraded xcb-proto (1.10-2 -> 1.11-1)
[2014-08-13 23:23] [PACMAN] upgraded libxcb (1.10-3 -> 1.11-1)
[2014-08-13 23:23] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2014-08-13 23:23] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio.  Please wait...
[2014-08-13 23:23] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2014-08-13 23:23] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2014-08-13 23:23] [ALPM-SCRIPTLET] ==> Starting build: 3.16.0-2-ARCH
[2014-08-13 23:23] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2014-08-13 23:23] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2014-08-13 23:23] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2014-08-13 23:23] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2014-08-13 23:23] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2014-08-13 23:23] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2014-08-13 23:23] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2014-08-13 23:23] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2014-08-13 23:23] [ALPM-SCRIPTLET] ==> ERROR: file not found: `fsck.btrfs'
[2014-08-13 23:23] [ALPM-SCRIPTLET] ==> WARNING: No fsck helpers found. fsck will not be run on boot.
[2014-08-13 23:23] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-08-13 23:23] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
[2014-08-13 23:23] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete.
[2014-08-13 23:23] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2014-08-13 23:23] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2014-08-13 23:23] [ALPM-SCRIPTLET] ==> Starting build: 3.16.0-2-ARCH
[2014-08-13 23:23] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2014-08-13 23:23] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2014-08-13 23:23] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2014-08-13 23:23] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2014-08-13 23:23] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2014-08-13 23:23] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2014-08-13 23:23] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2014-08-13 23:23] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2014-08-13 23:24] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2014-08-13 23:24] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-08-13 23:24] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
[2014-08-13 23:24] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-08-13 23:24] [PACMAN] upgraded linux (3.15.8-1 -> 3.16-2)
[2014-08-13 23:24] [PACMAN] upgraded lirc-utils (1:0.9.0-75 -> 1:0.9.0-76)
[2014-08-13 23:24] [PACMAN] upgraded mariadb-clients (10.0.12-2 -> 10.0.13-1)
[2014-08-13 23:24] [PACMAN] upgraded mariadb (10.0.12-2 -> 10.0.13-1)
[2014-08-13 23:24] [PACMAN] upgraded python-setuptools (1:5.4.2-1 -> 1:5.5.1-1)
[2014-08-13 23:24] [PACMAN] upgraded xfsprogs (3.2.0-1 -> 3.2.1-1)

Any ideas what may have caused this?

joshdmiller · 2014-08-19 20:58:29

As an update, this problem occurs exclusively with loop devices, whether created automatically through the loop module or manually through kpartx.

Laban · 2014-08-24 15:14:05

+1. Different dist but same problem with 4.4.0 and XL.

Arch Linux

#1 2014-08-14 17:44:28

Xen - device model: spawn failed

#2 2014-08-19 20:58:29

Re: Xen - device model: spawn failed

#3 2014-08-24 15:14:05

Re: Xen - device model: spawn failed

Board footer