search for: domcreate_launch_dm

...line 4: /block-common.sh: No such file or directory// ///etc/xen/scripts/block: line 208: xenstore_read_default: command not found// //libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/block add [15289] exited with error status 1// //libxl: error: libxl_create.c:935:domcreate_launch_dm: unable to add disk devices// ///etc/xen/scripts/block: line 3: dirname: command not found// ///etc/xen/scripts/block: line 4: /block-common.sh: No such file or directory// ///etc/xen/scripts/block: line 208: xenstore_read_default: command not found// //libxl: error: libxl_exec.c:118:libxl_repor...

.../etc/xen/scripts/block add [-1] died due to fatal signal Killed Sep 09 09:29:21 host xendomains[948]: libxl: error: libxl_exec.c:129:libxl_report_child_exitstatus: /etc/xen/scripts/block add [-1] died due to fatal signal Killed Sep 09 09:29:21 host xendomains[948]: libxl: error: libxl_create.c:1054:domcreate_launch_dm: unable to add disk devices Services seem to get started in the correct order according to LSB headers in the init scripts: Sep 9 09:28:49 host systemd[1]: Starting LSB: Xen daemons... Sep 9 09:28:49 host xenstored: Checking store ... Sep 9 09:28:49 host xenstored: Checking store complete. Sep...

...xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000000fb 1GB PAGES: 0x0000000000000000 libxl: error: libxl_device.c:858:device_backend_callback: unable to disconnect device with path /local/domain/0/backend/vbd/4/51744 libxl: error: libxl_create.c:933:domcreate_launch_dm: unable to add disk devices libxl: error: libxl_dm.c:1239:libxl__destroy_device_model: could not find device-model''s pid for dom 4 libxl: error: libxl.c:1429:libxl__destroy_domid: libxl__destroy_device_model failed for 4 This error is very common in Xen 4.2.1-pre. I need to repeat create...

...cripts/block add [-1] died due to fatal signal Killed > Sep 09 09:29:21 host xendomains[948]: libxl: error: libxl_exec.c:129:libxl_report_child_exitstatus: /etc/xen/scripts/block add [-1] died due to fatal signal Killed > Sep 09 09:29:21 host xendomains[948]: libxl: error: libxl_create.c:1054:domcreate_launch_dm: unable to add disk devices I suppose these domains all start just fine by hand, because the race is well over by then... Do you get anything further under /var/log/xen when this occurs? In particular the xl files associated with the domain and /var/log/xen/xen-hotplug.log What does the disk con...

.... + + =item B<irqs=[ NUMBER, NUMBER, ... ]> Allow a guest to access specific physical IRQs. diff --git a/tools/libxl/libxl_create.c b/tools/libxl/libxl_create.c index ef17f05..6cb586b 100644 --- a/tools/libxl/libxl_create.c +++ b/tools/libxl/libxl_create.c @@ -963,6 +963,24 @@ static void domcreate_launch_dm(libxl__egc *egc, libxl__multidev *multidev, } } + for (i = 0; i < d_config->b_info.num_iomem; i++) { + libxl_iomem_range *io = &d_config->b_info.iomem[i]; + + LOG(DEBUG, "dom%d iomem %"PRIx64"-%"PRIx64, + domid, io->sta...

...s under +administrator control. + + =item B<irqs=[ NUMBER, NUMBER, ... ]> Allow a guest to access specific physical IRQs. diff --git a/tools/libxl/libxl_create.c b/tools/libxl/libxl_create.c --- a/tools/libxl/libxl_create.c +++ b/tools/libxl/libxl_create.c @@ -963,6 +963,24 @@ static void domcreate_launch_dm(libxl__egc *egc, libxl__multidev *multidev, } } + for (i = 0; i < d_config->b_info.num_iomem; i++) { + libxl_iomem_range *io = &d_config->b_info.iomem[i]; + + LOG(DEBUG, "dom%d iomem %"PRIx64"-%"PRIx64, + domid, io->sta...

...domsi.img is path from Storage domain file system. While creating new domain I got this console log- root@suksha:~/domsikernel# xl create -c domsi Parsing config from domsi libxl: error: libxl.c:2125:device_disk_add: failed to get blktap devpath for 0x1f9e9e0 libxl: error: libxl_create.c:932:domcreate_launch_dm: unable to add disk devices Second try: then I did changed disk param to- disk = [''access=w,vdev=xvda1,backend=storage,target=/root/domsi.img''] And I got this console log - [ 5.588091] XENBUS: Waiting for devices to initialise: 25s...20s...15s...10s...5s...0s...235s...2...

...domsi.img is path from Storage domain file system. While creating new domain I got this console log- root@suksha:~/domsikernel# xl create -c domsi Parsing config from domsi libxl: error: libxl.c:2125:device_disk_add: failed to get blktap devpath for 0x1f9e9e0 libxl: error: libxl_create.c:932:domcreate_launch_dm: unable to add disk devices Second try: then I did changed disk param to- disk = [''access=w,vdev=xvda1,backend=storage,target=/root/domsi.img''] And I got this console log - [ 5.588091] XENBUS: Waiting for devices to initialise: 25s...20s...15s...10s...5s...0s...235s...2...

Grant references for the xenstore and xenconsole shared pages exist, but currently only xenstore uses these references. Change the xenconsole daemon to prefer using the grant reference over map_foreign_range when mapping the shared console ring. This allows xenconsoled to be run in a domain other than dom0 if set up correctly - for libxl, the xenstore path /tool/xenconsoled/domid specifies the

...pecific Options The following options apply only to Paravirtual guests. diff -r ccbee5bcb31b -r ddde6c2c45de tools/libxl/libxl_create.c --- a/tools/libxl/libxl_create.c Fri Aug 31 12:03:55 2012 +0100 +++ b/tools/libxl/libxl_create.c Fri Aug 31 16:54:01 2012 +0100 @@ -933,6 +933,36 @@ static void domcreate_launch_dm(libxl__e LOG(ERROR, "unable to add disk devices"); goto error_out; } + + for (i = 0; i < d_config->b_info.num_ioports; i++) { + libxl_ioport_range *io = &d_config->b_info.ioports[i]; + + LOG(DEBUG, "dom%d ioports %"PRIx32&quot...

(moving to xen-devel, xen-arm is for the older PV ARM port) On Tue, 2013-06-25 at 23:59 +0000, Eric Trudeau wrote: > Hi, I am trying to build the XEN tools for our port of XEN to our > Cortex A15-based platform. > > I am using the repo at git://xenbits.xenproject.org/xen.git to > cross-compile the tools into our rootfs. Which branch/changeset are you using? I've heard that