Re: Arndale: domU not booting

[Josep Subirats <josep.subirats@bsc.es>]

[-- Attachment #1.1: Type: text/plain, Size: 6199 bytes --]

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

[-- Attachment #1.2: Type: text/html, Size: 8691 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel