Re: [Xen-devel] Pygrub on ARM64

[Sanjeev Pandita <spandita@xxxxxxx>]

Hi Ian/All,

Here is the -vvv output

[root@localhost xen]# xl -vvv create vm1
Parsing config from vm1
libxl: debug: libxl_create.c:1557:do_domain_create: ao 0xa175050:
create: how=(nil) callback=(nil) poller=0xa1750e0
libxl: debug: libxl_arm.c:59:libxl__arch_domain_prepare_config:
Configure the domain
libxl: debug: libxl_arm.c:62:libxl__arch_domain_prepare_config:  -
Allocate 0 SPIs
libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk
vdev=xvda spec.backend=unknown
libxl: debug: libxl_device.c:298:libxl__device_disk_set_backend: Disk
vdev=xvda, using backend phy
libxl: debug: libxl_create.c:945:initiate_domain_create: running bootloader
libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk
vdev=(null) spec.backend=phy
libxl: debug: libxl.c:3097:libxl__device_disk_local_initiate_attach:
locally attaching RAW disk /mnt/xen/CentOS-7-aarch64.img
libxl: debug: libxl_bootloader.c:412:bootloader_disk_attached_cb:
Config bootloader value: pygrub
libxl: debug: libxl_bootloader.c:428:bootloader_disk_attached_cb:
Checking for bootloader in libexec path: /usr/local/lib/xen/bin/pygrub
libxl: debug: libxl_create.c:1580:do_domain_create: ao 0xa175050:
inprogress: poller=0xa1750e0, flags=i
libxl: debug: libxl_event.c:639:libxl__ev_xswatch_register: watch
w=0xa16c4d0 wpath=/local/domain/25 token=3/0: register slotnum=3
libxl: debug: libxl_event.c:2183:libxl__ao_progress_report: ao
0xa175050: progress report: ignored
libxl: debug: libxl_bootloader.c:540:bootloader_gotptys: executing
bootloader: /usr/local/lib/xen/bin/pygrub
libxl: debug: libxl_bootloader.c:544:bootloader_gotptys:   bootloader
arg: /usr/local/lib/xen/bin/pygrub
libxl: debug: libxl_bootloader.c:544:bootloader_gotptys:   bootloader
arg: --args=root=/dev/xvda4 rw console=hvc0 earlyprintk=xen
libxl: debug: libxl_bootloader.c:544:bootloader_gotptys:   bootloader
arg: --output=/var/run/xen/bootloader.25.out
libxl: debug: libxl_bootloader.c:544:bootloader_gotptys:   bootloader
arg: --output-format=simple0
libxl: debug: libxl_bootloader.c:544:bootloader_gotptys:   bootloader
arg: --output-directory=/var/run/xen/bootloader.25.d
libxl: debug: libxl_bootloader.c:544:bootloader_gotptys:   bootloader
arg: /mnt/xen/CentOS-7-aarch64.img
libxl: debug: libxl_event.c:576:watchfd_callback: watch w=0xa16c4d0
wpath=/local/domain/25 token=3/0: event epath=/local/domain/25


(gets stuck here. no prints after this)


[root@localhost ~]# xl list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  2048     4     r-----    4358.2
vm1                                         25     0     0     --p---       0.0
[root@localhost ~]#


If I run the command manually it says OSError: no such file or directory .

[root@localhost ~]# /usr/local/lib/xen/bin/pygrub
--args=root=/dev/xvda4 rw console=hvc0 earlyprintk=xen
--output=/var/run/xen/bootloader.25.out --output-format=simple0
--output-directory=/var/run/xen/bootloader.25.d
/mnt/xen/CentOS-7-aarch64.img
Traceback (most recent call last):
  File "/usr/local/lib/xen/bin/pygrub", line 888, in <module>
    part_offs = get_partition_offsets(file)
  File "/usr/local/lib/xen/bin/pygrub", line 113, in get_partition_offsets
    image_type = identify_disk_image(file)
  File "/usr/local/lib/xen/bin/pygrub", line 56, in identify_disk_image
    fd = os.open(file, os.O_RDONLY)
OSError: [Errno 2] No such file or directory: 'rw'

[root@localhost ~]#  ls -al /mnt/xen/CentOS-7-aarch64.img
-rw-r--r-- 1 root root 12884901888 Feb 24 14:54 /mnt/xen/CentOS-7-aarch64.img
[root@localhost ~]#


Tried setting rw permissions to the file as well. Still no luck.


[root@localhost ~]#ls -al /mnt/xen/CentOS-7-aarch64.img
-rwxrwxrwx 1 root root 12884901888 Feb 24 14:54 /mnt/xen/CentOS-7-aarch64.img

[root@localhost ~]# /usr/local/lib/xen/bin/pygrub
--args=root=/dev/xvda4 rw console=hvc0 earlyprintk=xen
--output=/var/run/xen/bootloader.25.out --output-format=simple0
--output-directory=/var/run/xen/bootloader.25.d
/mnt/xen/CentOS-7-aarch64.img
Traceback (most recent call last):
  File "/usr/local/lib/xen/bin/pygrub", line 888, in <module>
    part_offs = get_partition_offsets(file)
  File "/usr/local/lib/xen/bin/pygrub", line 113, in get_partition_offsets
    image_type = identify_disk_image(file)
  File "/usr/local/lib/xen/bin/pygrub", line 56, in identify_disk_image
    fd = os.open(file, os.O_RDONLY)
OSError: [Errno 2] No such file or directory: 'rw'

Thanks,
Sanjeev



On Wed, Feb 24, 2016 at 3:57 PM, Ian Campbell <ian.campbell@xxxxxxxxxx> wrote:
> On Wed, 2016-02-24 at 15:52 +0530, Sanjeev Pandita wrote:
>> All,
>>
>> Does pygrub work with ARM64 ?
>
> It's not arch specific, so it should.
>
>> I am trying to boot the CentOS-7-aarch64.img (raw) using pygrub.I am
>> using the below config file and it is not working.
>
> Please post the full "xl -vvv create vm1" output.
>
>> [root@localhost xen]# cat vm1
>> name = "vm1"
>> uuid = "3fb78ba6-8182-484c-acf7-8faba9773f68"
>> disk = [ 'tap:raw:/mnt/xen/CentOS-7-aarch64.img,xvda,w' ]
>> memory = 512
>> bootloader="/usr/local/lib/xen/bin/pygrub"
>
> Can just be "pygrub" and xl will find the one which corresponds to the
> install.
>
>> extra = "root=/dev/xvda4 rw console=hvc0 earlyprintk=xen"
>> vif=[ 'mac=00:16:3e:01:01:01,bridge=br0' ]
>> In /var/log/xen the bootloader log is empty.
>> [root@localhost xen]# ls -al bootloader.24.log
>> -rw-r--r-- 1 root root 0 Feb 24 15:22 bootloader.24.log
>
> Are you sure domain 24 is the correct one corresponding to a failed
> attempt?
>
> In the xl -vvv output you should see it logging the exact pygrub command
> line it is going to use. If you run that manually what output does it
> produce?
>
> 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