All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kip Macy <kmacy@fsmware.com>
To: Derrik Pates <demon@devrandom.net>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: Re: Where to get FreeBSD port for Xen
Date: Sun, 23 Jan 2005 22:15:18 -0800 (PST)	[thread overview]
Message-ID: <20050123221440.A16809@demos.bsdclusters.com> (raw)
In-Reply-To: <41F481D8.4020004@devrandom.net>

Please send me your config file so I can try and reproduce.
Are you using your own root?


			-Kip


On Mon, 24 Jan 2005, Derrik Pates wrote:

> Kip:
>
> > It only has the kernel, a compressed mdroot, and the config scripts
> > that I use. The blocking issue discussed previously has not been fixed.
> > I intend to fix it, but there are some infrastructure bits that take
> > priority for me.
> >
> > Let me know how this works for you as soon as you try it out.
>
> Bad news, I'm afraid; the 5.3 kernel and mdroot doesn't successfully
> boot for me. I'm using the same args that happily boot the 5.2.1 kernel,
> but it simply stops once it reaches a certain point. The boot messages
> are as follows:
>
> --- start boot messages ---
> WARNING: loader(8) metadata is missing!
> start_info 0xc0295000
> start_info->nr_pages 32768
> Copyright (c) 1992-2004 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
>          The Regents of the University of California. All rights reserved.
> FreeBSD 5.3-RELEASE #31: Thu Jan 20 11:37:43 PST 2005
>
> mowat@bldf1.eng.netapp.com:/t/niners/users/xen/bsd/sys-5.3/i386-xeno.tot/compile/XENCONF
> WARNING: DIAGNOSTIC option enabled, expect reduced performance.
> Timecounter "ixen" frequency 1593088000 Hz quality 0
> CPU: AMD Opteron(tm) Processor 242 (1593.09-MHz 686-class CPU)
>    Origin = "AuthenticAMD"  Id = 0xf58  Stepping = 8
>
> Features=0x78bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2>
>    AMD Features=0xe0500000<NX,AMIE,LM,DSP,3DNow!>
> Data TLB: 32 entries, fully associative
> Instruction TLB: 32 entries, fully associative
> L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative
> L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way
> associative
> L2 internal cache: 1024 kbytes, 64 bytes/line, 1 lines/tag, 8-way
> associative
> real memory  = 131354624 (125 MB)
> Physical memory chunk(s):
> 0x00000000002bb000 - 0x0000000007aecfff, 126033920 bytes (30770 pages)
> avail memory = 125120512 (119 MB)
> WARNING: driver "evtchn" used unreserved major device number 140
> null: <null device, zero device>
> random: <entropy source, Software, Yarrow>
> cpu0 on motherboard
> Device configuration finished.
> procfs registered
> Timecounters tick every 10.000 msec
> xc0: <Xen Console> on motherboard
> WARNING: driver "xc" used unreserved major device number 12
> xn0: bpf attached
> xn0: Ethernet address: aa:00:00:00:00:28
> --- end boot messages ---
>
> At that point, it just doesn't go any further; 'xm list' shows it as in
> run state, not crashed, but it just never goes any further. Any thoughts?
>
> --
> Derrik Pates
> demon@devrandom.net
>
>
> -------------------------------------------------------
> 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@lists.sourceforge.net
> 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

  reply	other threads:[~2005-01-24  6:15 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200501191606.22899.mparem@cisco.com>
2005-01-19 23:18 ` Where to get FreeBSD port for Xen Kip Macy
2005-01-20 17:00   ` Mikhail V.Paremski
2005-01-20 21:52     ` Kip Macy
2005-01-21  0:18       ` David Rhodus
2005-01-21 22:23         ` Kip Macy
2005-01-24  0:39   ` Derrik Pates
2005-01-24  0:44     ` Kip Macy
2005-01-24  1:31     ` Kip Macy
2005-01-24  5:04       ` Derrik Pates
2005-01-24  6:15         ` Kip Macy [this message]
2005-01-24  6:18           ` Derrik Pates
2005-01-24  6:47             ` Kip Macy
2005-01-24 22:57               ` Derrik Pates
2005-01-24 23:03                 ` Kip Macy
2005-01-24 23:50                 ` Kip Macy
2005-01-25  0:27                   ` OpenBSD " Dave Feustel
2005-01-25  0:38                     ` Kip Macy
2005-01-25  1:02                       ` Dave Feustel
2005-01-25  1:05                         ` Kip Macy
2005-01-25 22:04                       ` Scott Parish
2005-01-25  0:53                   ` Re: Where to get FreeBSD " Derrik Pates
2005-01-24  2:25     ` Kip Macy
2005-01-24  9:01       ` Hidetoshi Shimokawa
2005-01-24 21:29         ` Kip Macy
2005-01-25  3:05           ` Hidetoshi Shimokawa
2005-01-25  4:09             ` Kip Macy
2005-01-25  4:40             ` Kip Macy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050123221440.A16809@demos.bsdclusters.com \
    --to=kmacy@fsmware.com \
    --cc=demon@devrandom.net \
    --cc=xen-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.