From: Kip Macy <kmacy@fsmware.com>
To: Chris Andrews <chris@nodnol.org>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: FreeBSD/Xen kernel
Date: Thu, 16 Dec 2004 18:52:35 -0800 (PST) [thread overview]
Message-ID: <20041216185149.Y90399@demos.bsdclusters.com> (raw)
In-Reply-To: <26923500-4FB0-11D9-99E8-000393B01B94@nodnol.org>
Like I said in my initial post - any feedback would be *much
appreciated* :-).
-Kip
On Thu, 16 Dec 2004, Chris Andrews wrote:
>
> On 16 Dec 2004, at 19:20, Kip Macy wrote:
> >>
> >> Are you using an uncompressed copy of the mdroot I posted?
> >
> > Duh - obviously. The only thing I can think of is that the mdroot is
> > corrupted. I'll double check the bits I've posted.
>
> I got exactly these symptoms with the posted mdroot, and we fixed
> it with a slightly different block device export. I'm using this
> as my domain definition:
>
> kernel = "/boot/freebsd-5.2.1-xenU"
> memory = 64
> cpu = -1
> name = "XXVIII"
> nics=1
> vif = [ 'mac=aa:00:00:00:00:28, bridge=xen-br0' ]
> disk = [ 'phy:munkyII/vm-XXVIII,loopa,w' ]
> extra = "boot.netif.ip=10.1.70.28"
> extra += ",boot.netif.netmask=255.255.255.240"
> extra += ",boot.netif.gateway=10.1.70.17"
> extra += ",vfs.root.mountfrom=ufs:/dev/xbd0a"
> extra += ",boot_verbose=yes"
>
> I've put the mdroot image on a devicemapper device,
> /dev/munkyII/vm-XXVIII.
> This domain boots fine, although I do get this kind of log message to
> the console after a while:
>
> Expensive timeout(9) function: 0xc008c730(0) 0.010000091 s
>
> and the domain chews through CPU time as indicated by 'xm list' even
> when
> apparently idle. I haven't played much beyond that though.
>
> Cheers,
> Chris.
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-12-17 2:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 15:55 FreeBSD/Xen kernel Derrik Pates
2004-12-16 18:59 ` Kip Macy
2004-12-16 19:20 ` Kip Macy
2004-12-16 22:16 ` Chris Andrews
2004-12-17 2:03 ` Derrik Pates
2004-12-17 10:20 ` Chris Andrews
2004-12-28 6:59 ` Derrik Pates
2004-12-17 2:52 ` Kip Macy [this message]
2004-12-17 1:48 ` Derrik Pates
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=20041216185149.Y90399@demos.bsdclusters.com \
--to=kmacy@fsmware.com \
--cc=chris@nodnol.org \
--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.