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-devel

Re: [Xen-devel] Re: Where to get FreeBSD port for Xen

Funny you should ask. I just updated libxc to work with xen's current
context representation (previously I could just copy cpu_ctxt out and
everything worked, but just prior to the change most of the register
contents were wrong). I'll try to get everything posted within the hour.

One observation - I can't comment on 64MB, but FreeBSD 5.x doesn't do an
adequate job of managing its memory to stay up with 32MB or less.

                        -Kip



On Tue, 25 Jan 2005, Hidetoshi Shimokawa wrote:

> I have experianced strange lockups sometimes.
> In that case, 'xm list' shows no state for freebsd.
> (usually it is blocked)
>
> Name              Id  Mem(MB)  CPU  State  Time(s)  Console
> Domain-0           0       59    0  r----    990.1
> freebsd.sample     2       64    0  -----    547.6    9602
>
> I'd like to analyze this problem using debugger.
> I found gdbserver binary in your web site but it seems old and
> to require old libraries. Can I get the gdbserver source?
>
> Thanks,
>
> /\ Hidetoshi Shimokawa
> \/  simokawa@xxxxxxxxxxx
>
>
> At Mon, 24 Jan 2005 13:29:38 -0800 (PST),
> Kip Macy wrote:
> >
> > Thanks for patch and the heads up on the successful boot.
> >
> > I'll apply the patch and update the posted tarball and kernel tonight.
> >
> >
> >
> >                                     -Kip
> >
> > On Mon, 24 Jan 2005, Hidetoshi Shimokawa wrote:
> >
> > > Thank you very much for your work, Kip.
> > >
> > > I successfully booted xenofreebsd from your source.
> > > The following patch(obtained from NetBSD) seems to
> > > fix the scheduling problem.
> > >
> > > /\ Hidetoshi Shimokawa
> > > \/  simokawa@xxxxxxxxxxx
> > >
> > > diff -u -r /home/simokawa/xen/i386-xeno/i386-xeno/clock.c 
> > > i386-xeno/i386-xeno/clock.c
> > > --- /home/simokawa/xen/i386-xeno/i386-xeno/clock.c        Mon Jan 24 
> > > 10:36:19 2005
> > > +++ i386-xeno/i386-xeno/clock.c   Mon Jan 24 16:58:31 2005
> > > @@ -502,3 +502,10 @@
> > >   /* our adjusted time offset in microseconds */
> > >   return edx;
> > >  }
> > > +
> > > +void
> > > +idle_block(void)
> > > +{
> > > + if (HYPERVISOR_set_timer_op(processed_system_time + NS_PER_TICK) == 0)
> > > +         HYPERVISOR_block();
> > > +}
> > > diff -u -r /home/simokawa/xen/i386-xeno/i386-xeno/machdep.c 
> > > i386-xeno/i386-xeno/machdep.c
> > > --- /home/simokawa/xen/i386-xeno/i386-xeno/machdep.c      Mon Jan 24 
> > > 10:36:19 2005
> > > +++ i386-xeno/i386-xeno/machdep.c Mon Jan 24 17:50:25 2005
> > > @@ -140,6 +140,7 @@
> > >  #include <machine/hypervisor.h>
> > >  #include <machine/xenfunc.h>
> > >  #include <machine/xenvar.h>
> > > +#include <machine/xen_intr.h>
> > >
> > >  void Xhypervisor_callback(void);
> > >  void failsafe_callback(void);
> > > @@ -903,8 +904,13 @@
> > >    */
> > >   __asm __volatile("sti; hlt");
> > >  #endif
> > > +#if 0
> > >   enable_intr();
> > >   HYPERVISOR_yield();
> > > +#else
> > > + idle_block();
> > > + enable_intr();
> > > +#endif
> > >  }
> > >
> > >  /*
> > > diff -u -r /home/simokawa/xen/i386-xeno/include/xen_intr.h 
> > > i386-xeno/include/xen_intr.h
> > > --- /home/simokawa/xen/i386-xeno/include/xen_intr.h       Mon Jan 24 
> > > 10:36:19 2005
> > > +++ i386-xeno/include/xen_intr.h  Mon Jan 24 17:48:55 2005
> > > @@ -44,6 +44,7 @@
> > >  extern void irq_suspend(void);
> > >  extern void irq_resume(void);
> > >
> > > +extern void idle_block(void);
> > >
> > >
> > >  #endif /* _XEN_INTR_H_ */
> > >
> > >
> > > At Sun, 23 Jan 2005 18:25:25 -0800 (PST),
> > > Kip Macy wrote:
> > > >
> > > > For those interested I've uploaded a source tarball and copied in
> > > > updated directions.
> > > >
> > > >
> > > >                                         -Kip
> > > >
> > > >
> > > >
> > > > On Sun, 23 Jan 2005, Derrik Pates wrote:
> > > >
> > > > > Kip Macy wrote:
> > > > > > It looks like apache had gone out to lunch. I just restarted it and 
> > > > > > it
> > > > > > is accessible again. If you wait a day I'll have 5.3 up. 5.2.1 is 
> > > > > > what
> > > > > > is there right now.
> > > > >
> > > > > Kip:
> > > > >
> > > > > Any luck with that FreeBSD 5.3 kernel? Our network engineer wants to 
> > > > > set
> > > > > up a Xen box for internal use with Debian and FreeBSD on it, and I'm
> > > > > hoping to get FreeBSD 5.3 on there. Also, were you able to figure out
> > > > > the blocking stuff in the scheduling code?
> > > > >
> > > > > --
> > > > > Derrik Pates
> > > > > demon@xxxxxxxxxxxxx
> > > > >
> > > >
> > > >
> > > > -------------------------------------------------------
> > > > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> > > > Tool for open source databases. Create drag-&-drop reports. Save time
> > > > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> > > > Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> > > > _______________________________________________
> > > > Xen-devel mailing list
> > > > Xen-devel@xxxxxxxxxxxxxxxxxxxxx
> > > > https://lists.sourceforge.net/lists/listinfo/xen-devel
> > >
>


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel