Xen 4.5: can't create DomU guest on mustang(arm64)

Xen 4.5: can't create DomU guest on mustang(arm64)

[Ming Lei]

Hi Guys,

I just follow the guide in the link[1], and looks
I can boot Dom0 successfully on mustang, and the
xen 4.5 tools can be built OK on Dom0 side too.

But when I try to create domU with the following
commands:

    # losetup -f arm64-fs1.img
    # losetup -a
    /dev/loop0: [0802]:1318964 (/home/ubuntu/xt/arm64-fs1.img)

    # cat domu-test.cfg
    kernel = "./Image"
    memory = 512
    name = "ubuntu"
    vcpus = 2
    disk = [ 'phy:/dev/loop0,xvda,w' ]
    extra = 'console=hvc0 root=/dev/xvda rw earlyprintk=xen'

    # /etc/init.d/xencommons start || true
    # echo 9 > /proc/sysrq-trigger
    # export LIBXL_DEBUG_DUMP_DTB=guest.dtb
    # xl -vvv create domu-test.cfg

I saw the failures in [2], so could anyone give a hand on it?

Thanks in advance!


[1], http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/APMXGeneMustang

[2], log when creating domU
# /etc/init.d/xencommons start || true
Starting xenconsoled...
Starting QEMU as disk backend for dom0
Could not acquire pidfile: Inappropriate ioctl for device
# xl -v create domu-test.cfg
Parsing config from domu-test.cfg
domainbuilder: detail: xc_dom_allocate: cmdline="console=hvc0
root=/dev/xvda rw earlyprintk=xen", features="(null)"
domainbuilder: detail: xc_dom_kernel_file: filename="/home/ubuntu/xt/Image"
domainbuilder: detail: xc_dom_malloc_filemap    : 11403 kB
domainbuilder: detail: xc_dom_boot_xen_init: ver 4.5, caps
xen-3.0-aarch64 xen-3.0-armv7l
domainbuilder: detail: xc_dom_rambase_init: RAM starts at 40000
domainbuilder: detail: xc_dom_parse_image: called
domainbuilder: detail: xc_dom_find_loader: trying multiboot-binary loader ...
domainbuilder: detail: loader probe failed
domainbuilder: detail: xc_dom_find_loader: trying Linux zImage (ARM64)
loader ...
domainbuilder: detail: loader probe OK
domainbuilder: detail: xc_dom_parse_zimage64_kernel: called
domainbuilder: detail: xc_dom_parse_zimage64_kernel: xen-3.0-aarch64:
0x40080000 -> 0x40ba2e00
domainbuilder: detail: xc_dom_devicetree_mem: called
domainbuilder: detail: xc_dom_mem_init: mem 512 MB, pages 0x20000 pages, 4k each
domainbuilder: detail: xc_dom_mem_init: 0x20000 pages
domainbuilder: detail: xc_dom_boot_mem_init: called
domainbuilder: detail: set_mode: guest xen-3.0-aarch64, address size 64
domainbuilder: detail: xc_dom_malloc            : 1024 kB
domainbuilder: detail: populate_guest_memory: populating RAM @
0000000040000000-0000000060000000 (512MB)
domainbuilder: detail: populate_one_size: populated 0x100/0x100
entries with shift 9
domainbuilder: detail: arch_setup_meminit: placing boot modules at 0x48000000
domainbuilder: detail: arch_setup_meminit: devicetree: 0x48000000 -> 0x48001000
domainbuilder: detail: xc_dom_build_image: called
domainbuilder: detail: xc_dom_alloc_segment:   kernel       :
0x40080000 -> 0x40ba3000  (pfn 0x40080 + 0xb23 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn
0x40080+0xb23 at 0x7f7ab85000
domainbuilder: detail: xc_dom_load_zimage_kernel: called
domainbuilder: detail: xc_dom_load_zimage_kernel: kernel seg
0x40080000-0x40ba3000
domainbuilder: detail: xc_dom_load_zimage_kernel: copy 11677184 bytes
from blob 0x7f7b7a9000 to dst 0x7f7ab85000
domainbuilder: detail: xc_dom_alloc_segment:   devicetree   :
0x48000000 -> 0x48001000  (pfn 0x48000 + 0x1 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn
0x48000+0x1 at 0x7f7c626000
domainbuilder: detail: alloc_magic_pages: called
domainbuilder: detail: count_pgtables_arm: called
domainbuilder: detail: xc_dom_build_image  : virt_alloc_end : 0x48001000
domainbuilder: detail: xc_dom_build_image  : virt_pgtab_end : 0x0
domainbuilder: detail: xc_dom_boot_image: called
domainbuilder: detail: arch_setup_bootearly: doing nothing
domainbuilder: detail: xc_dom_compat_check: supported guest type:
xen-3.0-aarch64 <= matches
domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-armv7l
domainbuilder: detail: setup_pgtables_arm: called
domainbuilder: detail: clear_page: pfn 0x39000, mfn 0x39000
domainbuilder: detail: clear_page: pfn 0x39001, mfn 0x39001
domainbuilder: detail: start_info_arm: called
domainbuilder: detail: domain builder memory footprint
domainbuilder: detail:    allocated
domainbuilder: detail:       malloc             : 1093 kB
domainbuilder: detail:       anon mmap          : 0 bytes
domainbuilder: detail:    mapped
domainbuilder: detail:       file mmap          : 11403 kB
domainbuilder: detail:       domU mmap          : 11408 kB
domainbuilder: detail: vcpu_arm64: called
domainbuilder: detail: DTB 48000000
domainbuilder: detail: Initial state CPSR 0x1c5 PC 0x40080000
domainbuilder: detail: launch_vm: called, ctxt=0x7f7c62a004
domainbuilder: detail: xc_dom_release: called
libxl: error: libxl_device.c:950:device_backend_callback: unable to
add device with path /local/domain/0/backend/vbd/4/51712
libxl: error: libxl_create.c:1153:domcreate_launch_dm: unable to add
disk devices
libxl: error: libxl_device.c:950:device_backend_callback: unable to
remove device with path /local/domain/0/backend/vbd/4/51712
libxl: error: libxl.c:1640:devices_destroy_cb: libxl__devices_destroy
failed for 4


Thanks,
Ming Lei

Re: Xen 4.5: can't create DomU guest on mustang(arm64)

[Ming Lei]

On Thu, Feb 26, 2015 at 11:55 AM, Ming Lei <tom.leiming@gmail.com> wrote:
> Hi Guys,
>
> I just follow the guide in the link[1], and looks
> I can boot Dom0 successfully on mustang, and the
> xen 4.5 tools can be built OK on Dom0 side too.
>
> But when I try to create domU with the following
> commands:
>
>     # losetup -f arm64-fs1.img
>     # losetup -a
>     /dev/loop0: [0802]:1318964 (/home/ubuntu/xt/arm64-fs1.img)
>
>     # cat domu-test.cfg
>     kernel = "./Image"
>     memory = 512
>     name = "ubuntu"
>     vcpus = 2
>     disk = [ 'phy:/dev/loop0,xvda,w' ]
>     extra = 'console=hvc0 root=/dev/xvda rw earlyprintk=xen'
>
>     # /etc/init.d/xencommons start || true
>     # echo 9 > /proc/sysrq-trigger
>     # export LIBXL_DEBUG_DUMP_DTB=guest.dtb
>     # xl -vvv create domu-test.cfg
>
> I saw the failures in [2], so could anyone give a hand on it?

I just figured out the reason: xen-block backend drvier isn't built in
domU kernel. Once it is done, domU can be started successfully.

Sorry for the noise.

Thanks,
Ming Lei

Re: Xen 4.5: can't create DomU guest on mustang(arm64)

[Ming Lei]

On Thu, Feb 26, 2015 at 5:41 PM, Ming Lei <tom.leiming@gmail.com> wrote:
> On Thu, Feb 26, 2015 at 11:55 AM, Ming Lei <tom.leiming@gmail.com> wrote:
>> Hi Guys,
>>
>> I just follow the guide in the link[1], and looks
>> I can boot Dom0 successfully on mustang, and the
>> xen 4.5 tools can be built OK on Dom0 side too.
>>
>> But when I try to create domU with the following
>> commands:
>>
>>     # losetup -f arm64-fs1.img
>>     # losetup -a
>>     /dev/loop0: [0802]:1318964 (/home/ubuntu/xt/arm64-fs1.img)
>>
>>     # cat domu-test.cfg
>>     kernel = "./Image"
>>     memory = 512
>>     name = "ubuntu"
>>     vcpus = 2
>>     disk = [ 'phy:/dev/loop0,xvda,w' ]
>>     extra = 'console=hvc0 root=/dev/xvda rw earlyprintk=xen'
>>
>>     # /etc/init.d/xencommons start || true
>>     # echo 9 > /proc/sysrq-trigger
>>     # export LIBXL_DEBUG_DUMP_DTB=guest.dtb
>>     # xl -vvv create domu-test.cfg
>>
>> I saw the failures in [2], so could anyone give a hand on it?
>
> I just figured out the reason: xen-block backend drvier isn't built in
> domU kernel.

It should be dom0 kernel.


Thanks,
Ming Lei

Re: Xen 4.5: can't create DomU guest on mustang(arm64)

[Ian Campbell]

On Thu, 2015-02-26 at 11:55 +0800, Ming Lei wrote:
> libxl: error: libxl_device.c:950:device_backend_callback: unable to
> add device with path /local/domain/0/backend/vbd/4/51712
> libxl: error: libxl_create.c:1153:domcreate_launch_dm: unable to add
> disk devices
> libxl: error: libxl_device.c:950:device_backend_callback: unable to
> remove device with path /local/domain/0/backend/vbd/4/51712
> libxl: error: libxl.c:1640:devices_destroy_cb: libxl__devices_destroy
> failed for 4

This makes me think that either your kernel does not have blkback
enabled or the module is not loaded.

Ian.