From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Bader Subject: Re: ARM64: XEN Domu not booting with the qemu qcow AARCH64 Ubuntu 15.04 disk Date: Tue, 02 Jun 2015 14:41:00 +0200 Message-ID: <556DA45C.6040503@canonical.com> References: <8c250ccc118dd9a879d0509ef58030a6@mail.gmail.com> <556D67C0.7040809@canonical.com> <8ff64a3d1e94a099bbefe0efd4cdc5e5@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6582681427689114004==" Return-path: In-Reply-To: <8ff64a3d1e94a099bbefe0efd4cdc5e5@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --===============6582681427689114004== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="RvUbA9pR9kxh2dbeBRTfvufnOnB127QuT" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --RvUbA9pR9kxh2dbeBRTfvufnOnB127QuT Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 02.06.2015 14:09, Sanjeev Pandita wrote: > Hi, >=20 > -----Original Message----- > From: Stefan Bader [mailto:stefan.bader@canonical.com] > Sent: Tuesday, June 02, 2015 1:52 PM > To: Sanjeev Pandita; xen-devel@lists.xen.org > Cc: Ian.Campbell@citrix.com; Pranavkumar Sawargaonkar; > stefano.stabellini@eu.citrix.com > Subject: Re: [Xen-devel] ARM64: XEN Domu not booting with the qemu qcow= > AARCH64 Ubuntu 15.04 disk >=20 > On 02.06.2015 09:40, Sanjeev Pandita wrote: >> All, >> >> I am pretty new to xen . I am trying to boot DOMU with qemu qcow >> AARCH64 Ubuntu 15.04 disk on Xen but I am getting the errors which >> link to "/usr/local/lib/xen/bin/qemu-system-i386". >> Since I am working on aarch64 system the >> /usr/local/lib/xen/bin/qemu-system-i386 bin might not be present or >> might not work as expected. >=20 > Because I am lacking hardware and feedback, the arm64 packaging is a > rather theoretical exercise. At least for armhf I thought qemu-system-x= 86 > was a dependency. That binary should provide x86 emulation on arm64, th= e > same as one could install qemu for other arches on x86. > Have you tried to install qemu-system-x86 manually? >=20 > -Stefan >=20 >> >> Please let me know how to make the Qemu qcow image work on Xen. >> Attached are the DomU boot log and config file. >> >> Thanks, >> San >=20 > Thanks for your inputs, I have installed the qemu-system-i386 but my Do= mU > booting is still crashing with following short logs. Am I missing anyth= ing > ? >=20 > Kernel Crash logs: >=20 > xenbus_probe_frontend: Waiting for devices to initialise: > 25s...20s...15s...10s...5s...0s... > 235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...1= 85s > ...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s.= =2E.1 > 30s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s..= =2E75 > s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...1= 5s. > ..10s...5s...0s... >=20 > xenbus_probe_frontend: Timeout connecting to device: device/vbd/51712 > (local state 3, remote state 2) > console [netcon0] enabled > netconsole: network logging started > drivers/rtc/hctosys.c: unable to open rtc device (rtc0) > VFS: Cannot open root device "xvda" or unknown-block(0,0): error -6 > Please append a correct "root=3D" boot option; here are the available > partitions: > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(0,0) > CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.19.8 #5 > Hardware name: XENVM-4.6 (DT) > Call trace: > [] dump_backtrace+0x0/0x124 > [] show_stack+0x10/0x1c > [] dump_stack+0x80/0xc4 > [] panic+0xe0/0x220 > [] mount_block_root+0x1a4/0x24c > [] mount_root+0x110/0x130 > [] prepare_namespace+0x16c/0x1b8 > [] kernel_init_freeable+0x1c4/0x1ec > [] kernel_init+0xc/0xd8 > ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(0,0) >=20 >=20 > My config file : >=20 > linux:/mnt/xen # cat vm1 > name =3D "vm1" > uuid =3D "3fb78ba6-8182-484c-acf7-8faba9773f68" > disk =3D [ 'tap:qcow:/mnt/xen/vivid-server-cloudimg-arm64-disk1.img,xvd= a,w' We do not have blktap support. Maybe dropping that prefix helps... > ] > memory =3D 512 > kernel =3D "./Image" > extra =3D "root=3D/dev/xvda rw console=3Dhvc0 earlyprintk=3Dxen" >=20 >=20 > Regards, > San >=20 >=20 >> >> >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xen.org >> http://lists.xen.org/xen-devel >> >=20 --RvUbA9pR9kxh2dbeBRTfvufnOnB127QuT Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJVbaRjAAoJEOhnXe7L7s6jM88P/A+GriThntaGYd04AZaGUxW/ z3dnk32e6v32UnpLcQekHQC6X49o7+nIPvQEKqgIKGL16HUlJsjxLbUEpznAjisM bVohsyj+RWachm+b6wxtZ5EiCiifio8QMzEyvexjvHBn6KlYUlfYdCd+hivYZg7y BKc4CzkiJJoeE9WL5D5Y9rca+iURd17xENsqGSW/jnD5emUwsQBNCrsQK6CE2TxA 5fI61+aV+0ea9/uEn1w43Uk6i9qpBjGsrD1ImaP73YaBOQWe40sFGqUqVmuo2YIC bya/hgT9vg3LjNqRF6RGFIiwlWeBO8mQVLxUaKcwzyQ0WLXHZqKc0xl/yV6eLM12 fml7NpQ0taAHcOxj4w2JZqeGSvaqcq4HUyU4GgLq2LXbeIKCNhZaQzqAVjOb0coq KZwIDBXCkyNKoVx8aIJpZrrDr6RSlXFr8ffLcjNw67OnzE8VaZC1f7AHnkobmfLp FMGqN1/Uk4z9lEa5u3Fg13Fr54xLOco9yDbCjTru+8YSvVQvNFZwJohDO8VzZEWz MkVMZ0rGP+IirGH86QCcPiYcKzUFvceI1OV/qJihDJ1hBv+vX5CvwocGgyOQR5t0 SOdTuWvfCDS3xxs8/Lj8We4pdBam0iJ8tbrZcdqhBqtiia4n9y44lCpnQ23lBVcO yp5NjDqrACfsanlffMFn =FEG0 -----END PGP SIGNATURE----- --RvUbA9pR9kxh2dbeBRTfvufnOnB127QuT-- --===============6582681427689114004== 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 --===============6582681427689114004==--