I meant to add... even with this patch, when doing
"xend start", I am still getting
Exception starting xend: (1, 'Operation not permitted')
> -----Original Message-----
> From: Magenheimer, Dan (HP Labs Fort Collins)
> Sent: Monday, October 31, 2005 4:31 PM
> To: 'Tian, Kevin'
> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: DomU can progress to xen_init from serial output
>
> Committed to xen-ia64-unstable
>
> > -----Original Message-----
> > From: Tian, Kevin [mailto:kevin.tian@xxxxxxxxx]
> > Sent: Wednesday, October 26, 2005 4:45 AM
> > To: Magenheimer, Dan (HP Labs Fort Collins)
> > Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: DomU can progress to xen_init from serial output
> >
> > Hi, Dan,
> > With attached patch, I can "xend start" successfully
> > now and finally domU reached xen_init from the serial output:
> >
> > NET: Registered protocol family 16
> > Running on Xen! start_info_pfn=0x0 lags=0x0
> > xen-event-channel using irq 233
> > store_evtchn = 1
> >
> > Then domU falls into a dead loop to acquire spinlock of
> > printk buffer (already held by others), and strange thing is
> > that machine timer interrupt still happens while domain
> > switches disappeared.
> >
> > I'll go to Intel IDF (Shanghai) at the rest of this
> > week, and so can't find enough time to continue debug. Dan,
> > could you take over the domU boot? ;-) Actually the
> > start_info_pfn is problematic point here, since it should be
> > passed from control panel.
> >
> > Thanks,
> > Kevin
> >
>
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
Home