Committed. Note that I put the change in blkback.c into
an #ifdef __ia64__ to avoid the possibility that it might
break Xen/x86 and also mark it as a clear functional
difference between the grant table call for x86 and ia64.
> -----Original Message-----
> From: Tian, Kevin [mailto:kevin.tian@xxxxxxxxx]
> Sent: Tuesday, November 08, 2005 6:21 AM
> To: Magenheimer, Dan (HP Labs Fort Collins)
> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-ia64-devel] RE: DomU can progress to
> xen_init from serialoutput
>
> Hi, Dan,
> With the attached patch, I can boot domU again on a bit
> old repository which was pulled one week ago. However after
> pulling the latest tip from xen-ia64-unstable.hg, I can't
> even "xm create" successfully with phenomenon that "xm
> create" doesn't return blocking in createDevices (Python) and
> only way is to kill that thread. I sent out a mail to
> xen-devel for possible suggestions.
>
> However, I think domU code should be ready now based on
> this patch. The rest is mainly related to the environmental
> setup issue. ;-)
>
> Thanks,
> Kevin
>
> >-----Original Message-----
> >From: Magenheimer, Dan (HP Labs Fort Collins)
> [mailto:dan.magenheimer@xxxxxx]
> >Sent: 2005年11月8日 0:14
> >To: Tian, Kevin
> >Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> >Subject: RE: [Xen-ia64-devel] RE: DomU can progress to
> xen_init from serialoutput
> >
> >OK. I am going to try to merge with xen-unstable again
> >today as I think 3.0 freeze will be soon and I would like
> >to merge the remaining ia64 driver patches (per Keir's
> >permission). There are very few recent changes in driver
> >files, but one (7627) changes code near one of the ia64
> >patches, so after I merge, you might want to eyeball that
> >code as I cannot test it without multiple domains working.
> >
> >> -----Original Message-----
> >> From: Tian, Kevin [mailto:kevin.tian@xxxxxxxxx]
> >> Sent: Monday, November 07, 2005 7:47 AM
> >> To: Magenheimer, Dan (HP Labs Fort Collins)
> >> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> >> Subject: RE: [Xen-ia64-devel] RE: DomU can progress to
> >> xen_init from serialoutput
> >>
> >> Now I'm still seeing "VFS: can't open root device" error
> >> (most generic warning ;-), which means the communication
> >> between blkfront and blkback still not working yet. However
> >> I've verified that most stuff are set up correctly before
> >> xlblk_init(). Also some communications are already done
> >> correctly on xenbus. Maybe related to grant table, and still
> >> in investigation...
> >>
> >> If I see any obvious change required upon driver files, I'll
> >> let you know immediately.
> >>
> >> Thanks,
> >> Kevin
> >>
> >> >-----Original Message-----
> >> >From: Magenheimer, Dan (HP Labs Fort Collins)
> >> [mailto:dan.magenheimer@xxxxxx]
> >> >Sent: 2005年11月5日 0:10
> >> >To: Tian, Kevin
> >> >Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> >> >Subject: RE: [Xen-ia64-devel] RE: DomU can progress to
> >> xen_init from serialoutput
> >> >
> >> >Oops, I forgot to add... in particular I am interested
> >> >in whether there are more ia64-specific changes to any
> >> >xen driver files, as I would like to work with Keir
> >> >to integrate the ia64 patches before the 3.0 freeze.
> >> >
> >> >Thanks,
> >> >Dan
> >> >
> >> >> -----Original Message-----
> >> >> From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
> >> >> [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf
> >> >> Of Magenheimer, Dan (HP Labs Fort Collins)
> >> >> Sent: Friday, November 04, 2005 8:25 AM
> >> >> To: Tian, Kevin
> >> >> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> >> >> Subject: [Xen-ia64-devel] RE: DomU can progress to xen_init
> >> >> from serialoutput
> >> >>
> >> >> Hi Kevin --
> >> >>
> >> >> Any further progress on booting domU? Or were the
> >> >> KR problems the only problems?
> >> >>
> >> >> Thanks,
> >> >> Dan
> >> >>
> >> >> > -----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
> >> >>
> >>
>
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
Home