All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Chen <Wei.Chen@arm.com>
To: Marco Cacre <marco.cacre@gmail.com>, xen-devel@lists.xenproject.org
Subject: Re: Problem creating domU guest on arm64
Date: Wed, 20 Apr 2022 09:55:12 +0800	[thread overview]
Message-ID: <5e7ded0e-36f6-2a0a-4dab-30d39e649c05@arm.com> (raw)
In-Reply-To: <CAGHctbYx6sspA__OmKyumU+WkhzEsDpLstyhRDM9Kbc696Co7Q@mail.gmail.com>

Hi Marco,

On 2022/4/15 18:56, Marco Cacre wrote:
> Hi all,
> 
> I'm facing always the same problem (described below) trying to create a 
> Xen guest domain on rockpro64 (arm64).
> 
> I have successfully built uboot, xen (4.14.4) and dom0 linux kernel with 
> xen tool stack, these two last starting from buildroot (with linux 
> kernel version 5.15.33 and xen toolstack version 4.14.4)
> 
> These are the process of Xen:
> 
> 177 root    /usr/sbin/xenwatchdogd 30 15
> 203 root    /usr/sbin/xenstored --pid-file /var/run/xen/xenstored.pid
> 208 root    /usr/sbin/xenconsoled --pid-file=/var/run/xen/xenconsoled.pid
> 214 root    /usr/lib/xen/bin/qemu-system-i386 -xen-domid 0 -xen-attach 
> -name dom0 -nographic -M xenpv -daemonize -monitor /dev/null 
> -serial/dev/nul -parallel/dev/null -pidfile/var/run/xen/qemu-dom0.pid
> 
> and the drivers loaded as a module:
> # lsmod
> Module                  Size  Used by    Tainted: G
> xen_netback            65536  0
> xen_blkback            49152  0
> 
> Xen and dom0 Image boot up successfully, at the end:
> ================================================
>  >xl list
> Name                                        ID  Mem VCPUs State Time(s)
> Domain-0                                    0  1024    2    r-----    4000.3
> 
> # uname -a
> Linux rockpro64 5.15.33 #3 SMP PREEMPT Fri Apr 15 11:01:37 CEST 2022 
> aarch64 GNU/Linux
> ================================================
> 
> when I try to create a domU domain I have problem with disk backend, I 
> have made several attempts trying with different domU linux and I always 
> get the following error :
> 
> ================================================
> Parsing config from ./alpine_xen_domu.config
> 
> libxl: error: libxl_aoutils.c:539:async_exec_timeout: killing execution 
> of /etc/xen/scripts/block add because of timeout
> libxl: error: libxl_create.c:1608:domcreate_launch_dm: Domain 2:unable 
> to add disk devices
> libxl: error: libxl_aoutils.c:539:async_exec_timeout: killing execution 
> of /etc/xen/scripts/block remove because of timeout
> libxl: error: libxl_domain.c:1182:libxl__destroy_domid: Domain 
> 2:Non-existant domain
> libxl: error: libxl_domain.c:1136:domain_destroy_callback: Domain 
> 2:Unable to destroy guest
> libxl: error: libxl_domain.c:1063:domain_destroy_cb: Domain 
> 2:Destruction of domain failed
> ================================================
> 
> The last try was with alpine domU linux with the following config:
> ================================================
> 
> # Alpine Linux PV DomU
> # Kernel paths for install
> kernel = "/home/xen/vmlinuz-virt"
> ramdisk = "/home/xen/initramfs-virt"
> extra="modules=loop,squashfs console=hvc0"
> # Path to HDD and iso file
> disk = [ 'format=raw, vdev=xvda, access=w, target=/data/a1.img',
>          'format=raw, vdev=xvdc, access=r, devtype=cdrom, 

Have you tried to remove cdrom from your DomU config? I am not sure
cdrom can work well for Arm without device model.

Cheers,
Wei Chen
> target=/home/xen/alpine-virt-3.15.3-armv7.iso'  ]
> # Network configuration
> vif = ['bridge=br0']
> # DomU settings
> memory = 512
> name = "alpine-a1"
> vcpus = 1
> maxvcpus = 1
> ================================================
> 
> thanks a lot in advance
> Best regards
> Marco


  reply	other threads:[~2022-04-20  1:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-15 10:56 Problem creating domU guest on arm64 Marco Cacre
2022-04-20  1:55 ` Wei Chen [this message]
2022-04-20 10:54 ` Marco Cacre
2022-04-20 11:39   ` Wei Chen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5e7ded0e-36f6-2a0a-4dab-30d39e649c05@arm.com \
    --to=wei.chen@arm.com \
    --cc=marco.cacre@gmail.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.