Subject: Re: vmware's vmnet doesn't compile in -current
To: Mario Kemper <firstname.lastname@example.org>
From: Duncan McEwan <email@example.com>
Date: 06/16/2001 23:32:52
> i wanted to give vmware another try and as i'm running -current, i wanted to
> compile the kernel modules first. The problem ist, that vmnet doesn't build
> anymore. This is due to the fact that the macro ETHER_MAX_FRAME in
> /usr/include/net/if_ether.h changed from
> #define ETHER_MAX_FRAME(etype, hasfcs) to
> #define ETHER_MAX_FRAME(ifp, etype, hasfcs)
I just encountered the exact same problem. I kludged around it temporarily
by ifdefing out the couple of places in if_hubmod.c where the macro
HUBMAXPKT was used. As far as I could see from the comments, they were both
testing conditions that "should never happen anyway".
With those modules recompiled and running in a 1.5W kernel, I can report
that vmware now gets further than it did with a 1.5U kernel when installing
windows 98 in a virtual disk. It now seems to complete the install fine,
whereas before it wedged part way through the install.
I haven't exercised the windows installation much, so I can't yet comment
on how reliably it works.