Re: [Xen-devel] Pygrub on ARM64

[Ian Campbell <ian.campbell@xxxxxxxxxx>]

On Thu, 2016-02-25 at 13:20 +0530, Sanjeev Pandita wrote:
> 
> Terminal 3: (manually running the pygrub command)
> [root@dhcp-194 xen]# export LD_LIBRARY_PATH=/usr/lib
> [root@dhcp-194 xen]# mkdir -p /var/run/xen/bootloader.2.d
> [root@dhcp-194 xen]# touch /var/run/xen/bootloader.2.out
> [root@dhcp-194 xen]# /usr/lib/xen/bin/pygrub --args="root=/dev/xvda4 rw
> console=hvc0 earlyprintk=xen" --output=/var/run/xen/bootloader.2.out --
> output-format=simple0 --output-directory=/var/run/xen/bootloader.2.d
> /mnt/xen/CentOS-7-aarch64.img
> 
> (nothing comes on console after this) 

I don't remember ever seeing pygrub fail silently in this way.

I think at this point I would be trying a few different things, firstly
using strace(1) on the pygrub invocation to see if I could see where it was
blocked. I think you can drop all of the arguments except for the image,
e.g.

    pygrub /mnt/xen/CentOS-7-aarch64.img

leading to

    strace -o pygrub.strace pygrub /mnt/xen/CentOS-7-aarch64.img

(maybe add -fff if it looks to be using threads)

Secondly manually mounting CentOS-7-aarch64.img (e.g. "mount -o loop etc",
or maybe kpartx -a first if the image has a partition table) to check it
really is some sort of sensible/readable image.

Ian.

> 
> Terminal4: (ls of the logs directory and files. All files are empty)
> [root@dhcp-194 ~]# cd /var/run/xen/
> [root@dhcp-194 xen]# ls
> bootloader.1.d  bootloader.1.out  bootloader.2.d  bootloader.2.out
> [root@dhcp-194 xen]# ls -al
> total 0
> drwxr-xr-x  4 root root  120 Feb 25 12:50 .
> drwxr-xr-x 35 root root 1100 Feb 25 10:00 ..
> drw-------  2 root root   40 Feb 25 12:07 bootloader.1.d
> -rw-------  1 root root    0 Feb 25 12:07 bootloader.1.out
> drwxr-xr-x  2 root root   40 Feb 25 12:50 bootloader.2.d
> -rw-r--r--  1 root root    0 Feb 25 12:50 bootloader.2.out
> [root@dhcp-194 xen]# ls -al bootloader.*
> -rw------- 1 root root  0 Feb 25 12:07 bootloader.1.out
> -rw-r--r-- 1 root root  0 Feb 25 12:50 bootloader.2.out
> bootloader.1.d:
> total 0
> drw------- 2 root root  40 Feb 25 12:07 .
> drwxr-xr-x 4 root root 120 Feb 25 12:50 ..
> bootloader.2.d:
> total 0
> drwxr-xr-x 2 root root  40 Feb 25 12:50 .
> drwxr-xr-x 4 root root 120 Feb 25 12:50 ..
> [root@dhcp-194 xen]#
> 
> 
> Issue #2:
> 
> While above things are in dangling state if I try to create another VM
> then a new DomU does not get create.
> 
> [root@dhcp-194 xen]# xl -vvv create vm8
> Parsing config from vm8
> <Nothing comes after the above line>
> 
> 
> If I kill pygrub from another terminal , press ctrl C in all other
> blocking terminals of vm1 and then start the vm8 , the vm8 boots fine.
> 
> Please let me know if am I missing anything in this sequence ?
> 
> Thanks,
> Sanjeev
>  
> >  Ian.
> > 
> > [*] normally this information would come from your grub.cfg in the
> > guest,
> > so you might want to remove the extra = in your guest cfg, or maybe you
> > are
> > deliberately overriding grub.cfg, in any case you are not yet at the
> > point
> > where this setting would make any difference.
> > 
> > Ian.
> > 
> 
> CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
> is for the sole use of the intended recipient(s) and contains information
> that is confidential and proprietary to Applied Micro Circuits
> Corporation or its subsidiaries. It is to be used solely for the purpose
> of furthering the parties' business relationship. All unauthorized
> review, use, disclosure or distribution is prohibited. If you are not the
> intended recipient, please contact the sender by reply e-mail and destroy
> all copies of the original message.

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