On Thu, 27 Jan 2011, Alex wrote:
[..]
> the HVM kernel just panics and I remember seeing something along the lines of
> "do something smart?"
>
> does this patch you mention fix that?
Yes. See http://www.freebsd.org/cgi/query-pr.cgi?pr=154302
The patch is also attached to this mail.
Best Regar
It's would be a logical conclusion that it's an issue with the "re"
driver then. I cant get my 8.2-RC1 XENHVM kernel to boot so had to
resort to GENERIC, the HVM kernel just panics and I remember seeing
something along the lines of "do something smart?"
does this patch you mention fix that?
O
I saw this same high collision count before I converted my RootBSD domU from
GENERIC to XENHVM. I do not see any collisions show up in netstat -i with
xn0/xn1 instead of re0/re1.
Of course, I needed kern/154302's patch to make the XENHVM kernel work. I hope
that gets committed and merged back i
On Wed, 26 Jan 2011, Alex wrote:
> Though as far as I know, when a collision is detected, the behavior is for the
> sender to invoke it's backoff algorithm and to wait a set amount of time
> before transmitting again. if this is actually occurring then there would be
> performance degradation.
Ye
Hi Janne,
I don't know whether this is an issue with the "re" driver or something
else that's affecting the "re" driver (the way Xen handles network
traffic). Though as far as I know, when a collision is detected, the
behavior is for the sender to invoke it's backoff algorithm and to wait
a
On Wed, 26 Jan 2011, Alex wrote:
> I am having an issue with high network interface collisions when running
> freebsd under XEN (I am using freebsd as my OS for a VPS).
[..]
> whether they have seen the same issue or know what may be causing it.
I can confirm seeing it here also, you are not alon
