[9fans] vmware oddity (Fusion on Mac OS X)

[9fans] vmware oddity (Fusion on Mac OS X)

[David Leimbach]

[-- Attachment #1: Type: text/plain, Size: 470 bytes --]

Just fired up my plan 9 image in VMWare, and I noticed that gnot is showing
a large amount of interrupts, and then the whole tracking of the system
interrupts goes to nothing, the mouse stops working, and things are
generally frozen.
However, the odd bit is at one point time seemed to speed up and gnot went
"really fast", before freezing again.

anyone experienced this?  It just unfroze again, but "l" "i" "s" and "c" on
gnot are totally pegged. :-(

Dave

[-- Attachment #2: Type: text/html, Size: 587 bytes --]

Re: [9fans] vmware oddity (Fusion on Mac OS X)

[David Leimbach]

[-- Attachment #1: Type: text/plain, Size: 642 bytes --]

now i am getting repeated soverflow for fx->in messages repeatedly.

On Tue, Aug 18, 2009 at 7:20 AM, David Leimbach <leimy2k@gmail.com> wrote:

> Just fired up my plan 9 image in VMWare, and I noticed that gnot is showing
> a large amount of interrupts, and then the whole tracking of the system
> interrupts goes to nothing, the mouse stops working, and things are
> generally frozen.
> However, the odd bit is at one point time seemed to speed up and gnot went
> "really fast", before freezing again.
>
> anyone experienced this?  It just unfroze again, but "l" "i" "s" and "c" on
> gnot are totally pegged. :-(
>
> Dave
>

[-- Attachment #2: Type: text/html, Size: 972 bytes --]

Re: [9fans] vmware oddity (Fusion on Mac OS X)

[erik quanstrom]

On Tue Aug 18 10:28:44 EDT 2009, leimy2k@gmail.com wrote:

> now i am getting repeated soverflow for fx->in messages repeatedly.
>

it sounds like the interrupt handler takes long enough that
there is no time to process the incoming frames.

i wonder, are you running venti?

- erik

Re: [9fans] vmware oddity (Fusion on Mac OS X)

[David Leimbach]

[-- Attachment #1: Type: text/plain, Size: 531 bytes --]

On Tue, Aug 18, 2009 at 7:32 AM, erik quanstrom <quanstro@quanstro.net>wrote:

> On Tue Aug 18 10:28:44 EDT 2009, leimy2k@gmail.com wrote:
>
> > now i am getting repeated soverflow for fx->in messages repeatedly.
> >
>
> it sounds like the interrupt handler takes long enough that
> there is no time to process the incoming frames.
>
> i wonder, are you running venti?


I am, and venti took a long time to start at boot this time around.  I
suppose I should just run fossil in vmware.




>
>
> - erik
>
>

[-- Attachment #2: Type: text/html, Size: 1062 bytes --]

Re: [9fans] vmware oddity (Fusion on Mac OS X)

[erik quanstrom]

> > it sounds like the interrupt handler takes long enough that
> > there is no time to process the incoming frames.
> >
> > i wonder, are you running venti?
>
>
> I am, and venti took a long time to start at boot this time around.  I
> suppose I should just run fossil in vmware.

well, there are a couple of things that should be done
- the ethernet driver bug should be fixed
- venti should be shown how to use a pipe instead of tcp.

but, i think if you configure a proper loopback using
loopbackmedium rather than going through your virtual
ethernet controller, that might just fix the problem.

- erik

Re: [9fans] vmware oddity (Fusion on Mac OS X)

[james toy]

I was just actually about to post about this. I have yet to find a
fix; however, it seems its after the multiplex code and can be found
here

<link>
http://fxr.watson.org/fxr/source/pc/devether.c?v=PLAN9#L202
</link>

I am not running venti; I am only running fossil.  I don't think that
is related in light of the fact we are running both options and its
happening on both.  I get the behavior after i put in my aescbc key
before rio.  I also get a whole bunch of download failed and see faces
freaking out as its trying to interact with my GMail.  I only get this
on updating or downloading my emails on first boot.

I am going to continue to look into it.

james toy

On Tue, Aug 18, 2009 at 10:49 AM, erik quanstrom<quanstro@quanstro.net> wrote:
>> > it sounds like the interrupt handler takes long enough that
>> > there is no time to process the incoming frames.
>> >
>> > i wonder, are you running venti?
>>
>>
>> I am, and venti took a long time to start at boot this time around.  I
>> suppose I should just run fossil in vmware.
>
> well, there are a couple of things that should be done
> - the ethernet driver bug should be fixed
> - venti should be shown how to use a pipe instead of tcp.
>
> but, i think if you configure a proper loopback using
> loopbackmedium rather than going through your virtual
> ethernet controller, that might just fix the problem.
>
> - erik
>
>

Re: [9fans] vmware oddity (Fusion on Mac OS X)

[erik quanstrom]

> <link>
> http://fxr.watson.org/fxr/source/pc/devether.c?v=PLAN9#L202
> </link>

you may wish to give "standard" (at least to 9fans) links
to code, e.g:

	/sys/src/9/pc/devether.c:202

you would probablly benefit from removing the print statements.
they're potentially going to make the problem much worse.
/net/ether0/stats will have the statistic so it can be tracked there
without printing on each error.

i would imagine snoopy would be informative.

- erik