This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-ia64-devel] RE: DomU can progress to xen_init from serial output

To: "Magenheimer, Dan \(HP Labs Fort Collins\)" <dan.magenheimer@xxxxxx>
Subject: [Xen-ia64-devel] RE: DomU can progress to xen_init from serial output
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Tue, 1 Nov 2005 08:44:37 +0800
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 01 Nov 2005 00:41:38 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcXaGlgu/QcjDUygS6CWvF8wTHlozQEWNfigAAFE/GAAAPqoMA==
Thread-topic: DomU can progress to xen_init from serial output
Did you see ""unknown hypercall ..." warning on the console? Following patch is 
aimed to solve that issue. 

Also which changeset are you working on? Simply tip or you add something upon 
tip? Usually -EACCES errno is related to environmental issue. For example, you 
may see -EACCES if your control panel is compiled with different version as Xen 
(different interface version number). Also many ACM interfaces may return 
-EACCES but I think it hasn't make effect on ia64 yet.


>-----Original Message-----
>From: Magenheimer, Dan (HP Labs Fort Collins) [mailto:dan.magenheimer@xxxxxx]
>Sent: 2005年11月1日 8:08
>To: Tian, Kevin
>Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: RE: DomU can progress to xen_init from serial output
>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

<Prev in Thread] Current Thread [Next in Thread>