[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Arndale: domU not booting

  • To: xen-devel <xen-devel@xxxxxxxxxxxxx>
  • From: Josep Subirats <josep.subirats@xxxxxx>
  • Date: Tue, 22 Oct 2013 18:10:55 +0200
  • Delivery-date: Tue, 22 Oct 2013 16:11:15 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

I just observed the following output in the serial console, too:

[ 3112.311649] platform 122f0000.sata: Driver exynos-sata requests probe deferral
[ 3113.060272] attempt to access beyond end of device
[ 3113.063630] mmcblk1p1: rw=0, want=15886903136, limit=30210048
[ 3113.069404] attempt to access beyond end of device
[ 3113.074168] mmcblk1p1: rw=0, want=15886903136, limit=30210048
udevd[15288]: '/sbin/modprobe -b xen-backend:vbd' [15290] terminated by signal 7 (Bus error)

udevd[15302]: failed to execute '/etc/xen/scripts/xen-hotplug-cleanup' '/etc/xen/scripts/xen-hotplug-cleanup': Exec format error

[ 3113.272567] Failed to unmap pfn:a7525 rc:-2
INIT: Id "T0" respawning too fast: disabled for 5 minutes
[ 3339.357270] EXT3-fs error (device mmcblk1p1): ext3_lookup: deleted inode referenced: 814983
[ 3339.364160] Aborting journal on device mmcblk1p1.
[ 3340.185603] EXT3-fs (mmcblk1p1): error: remounting filesystem read-only



On 10/22/2013 06:07 PM, Josep Subirats wrote:
Dear all,

I followed the steps described in the wiki in order to get an Arnadle board running Xen, but I'm having trouble in starting a domU. Let me describe you the steps I followed. Sorry for such a long mail, but I think that a verbose description is necessary so you can point me what I'm doing wrong.

I couldn't boot properly over the network. This is why I modified the boot script so everything was loaded from the microSD (assuming it only contains one partition, which starts at sector 10240 and has all the necessary files in it at its root, along with the filesystem). To achieve it, simply take the source file I attach in this mail and convert it to an img file with:

mkimage -T script -C none -d load-xen-mmc.scr.txt load-xen-mmc.img

Then set up the environment variables in the board with:

setenv xen_addr_r 0x50000000
setenv kernel_addr_r 0x60000000
setenv dtb_addr_r 0x42000000
setenv script_addr_r 0x40080000

setenv bootcmd_load_linux_mmc 'ext2load mmc 0:1 $kernel_addr_r /zImage'
setenv bootcmd_load_xen_mmc 'ext2load mmc 0:1 $xen_addr_r /xen-uImage'
setenv bootcmd_load_dtb_mmc 'ext2load mmc 0:1 $dtb_addr_r /exynos5250-arndale.dtb'
setenv bootcmd_load_script_mmc 'ext2load mmc 0:1 $script_addr_r /load-xen-mmc.img'

setenv bootcmd 'run bootcmd_load_script_mmc; source $script_addr_r'
setenv xen_bootargs 'sync_console console=dtuart dtuart=/serial@12C20000'
setenv dom0_bootargs 'console=hvc0 ignore_loglevel psci=enable clk_ignore_unused root=/dev/mmcblk1p1 rw rootwait earlyprintk'

Save the changes with saveenv and simply boot.

At this point, I was able to launch the kernel and Xen successfully, and to log into the dom0. I couldn't find any reference on the exact steps to follow in order to be able to execute the "xl" command properly, as the wiki only says that a native compilation of the tools is necessary. So, what I did was to copy the xen source code in the board and compiled it with "make install-tools" (after running ./configure and installing the required packages).

I had to modify some library paths (apend "include /usr/local/lib/" to /etc/ld.so.conf and run ldconfig), start xencommons manually (/etc/init.d/xencommons start) and finally I've been able to run "xl list". Nevertheless, when xencommons is started, it outputs:

root@arndale:/# /etc/init.d/xencommons start
Starting C xenstored...WARNING: Failed to open connection to gnttab
Setting domain 0 name...
Starting xenconsoled...
Starting QEMU as disk backend for dom0
/etc/init.d/xencommons: line 120: /usr/local/lib/xen/bin/qemu-system-i386: No such file or directory

At this point, xl list displays:

root@arndale:/# xl list

Then I tried to create the VM described in the wiki, but to no avail. I copied all the necessary files, concatenated the domU kernel with the xenvm dtb, but in the end I get the following output:

root@arndale:~# xl create -c vmDescriptor.cfg
Parsing config from vmDescriptor.cfg
/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_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_report_child_exitstatus: /etc/xen/scripts/block remove [15297] exited with error status 1

Could you please tell me what is happening? Is there a step I'm not taking into consideration?

Many thanks. Best regards,

Josep Subirats

WARNING / LEGAL TEXT: This message is intended only for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential, proprietary, or exempt from disclosure under applicable law. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, you are strictly prohibited from disclosing, distributing, copying, or in any way using this message. If you have received this communication in error, please notify the sender and destroy and delete any copies you may have received.

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.