From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefano Stabellini Subject: Re: ARM64: XEN Domu not booting with the qemu qcow AARCH64 Ubuntu 15.04 disk Date: Wed, 3 Jun 2015 12:50:59 +0100 Message-ID: References: <8c250ccc118dd9a879d0509ef58030a6@mail.gmail.com> <556D67C0.7040809@canonical.com> <8ff64a3d1e94a099bbefe0efd4cdc5e5@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="1342847746-2087967885-1433332226=:19838" Return-path: In-Reply-To: Content-ID: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Sanjeev Pandita Cc: xen-devel@lists.xen.org, Pranavkumar Sawargaonkar , Ian Campbell , Stefan Bader , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org --1342847746-2087967885-1433332226=:19838 Content-Type: text/plain; charset="UTF-8" Content-Length: 7606 Content-Transfer-Encoding: quoted-printable Content-ID: On Wed, 3 Jun 2015, Sanjeev Pandita wrote: > Hi Stefano, > > On Wed, Jun 3, 2015 at 3:45 PM, Stefano Stabellini wrote: > On Wed, 3 Jun 2015, Sanjeev Pandita wrote: > > On Tue, Jun 2, 2015 at 7:55 PM, Stefano Stabellini wrote: > >=C2=A0 =C2=A0 =C2=A0 =C2=A0On Tue, 2 Jun 2015, Sanjeev Pandita wrote: > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> From: Stefan Bader [mailto:stefan.bader@canonical.com] > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> Sent: Tuesday, June 02, 2015 1:52 PM > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> To: Sanjeev Pandita; xen-devel@lists.xen.org > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> Cc: Ian.Campbell@citrix.com; Pranavkumar Sawargaonkar; > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> stefano.stabellini@eu.citrix.com > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> Subject: Re: [Xen-devel] ARM64: XEN Domu not booting with the qemu qcow > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> AARCH64 Ubuntu 15.04 disk > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> On 02.06.2015 09:40, Sanjeev Pandita wrote: > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> > All, > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> > I am pretty new to xen . I am trying to boot DOMU with qemu qcow > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> > AARCH64 Ubuntu 15.04 disk on Xen but I am getting the errors which > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> > link to "/usr/local/lib/xen/bin/qemu-system-i386". > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> > Since I am working on aarch64 system the > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> > /usr/local/lib/xen/bin/qemu-system-i386 bin might not be present or > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> > might not work as expected. > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> Because I am lacking hardware and feedback, the arm64 packaging is a > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> rather theoretical exercise. At least for armhf I thought qemu-system-x86 > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> was a dependency. That binary should provide x86 emulation on arm64, the > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> same as one could install qemu for other arches on x86. > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> Have you tried to install qemu-system-x86 manually=3F > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> -Stefan > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> > Please let me know how to make the Qemu qcow image work on Xen. > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> > Attached are the DomU boot log and config file. > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> > Thanks, > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> > San > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> Thanks for your inputs, I have installed the qemu-system-i386 but my DomU > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> booting is still crashing with following short logs. Am I missing anything > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> =3F > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> Kernel Crash logs: > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> xenbus_probe_frontend: Waiting for devices to initialise: > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> 25s...20s...15s...10s...5s...0s... > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> 235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> ...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...1 > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> 30s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75 > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s. > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> ..10s...5s...0s... > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> xenbus_probe_frontend: Timeout connecting to device: device/vbd/51712 > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> (local state 3, remote state 2) > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> console [netcon0] enabled > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> netconsole: network logging started > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> drivers/rtc/hctosys.c: unable to open rtc device (rtc0) > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> VFS: Cannot open root device "xvda" or unknown-block(0,0): error -6 > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> Please append a correct "root=3D" boot option; here are the available > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> partitions: > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> Kernel panic - not syncing: VFS: Unable to mount root fs on > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> unknown-block(0,0) > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.19.8 #5 > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> Hardware name: XENVM-4.6 (DT) > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> Call trace: > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> [] dump_backtrace+0x0/0x124 > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> [] show_stack+0x10/0x1c > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> [] dump_stack+0x80/0xc4 > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> [] panic+0xe0/0x220 > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> [] mount_block_root+0x1a4/0x24c > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> [] mount_root+0x110/0x130 > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> [] prepare_namespace+0x16c/0x1b8 > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> [] kernel_init_freeable+0x1c4/0x1ec > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> [] kernel_init+0xc/0xd8 > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on > >=C2=A0 =C2=A0 =C2=A0 =C2=A0> unknown-block(0,0) > > > > It looks like the backend (QEMU) hasn't been initialized properly. > > Could you please post the output of xenstore-ls=3F Also could you run ps > > aux|grep qemu to check whether QEMU was spawned correctly=3F > > > > > > Attaching output of xenstore-ls and grep qemu. > > Looks like qemu process is getting spawned and running fine. > > > > I have also modified the config file to remove tap from disk like: > > disk =3D [ 'qcow:/mnt/xen/vivid-server-cloudimg-arm64-disk1.img,xvda,w' ] > > But still my DOMU booting is stuck and getting crashed due to lack of rootfs/disk. > > > > I am running this on mustang board. > > QEMU has been spawn correctly, and I can see that it changed the > backend state to "2" (/local/domain/0/backend/qdisk/1/51712 in xenstore). > > Similarly the frontend initialization has started as the frontend state > has been changed to "3". > > However they should be both "4". So unless you manage to capture a > transient state, the communication between frontend and backend got > stuck. I don't know why. > > Is there anything interesting in the QEMU logs (under /var/log/xen) =3F > > > > I checked /var/log/xen. Here is the error message. > > linux:/var/log/xen # cat qemu-dm-vm4.log > xen be: qdisk-51712: error: 'xvda' uses a qcow feature which is not supported by this qemu version: QCOW version 2 > xen be: qdisk-51712: initialise() failed All right, maybe you just need to specify: disk =3D ['tap:qcow2:/mnt/xen/vivid-server-cloudimg-arm64-disk1.img,xvda,w'] =3F --1342847746-2087967885-1433332226=:19838 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 --1342847746-2087967885-1433332226=:19838--