WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

RE: [Xen-ia64-devel] Paravirtualized xenlinux/ia64 available

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-ia64-devel] Paravirtualized xenlinux/ia64 available
From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
Date: Mon, 16 May 2005 09:37:15 -0700
Cc: "Munoz, Alberto J" <alberto.j.munoz@xxxxxxxxx>
Delivery-date: Mon, 16 May 2005 16:37:10 +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: AcVHlVmMb8/hDflETjKrZWojU5vuVgJUlTQAAaoddtAACuyVYAB+E+YwACBEQcA=
Thread-topic: [Xen-ia64-devel] Paravirtualized xenlinux/ia64 available
OK, I'll try to take a look at it today, possibly tomorrow.

Yes, the bits have only been tested on a ZX1 box (rx2600).
The hpsim_cons stuff is there for debugging purposes only. 

> -----Original Message-----
> From: Tian, Kevin [mailto:kevin.tian@xxxxxxxxx] 
> Sent: Sunday, May 15, 2005 11:33 PM
> To: Magenheimer, Dan (HP Labs Fort Collins); 
> xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Cc: Munoz, Alberto J
> Subject: RE: [Xen-ia64-devel] Paravirtualized xenlinux/ia64 available
> 
> Hi, Dan,
>       It still doesn't work, and could you give more detail 
> instructions about steps to run on ski simulator and real hardware.
> 
>       Are the steps you described upon zx1_defconfig only 
> adapts to zx1 machine, or also works for ski? If only for zx1 
> machine, why need to add hpsim_cons like stuff for 
> CONFIG_XEN? If also for ski, I always encountered "Can't open 
> root device" problem.
> 
>       I also tried to copy sim_defconfig, and there's no 
> output after "Freeing unused kernel memory: 192kB freed" but 
> the keyboard can work. Before reaching this point, at least I 
> need to change something for para-xenlinux:
>       1. Comment following line in arch/ia64/Makefile:
>               #drivers-$(CONFIG_XEN)          += arch/ia64/hp/sim/
>               Or else the compilation will fail due to double 
> inclusion
>       2. Comment arch/ia64/kernel/setup.c:
> static inline int __init
> early_console_setup (char *cmdline)
> {
> #if 0
> //#ifdef CONFIG_XEN
>         extern struct console hpsim_cons;
>         register_console(&hpsim_cons);
>         return 0;
> #else
>       Or else the hpsim_cons is registered twice and then 
> xenlinux will search console list and output same string 
> repeatedly for ever:
> Linux version 2.6.11 (gcc version 3.2.3 20030502 (Red Hat 
> Linux 3.2.3-20)) #7 SMP Sun May 15 18:30:58 PDT 2005
> 
>       But after all above done, it still can't reach user 
> prompt. Since I'm not familiar with ski simulator 
> environment, could you give a step-by-step instruction for 
> run on ski? :)
> 
> Thanks a lot,
> Kevin
> >-----Original Message-----
> >From: Magenheimer, Dan (HP Labs Fort Collins) 
> [mailto:dan.magenheimer@xxxxxx]
> >Sent: Friday, May 13, 2005 9:07 PM
> >To: Tian, Kevin; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx; xen-devel
> >Cc: Munoz, Alberto J
> >Subject: RE: [Xen-ia64-devel] Paravirtualized xenlinux/ia64 available
> >
> >Yes, like real Linux/ia64, it is not possible to run the
> >same Xenlinux bits both on ski and on real hardware.
> >A different configuration and build is required.  The
> >config difference is the same as it was with the
> >privified xenlinux... I think you did that successfully
> >before (with privified xenlinux) so give that config
> >file a try and if it doesn't work, let me know.
> >
> >BTW, I think I know how to fix this problem (unable
> >to run same bits on ski and real hardware) for real
> >Linux/ia64 and Xen/ia64, but it would take a day or
> >two and hasn't bubbled up to the top of my list yet.
> >
> >Dan
> >
> >P.S. Please move further replies on this topic
> >to xen-ia64-devel only.
> >
> >> -----Original Message-----
> >> From: Tian, Kevin [mailto:kevin.tian@xxxxxxxxx]
> >> Sent: Friday, May 13, 2005 2:35 AM
> >> To: Magenheimer, Dan (HP Labs Fort Collins);
> >> xen-ia64-devel@xxxxxxxxxxxxxxxxxxx; xen-devel
> >> Cc: Munoz, Alberto J
> >> Subject: RE: [Xen-ia64-devel] Paravirtualized 
> xenlinux/ia64 available
> >>
> >> Hi, Dan,
> >>    We tried latest xeno-unstable-ia64 bk tree on a para-virtualized
> >> dom0 following your instructions. However it failed to 
> find root fs on
> >> ski:
> >>
> >> VFS: Cannot open root device "<NULL>" or unknown-block(8,2)
> >> Please append a correct "root=" boot option
> >> Kernel panic - not syncing: VFS: Unable to mount root fs on
> >> unknown-block(8,2)
> >>
> >>    The bk info is:
> >>   ChangeSet@xxxxxx, 2005-05-10 15:58:27-07:00, 
> xen-ia64.adm@xxxxxxxxxx
> >>   Merge bk://xen.bkbits.net/xeno-unstable.bk
> >>   into  bkbits.net:/repos/x/xen-ia64/xeno-unstable-ia64.bk
> >>
> >>    However we then tried previous binary-patched dom0 with code in
> >> our trunk (VTI disabled), it can work to user prompt. This
> >> means the ski
> >> environment still working well.
> >>
> >>    Do you ever see similar error on this revision? Maybe we missed
> >> some important step or... ski environment needs some change?
> >> The command
> >> to start ski is:
> >>     "ski bootloader xen paralinux nomca simscsi=`pwd`/sd"
> >>
> >>    Here paralinux is built upon
> >> bk://xen-ia64.bkbits.net/xenlinux-ia64-2.6.11.bk.
> >>
> >>    BTW, just saw a small bug in vcpu.c:
> >> IA64FAULT vcpu_itc_d(VCPU *vcpu, UINT64
> >>            ...
> >>        if (((itir & ~0xfc) >> 2) < PAGE_SHIFT) {
> >> Should be:
> >>        if (((itir & 0xfc) >> 2) < PAGE_SHIFT) {
> >>
> >> Thanks,
> >> Kevin
> >> >-----Original Message-----
> >> >From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
> >> >[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> >> Magenheimer,
> >> >Dan (HP Labs Fort Collins)
> >> >Sent: Thursday, May 05, 2005 4:56 AM
> >> >To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx; xen-devel
> >> >Cc: Munoz, Alberto J
> >> >Subject: [Xen-ia64-devel] Paravirtualized xenlinux/ia64 available
> >> >
> >>
> 

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel

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