From mboxrd@z Thu Jan 1 00:00:00 1970 From: Josep Subirats Subject: Re: Arndale: domU not booting Date: Wed, 23 Oct 2013 13:35:28 +0200 Message-ID: <5267B480.6020104@bsc.es> References: <5266A2A4.6030501@bsc.es> <1382461112.18283.39.camel@hastur.hellion.org.uk> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4474557510106944968==" Return-path: In-Reply-To: <1382461112.18283.39.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. --===============4474557510106944968== Content-Type: multipart/alternative; boundary="------------030305050309030800050907" This is a multi-part message in MIME format. --------------030305050309030800050907 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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. Should I also recompile the domU kernel with this option? I also gave execution rights to the "image" (kernel+xendtb) file, just in case. 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. 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 // //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// ///etc/xen/scripts/block-common.sh: line 2: $'\247\206\261p\252\036#t\207\216#\301T\317': command not found// ///etc/xen/scripts/block-common.sh: line 3: ��0��: Input/output error// ///etc/xen/scripts/block-common.sh: line 4: $'\313\361+K\364\260Z\375\271\314\005\275\366v\276\035\2776\032j\324KsoW\276OJ:': command not found// // //malloc: ../bash/subst.c:8485: assertion botched// //malloc: block on free list clobbered // //Aborting...libxl: error: libxl_exec.c:129:libxl_report_child_exitstatus: /etc/xen/scripts/block add [3155] died due to fatal signal Aborted // //libxl: error: libxl_create.c:935:domcreate_launch_dm: unable to add disk devices // //libxl: error: libxl_xshelp.c:212:libxl__xs_transaction_start: could not create xenstore transaction: Read-only file system // //libxl: error: libxl_device.c:798:libxl__initiate_device_remove: unable to start transaction // //libxl: error: libxl_xshelp.c:212:libxl__xs_transaction_start: could not create xenstore transaction: Read-only file system// //libxl: error: libxl.c:1456:devices_destroy_cb: libxl__devices_destroy failed for 1/ After this, the filesystem becomes read-only and I have to reboot the whole board. What can be happening? Many thanks for your help. Kind regards, Josep On 10/22/2013 06:58 PM, Ian Campbell wrote: > On Tue, 2013-10-22 at 18:07 +0200, Josep Subirats wrote: > >> root@arndale:/# /etc/init.d/xencommons start >> Starting C xenstored...WARNING: Failed to open connection to gnttab > Make sure you have all the Xen drivers enabled in your kernel, including > the gnttab one. Also make sure the modules are loaded, or better build > them into the kernel statically. > >> 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 > Your root filesystem seems to be missing the coreutils package (or > something else which provides dirname). The following errors all look > like fallout from this. > > 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 --------------030305050309030800050907 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit 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. Should I also recompile the domU kernel with this option? I also gave execution rights to the "image" (kernel+xendtb) file, just in case. 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. 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

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
/etc/xen/scripts/block-common.sh: line 2: $'\247\206\261p\252\036#t\207\216#\301T\317': command not found
/etc/xen/scripts/block-common.sh: line 3: ��0��: Input/output error
/etc/xen/scripts/block-common.sh: line 4: $'\313\361+K\364\260Z\375\271\314\005\275\366v\276\035\2776\032j\324KsoW\276OJ:': command not found

malloc: ../bash/subst.c:8485: assertion botched
malloc: block on free list clobbered                                                                                                                                
Aborting...libxl: error: libxl_exec.c:129:libxl_report_child_exitstatus: /etc/xen/scripts/block add [3155] died due to fatal signal Aborted                         
libxl: error: libxl_create.c:935:domcreate_launch_dm: unable to add disk devices                                                                                    
libxl: error: libxl_xshelp.c:212:libxl__xs_transaction_start: could not create xenstore transaction: Read-only file system                                          
libxl: error: libxl_device.c:798:libxl__initiate_device_remove: unable to start transaction                                                                         
libxl: error: libxl_xshelp.c:212:libxl__xs_transaction_start: could not create xenstore transaction: Read-only file system
libxl: error: libxl.c:1456:devices_destroy_cb: libxl__devices_destroy failed for 1

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

Many thanks for your help.

Kind regards,

Josep


On 10/22/2013 06:58 PM, Ian Campbell wrote:
On Tue, 2013-10-22 at 18:07 +0200, Josep Subirats wrote:


root@arndale:/# /etc/init.d/xencommons start
Starting C xenstored...WARNING: Failed to open connection to gnttab

Make sure you have all the Xen drivers enabled in your kernel, including
the gnttab one. Also make sure the modules are loaded, or better build
them into the kernel statically.
 

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

Your root filesystem seems to be missing the coreutils package (or
something else which provides dirname). The following errors all look
like fallout from this.

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
--------------030305050309030800050907-- --===============4474557510106944968== 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 --===============4474557510106944968==--