From: Kip Macy <kip.macy@gmail.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net, ian.pratt@cl.cam.ac.uk
Subject: Re: DOM0 falling off of network when running latest FreeBSD
Date: Sat, 12 Mar 2005 10:18:02 -0800 [thread overview]
Message-ID: <b1fa29170503121018f0fb2cb@mail.gmail.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E35F0@liverpoolst.ad.cl.cam.ac.uk>
It turns out I had missed a couple of lines when updating blkfront.c &
ctrl_if.c. Fixing the ring sizes in blkfront.c fixed the problem with
DOM0 not getting any CPU time and fixing ctrl_if.c fixed the issue
with device set up. Not surprisingly it was my fault, but I think that
long term xen needs to be a little more vigorous in containing
misbehaved guests.
Thanks.
-Kip
On Sat, 12 Mar 2005 15:32:48 -0000, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:
>
> > Am I missing some important configuration change between
> > -testing and -unstable?
> >
> > When I boot FreeBSD with a config file that works on -testing I see
> > the following on the console with -unstable after which ping still
> > succeeds but ssh hangs...
>
> There have been a couple of changes to the message protocal between
> testing and unstable. Are you sure you've tracked these? E.g. network
> device MTU and backend MAC configuration.
>
> Ian
>
> > [XEN] Attempting to reconnect network interface: handle=0
> > [XEN] Netfront recovered tx=0 rxfree=0
> > [XEN] Attempting to reconnect network interface: handle=0
> > [XEN] Attempting to reconnect network interface: handle=0
> > [XEN] Failed to connect all virtual interfaces: err=-50
> > [XEN] Initialising virtual block device driver
> >
> >
> > -------------------------------------------------------
> > 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> > _______________________________________________
> > 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-12 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-12 15:32 DOM0 falling off of network when running latest FreeBSD Ian Pratt
2005-03-12 18:18 ` Kip Macy [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-12 18:46 Ian Pratt
2005-03-12 1:24 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=b1fa29170503121018f0fb2cb@mail.gmail.com \
--to=kip.macy@gmail.com \
--cc=ian.pratt@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--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.