I am running xen-git 4.4. To start my domain with systemd I softlinked my config file (/etc/xen/conf/utm9.cfg) to /etc/xen/auto and enabled xendomains in systemd. My VM doesn't start successfully and I see the following in the journal:
Aug 23 19:14:23 adamwest xendomains: /etc/xen/scripts/xendomains: line 29: LOCKFILE: command not found Aug 23 19:14:23 adamwest xendomains: touch: cannot touch '': No such file or directory Aug 23 19:14:23 adamwest xendomains: Starting auto Xen domains Aug 23 19:14:23 adamwest xendomains: utm9.cfg: libxl: error: libxl_exec.c:129:libxl_report_child_exitstatus: /etc/xen/scripts/block add  died due to fatal signal Killed Aug 23 19:14:23 adamwest xendomains: libxl: error: libxl_create.c:948:domcreate_launch_dm: unable to add disk devices Aug 23 19:14:23 adamwest xendomains: libxl: error: libxl_dm.c:1331:libxl__destroy_device_model: could not find device-model's pid for dom 1 Aug 23 19:14:23 adamwest xendomains: libxl: error: libxl.c:1422:libxl__destroy_domid: libxl__destroy_device_model failed for 1 Aug 23 19:14:23 adamwest xendomains: ..failed
It appears that it can't see it's disk (odd as it should be /dev/sda6, the same drive it is booting from).
My config looks like so:
# ===================================================================== # Example HVM guest configuration # ===================================================================== # # This is a fairly minimal example of what is required for an # HVM guest. For a more complete guide see xl.cfg(5) #kernel = '/usr/lib/xen/boot/hvmloader' # This configures an HVM rather than PV guest builder = "hvm" # Guest name name = "utm9" # 128-bit UUID for the domain as a hexadecimal number. # Use "uuidgen" to generate one if required. # The default behavior is to generate a new UUID each time the guest is started. #uuid = "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" # Enable Microsoft Hyper-V compatibile paravirtualisation / # enlightenment interfaces. Turning this on can improve Windows guest # performance and is therefore recommended #viridian = 1 # Initial memory allocation (MB) memory = 4096 # Maximum memory (MB) # If this is greater than `memory' then the slack will start ballooned # (this assumes guest kernel support for ballooning) maxmem = 4096 # Number of VCPUS vcpus = 1 # Network devices # A list of 'vifspec' entries as described in # docs/misc/xl-network-configuration.markdown vif = [ 'mac=08:0b:27:c2:b7:e4,model=e1000,bridge=xenbr0', 'mac=08:0b:27:20:09:59,model=e1000,bridge=xenbr1' ] # Disk Devices # A list of `diskspec' entries as described in # docs/misc/xl-disk-configuration.txt disk = [ '/dev/sda6,raw,hda,w' ] #device_model = 'qemu-dm' # Guest VGA console configuration, either SDL or VNC sdl = 0 vnc = 1 vnclisten="10.144.0.255" vncpasswd=*CENSORED* usbdevice='tablet' acpi=1 apic=1 stdvga=0 serial='pty' on_xend_stop = 'shutdown' on_xend_start = 'start'
Once it is booted fully I can run sudo systemctl start xendomains and everything is fine... Any ideas on why this would happen? It is very annoying to have to manually log in each boot to start the Xen dom.
Last edited by chetwisniewski (2014-03-06 17:10:44)
Switched back to regular Xen after a rebuild and all if working as expected... Not really solved, but no longer an issue.