Re: [Xen-users] ARM: Xen on Vexpress

[Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>]

On Mon, 23 Jun 2014, Stefano Stabellini wrote:
> On Mon, 23 Jun 2014, Jeenu Viswambharan wrote:
> > On Mon, Jun 23, 2014 at 11:23:23, Stefano Stabellini wrote:
> > > On Mon, 23 Jun 2014, Jeenu Viswambharan wrote:
> > > > Are there any options to enable logs from upstart?
> > >
> > > I know very little about upstart.
> > > Do you see something like:
> > >
> > > Xen 4.5 support found, events_irq=31 gnttab_frame_pfn=ff800
> > > xen:grant_table: Grant tables using version 1 layout
> > > Grant table initialized
> > > NET: Registered protocol family 16
> > > Xen: initializing cpu0
> > > Xen: initializing cpu1
> > > Xen: initializing cpu3
> > > Xen: initializing cpu2
> > > DMA: preallocated 256 KiB pool for atomic coherent allocations
> > > xen:swiotlb_xen: Warning: only able to allocate 4 MB for software IO TLB
> > > software IO TLB [mem 0xbf000000-0xbf400000] (4MB) mapped at 
> > > [df000000-df3fffff]
> > > Serial: AMBA PL011 UART driver
> > > bio: create slab <bio-0> at 0
> > > xen:balloon: Initialising balloon driver
> > >
> > > on your dom0 kernel logs?
> > 
> > I don't! Dom0 logs are mostly silent about Xen.
> 
> You are missing all the earlyboot stuff from your logs.
> Try passing earlyprintk to the dom0 kernel command line.

FYI from "xen_netfront: Initialising Xen virtual ethernet driver" I
gather that the Xen subsystem most probably initialized correctly.
So it might actually be just a misconfiguration of agetty for hvc0 in
upstart.


> > > > Are there any extra options to be enabled in the Dom0 kernel other
> > > > than Xen support?
> > >
> > > For the console you need:
> > >
> > > CONFIG_HVC_XEN=y
> > >
> > > Overall this is what I have:
> > >
> > > CONFIG_XEN_DOM0=y
> > > CONFIG_XEN=y
> > > CONFIG_XEN_BLKDEV_FRONTEND=y
> > > CONFIG_XEN_BLKDEV_BACKEND=y
> > > CONFIG_XEN_NETDEV_FRONTEND=y
> > > CONFIG_XEN_NETDEV_BACKEND=y
> > > CONFIG_HVC_XEN=y
> > > CONFIG_XEN_BALLOON=y
> > > CONFIG_XEN_SCRUB_PAGES=y
> > > CONFIG_XEN_DEV_EVTCHN=y
> > > CONFIG_XEN_BACKEND=y
> > > CONFIG_XENFS=y
> > > CONFIG_XEN_COMPAT_XENFS=y
> > > CONFIG_XEN_SYS_HYPERVISOR=y
> > > CONFIG_XEN_XENBUS_FRONTEND=y
> > > CONFIG_XEN_GNTDEV=y
> > > CONFIG_SWIOTLB_XEN=y
> > > CONFIG_XEN_PRIVCMD=y
> > 
> > Mine was comparable; the only exceptions were that some where 'm',
> > rather than 'y'. I changed my configuration to match yours above, but I
> > still am where I was :(
> > 
> > I've attached my logs. I reckon you're running Xen 4.5, but I'm on 4.4.
> > I'll try switching to 4.5.0.

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