[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] ARM64: XEN Domu not booting with the qemu qcow AARCH64 Ubuntu 15.04 disk



On Wed, 3 Jun 2015, Sanjeev Pandita wrote:
> Hi Stefano,
>
> On Wed, Jun 3, 2015 at 3:45 PM, Stefano Stabellini 
> <stefano.stabellini@xxxxxxxxxxxxx> wrote:
>       On Wed, 3 Jun 2015, Sanjeev Pandita wrote:
>       > On Tue, Jun 2, 2015 at 7:55 PM, Stefano Stabellini 
> <stefano.stabellini@xxxxxxxxxxxxx> wrote:
>       >Â Â Â ÂOn Tue, 2 Jun 2015, Sanjeev Pandita wrote:
>       >Â Â Â Â> From: Stefan Bader [mailto:stefan.bader@xxxxxxxxxxxxx]
>       >Â Â Â Â> Sent: Tuesday, June 02, 2015 1:52 PM
>       >Â Â Â Â> To: Sanjeev Pandita; xen-devel@xxxxxxxxxxxxx
>       >Â Â Â Â> Cc: Ian.Campbell@xxxxxxxxxx; Pranavkumar Sawargaonkar;
>       >Â Â Â Â> stefano.stabellini@xxxxxxxxxxxxx
>       >Â Â Â Â> Subject: Re: [Xen-devel] ARM64: XEN Domu not booting with the 
> qemu qcow
>       >Â Â Â Â> AARCH64 Ubuntu 15.04 disk
>       >Â Â Â Â>
>       >Â Â Â Â> 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.
>       >Â Â Â Â>
>       >Â Â Â Â> Because I am lacking hardware and feedback, the arm64 
> packaging is a
>       >Â Â Â Â> rather theoretical exercise. At least for armhf I thought 
> qemu-system-x86
>       >Â Â Â Â> was a dependency. That binary should provide x86 emulation on 
> arm64, the
>       >Â Â Â Â> same as one could install qemu for other arches on x86.
>       >Â Â Â Â> Have you tried to install qemu-system-x86 manually?
>       >Â Â Â Â>
>       >Â Â Â Â> -Stefan
>       >Â Â Â Â>
>       >Â Â Â Â> >
>       >Â Â Â Â> > 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
>       >Â Â Â Â>
>       >Â Â Â Â> Thanks for your inputs, I have installed the qemu-system-i386 
> but my DomU
>       >Â Â Â Â> booting is still crashing with following short logs. Am I 
> missing anything
>       >Â Â Â Â> ?
>       >Â Â Â Â>
>       >Â Â Â Â> Kernel Crash logs:
>       >Â Â Â Â>
>       >Â Â Â Â> xenbus_probe_frontend: Waiting for devices to initialise:
>       >Â Â Â Â> 25s...20s...15s...10s...5s...0s...
>       >Â Â Â Â> 
> 235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s
>       >Â Â Â Â> 
> ...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...1
>       >Â Â Â Â> 
> 30s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75
>       >Â Â Â Â> 
> s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s.
>       >Â Â Â Â> ..10s...5s...0s...
>       >Â Â Â Â>
>       >Â Â Â Â> 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=" 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:
>       >Â Â Â Â> [<ffffffc00008a0dc>] dump_backtrace+0x0/0x124
>       >Â Â Â Â> [<ffffffc00008a210>] show_stack+0x10/0x1c
>       >Â Â Â Â> [<ffffffc000657d88>] dump_stack+0x80/0xc4
>       >Â Â Â Â> [<ffffffc000656f04>] panic+0xe0/0x220
>       >Â Â Â Â> [<ffffffc00087eea8>] mount_block_root+0x1a4/0x24c
>       >Â Â Â Â> [<ffffffc00087f19c>] mount_root+0x110/0x130
>       >Â Â Â Â> [<ffffffc00087f328>] prepare_namespace+0x16c/0x1b8
>       >Â Â Â Â> [<ffffffc00087eb44>] kernel_init_freeable+0x1c4/0x1ec
>       >Â Â Â Â> [<ffffffc00065481c>] kernel_init+0xc/0xd8
>       >Â Â Â Â> ---[ end Kernel panic - not syncing: VFS: Unable to mount 
> root fs on
>       >Â Â Â Â> unknown-block(0,0)
>       >
>       > It looks like the backend (QEMU) hasn't been initialized properly.
>       > Could you please post the output of xenstore-ls? Also could you run ps
>       > aux|grep qemu to check whether QEMU was spawned correctly?
>       >
>       >
>       > 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 = [ '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) ?
>
>
>
> 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 = ['tap:qcow2:/mnt/xen/vivid-server-cloudimg-arm64-disk1.img,xvda,w']

?
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.