From mboxrd@z Thu Jan 1 00:00:00 1970 From: Josep Subirats Subject: Re: Arndale: domU not booting Date: Wed, 23 Oct 2013 17:09:24 +0200 Message-ID: <5267E6A4.4030602@bsc.es> References: <5266A2A4.6030501@bsc.es> <1382461112.18283.39.camel@hastur.hellion.org.uk> <5267B480.6020104@bsc.es> <1382535103.22417.26.camel@hastur.hellion.org.uk> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0408905122196865698==" Return-path: In-Reply-To: <1382535103.22417.26.camel@hastur.hellion.org.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: xen-devel List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --===============0408905122196865698== Content-Type: multipart/alternative; boundary="------------060908070702070200080204" This is a multi-part message in MIME format. --------------060908070702070200080204 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Dear Mr. Campbell, Thanks again for your answers. I restored the filesystem to a version I had before installing qemu in it. Upon start, this is what I do (no strange symbols now :) ): /root@arndale:~/vmTest# /etc/init.d/xencommons start// //Starting C xenstored...// //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// //root@arndale:~/vmTest# /etc/init.d/xendomains start// //root@arndale:~/vmTest# cat vmTest.cfg // //kernel = "/root/vmTest/image"// //memory = 128// //name = "win"// //vcpus = 1// //disk = [ 'phy:/dev/loop0,xvda,w' ]// //root@arndale:~/vmTest# xl create -c vmTest.cfg // //Parsing config from vmTest.cfg// ///etc/xen/scripts/block: 1: /etc/xen/scripts/block: Syntax error: word unexpected (expecting ")")// //libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/block add [3191] exited with error status 2// //libxl: error: libxl_create.c:935:domcreate_launch_dm: unable to add disk devices // ///etc/xen/scripts/block: 1: /etc/xen/scripts/block: Syntax error: word unexpected (expecting ")") // //libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/block remove [3396] exited with error status 2/ On the other hand, I get the following in the serial console: /[ 158.542759] Failed to unmap pfn:a7b2b rc:-2// //[ 158.545652] Failed to unmap pfn:a7b29 rc:-2// //[...]// //[ 162.646972] Failed to unmap pfn:a5de3 rc:-2// //[ 162.657145] Failed to unmap pfn:a5d27 rc:-2// //[ 162.691653] 6ahci: SSS flag set, parallel bus scan disabled// //[ 162.695915] platform 122f0000.sata: Driver exynos-sata requests probe deferral// //[ 162.833711] request_module: runaway loop modprobe binfmt-0000// //[ 162.833715] request_module: runaway loop modprobe binfmt-0000// //udevd[3194]: failed to execute '/etc/xen/scripts/block' '/etc/xen/scripts/block add': Exec format error// // //[ 163.250660] request_module: runaway loop modprobe binfmt-0000// //[ 163.254054] request_module: runaway loop modprobe binfmt-0000// //udevd[3393]: failed to execute '/etc/xen/scripts/block' '/etc/xen/scripts/block remove': Exec format error// // //(XEN) mm.c:1250:d0 gnttab_mark_dirty not implemented yet// //INIT: Id "T0" respawning too fast: disabled for 5 minutes// //[ 401.466716] asix 3-3.2.4:1.0 eth0: asix_rx_fixup() Bad Header Length 0x0, offset 4// //[ 403.469518] asix 3-3.2.4:1.0 eth0: asix_rx_fixup() Bad Header Length 0x0, offset 4// //[ 409.284223] asix 3-3.2.4:1.0 eth0: asix_rx_fixup() Bad Header Length 0x0, offset 4// //[ 438.824151] asix 3-3.2.4:1.0 eth0: asix_rx_fixup() Bad Header Length 0x76f3, offset 4// //[ 443.158425] asix 3-3.2.4:1.0 eth0: asix_rx_fixup() Bad Header Length 0x0, offset 4// //[ 443.358909] asix 3-3.2.4:1.0 eth0: asix_rx_fixup() Bad Header Length 0x0, offset 4// //[ 443.760255] asix 3-3.2.4:1.0 eth0: asix_rx_fixup() Bad Header Length 0x0, offset 4// //[ 444.562832] asix 3-3.2.4:1.0 eth0: asix_rx_fixup() Bad Header Length 0x0, offset 4// //[ 446.171803] asix 3-3.2.4:1.0 eth0: asix_rx_fixup() Bad Header Length 0x919376ea, offset 4// //[ 448.091583] asix 3-3.2.4:1.0 eth0: asix_rx_fixup() Bad Header Length 0x72636a2e, offset 4// //[ 449.075213] asix 3-3.2.4:1.0 eth0: asix_rx_fixup() Bad Header Length 0x0, offset 4/ And it goes on like this... Is it normal that I don't have xend under /etc/init.d? Many thanks and best regards, Josep On 10/23/2013 03:31 PM, Ian Campbell wrote: > On Wed, 2013-10-23 at 13:35 +0200, Josep Subirats wrote: >> Dear Mr. Campbell, >> >> Many thanks for your answer. I recompiled the dom0 kernel with GNTDEV >> (couldn't find gnttab, were you referring to gntdev?) built into the >> kernel, and any other XEN driver. > It looks like the message has gone, so you've got the right one, > >> Should I also recompile the domU kernel with this option? > Not for your use case (i.e. getting a basic domU running). > >> I also gave execution rights to the "image" (kernel+xendtb) file, >> just in case. > There is no need, but it is harmless enough to do so. > >> I installed qemu-system and qemu-utils and >> linked /usr/local/lib/xen/bin/qemu-system-i386 to the path where >> qemu-system-i386 was actually located. > This wasn't necessary. The warning is benign. > >> When I boot, I execute: >> >> root@arndale:~/vmTest# /etc/init.d/xencommons start >> Starting C xenstored... >> Setting domain 0 name... >> Starting xenconsoled... >> Starting QEMU as disk backend for dom0 >> Option xen-domid not supported for this target > What does your disk stanza look like? Currently only "phy" type ones are > supported on ARM. It looks like you are using something wihch wants to > use a qemu backend, which is not something the rest of us have tried > yet. I recommend using either a physical device or /dev/loop for the > time being > >> root@arndale:~/vmTest# /etc/init.d/xendomains start >> >> What I now get when I try to create the VM is: >> >> root@arndale:~/vmTest# xl create -c vmTest.cfg >> Parsing config from vmTest.cfg >> /etc/xen/scripts/block-common.sh: line 1: Jն�:���ʗ/_y�^�����A�: No >> such file or directory > Something is very wrong/corrupted with your root filesystem and or the > device underlying it. > >> After this, the filesystem becomes read-only and I have to reboot the >> whole board. What can be happening? > My first impression is that your disk or mmc or whatever is busy dying. > > Ian. > > 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. http://www.bsc.es/disclaimer --------------060908070702070200080204 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Dear Mr. Campbell,

Thanks again for your answers. I restored the filesystem to a version I had before installing qemu in it. Upon start, this is what I do (no strange symbols now :) ):

root@arndale:~/vmTest# /etc/init.d/xencommons start
Starting C xenstored...
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
root@arndale:~/vmTest# /etc/init.d/xendomains start
root@arndale:~/vmTest# cat vmTest.cfg
kernel = "/root/vmTest/image"
memory = 128
name = "win"
vcpus = 1
disk = [ 'phy:/dev/loop0,xvda,w' ]
root@arndale:~/vmTest# xl create -c vmTest.cfg
Parsing config from vmTest.cfg
/etc/xen/scripts/block: 1: /etc/xen/scripts/block: Syntax error: word unexpected (expecting ")")
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/block add [3191] exited with error status 2
libxl: error: libxl_create.c:935:domcreate_launch_dm: unable to add disk devices                                                                                    
/etc/xen/scripts/block: 1: /etc/xen/scripts/block: Syntax error: word unexpected (expecting ")")                                                                    
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/block remove [3396] exited with error status 2

On the other hand, I get the following in the serial console:

[  158.542759] Failed to unmap pfn:a7b2b rc:-2
[  158.545652] Failed to unmap pfn:a7b29 rc:-2
[...]
[  162.646972] Failed to unmap pfn:a5de3 rc:-2
[  162.657145] Failed to unmap pfn:a5d27 rc:-2
[  162.691653] 6ahci: SSS flag set, parallel bus scan disabled
[  162.695915] platform 122f0000.sata: Driver exynos-sata requests probe deferral
[  162.833711] request_module: runaway loop modprobe binfmt-0000
[  162.833715] request_module: runaway loop modprobe binfmt-0000
udevd[3194]: failed to execute '/etc/xen/scripts/block' '/etc/xen/scripts/block add': Exec format error

[  163.250660] request_module: runaway loop modprobe binfmt-0000
[  163.254054] request_module: runaway loop modprobe binfmt-0000
udevd[3393]: failed to execute '/etc/xen/scripts/block' '/etc/xen/scripts/block remove': Exec format error

(XEN) mm.c:1250:d0 gnttab_mark_dirty not implemented yet
INIT: Id "T0" respawning too fast: disabled for 5 minutes
[  401.466716] asix 3-3.2.4:1.0 eth0: asix_rx_fixup() Bad Header Length 0x0, offset 4
[  403.469518] asix 3-3.2.4:1.0 eth0: asix_rx_fixup() Bad Header Length 0x0, offset 4
[  409.284223] asix 3-3.2.4:1.0 eth0: asix_rx_fixup() Bad Header Length 0x0, offset 4
[  438.824151] asix 3-3.2.4:1.0 eth0: asix_rx_fixup() Bad Header Length 0x76f3, offset 4
[  443.158425] asix 3-3.2.4:1.0 eth0: asix_rx_fixup() Bad Header Length 0x0, offset 4
[  443.358909] asix 3-3.2.4:1.0 eth0: asix_rx_fixup() Bad Header Length 0x0, offset 4
[  443.760255] asix 3-3.2.4:1.0 eth0: asix_rx_fixup() Bad Header Length 0x0, offset 4
[  444.562832] asix 3-3.2.4:1.0 eth0: asix_rx_fixup() Bad Header Length 0x0, offset 4
[  446.171803] asix 3-3.2.4:1.0 eth0: asix_rx_fixup() Bad Header Length 0x919376ea, offset 4
[  448.091583] asix 3-3.2.4:1.0 eth0: asix_rx_fixup() Bad Header Length 0x72636a2e, offset 4
[  449.075213] asix 3-3.2.4:1.0 eth0: asix_rx_fixup() Bad Header Length 0x0, offset 4

And it goes on like this... Is it normal that I don't have xend under /etc/init.d?

Many thanks and best regards,

Josep

On 10/23/2013 03:31 PM, Ian Campbell wrote:
On Wed, 2013-10-23 at 13:35 +0200, Josep Subirats wrote:

Dear Mr. Campbell,

Many thanks for your answer. I recompiled the dom0 kernel with GNTDEV
(couldn't find gnttab, were you referring to gntdev?) built into the
kernel, and any other XEN driver.

It looks like the message has gone, so you've got the right one,


 Should I also recompile the domU kernel with this option?

Not for your use case (i.e. getting a basic domU running).


 I also gave execution rights to the "image" (kernel+xendtb) file,
just in case.

There is no need, but it is harmless enough to do so.


 I installed qemu-system and qemu-utils and
linked /usr/local/lib/xen/bin/qemu-system-i386 to the path where
qemu-system-i386 was actually located.

This wasn't necessary. The warning is benign.


 When I boot, I execute:

root@arndale:~/vmTest# /etc/init.d/xencommons start
Starting C xenstored...
Setting domain 0 name...
Starting xenconsoled...
Starting QEMU as disk backend for dom0
Option xen-domid not supported for this target

What does your disk stanza look like? Currently only "phy" type ones are
supported on ARM. It looks like you are using something wihch wants to
use a qemu backend, which is not something the rest of us have tried
yet. I recommend using either a physical device or /dev/loop for the
time being
 

root@arndale:~/vmTest# /etc/init.d/xendomains start

What I now get when I try to create the VM is:

root@arndale:~/vmTest# xl create -c vmTest.cfg 
Parsing config from vmTest.cfg
/etc/xen/scripts/block-common.sh: line 1: Jն�:���ʗ/_y�^�����A�: No
such file or directory

Something is very wrong/corrupted with your root filesystem and or the
device underlying it.


After this, the filesystem becomes read-only and I have to reboot the
whole board. What can be happening?

My first impression is that your disk or mmc or whatever is busy dying.

Ian.



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.

http://www.bsc.es/disclaimer
--------------060908070702070200080204-- --===============0408905122196865698== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============0408905122196865698==--