VMware Patches

Sascha Holzleiter

unread,

Nov 16, 2001, 9:59:42 AM11/16/01

to

Hello,

i just tried the patches for the VMWare 'could not get address' issue
but it seems it didn't resolve the problem.
VMWare is still complaining about the same thing. Only one additional
errormessage I get on the console :

linux: 'ioctl' fd=19, cmd=0x8915 ('~I',21) not implemented

Did I something wrong ?

The System is a recent FreeBSD-Stable 4.4

To Unsubscribe: send mail to majo...@FreeBSD.org
with "unsubscribe freebsd-emulation" in the body of the message

Dag-Erling Smorgrav

unread,

Nov 16, 2001, 10:15:52 AM11/16/01

to

Sascha Holzleiter <ape...@mother.chief.home> writes:
> linux: 'ioctl' fd=19, cmd=0x8915 ('~I',21) not implemented
>
> Did I something wrong ?

No, 0x8915 is LINUX_SIOCGIFADDR which is not implemented in -STABLE.

DES
--
Dag-Erling Smorgrav - d...@ofug.org

Dag-Erling Smorgrav

unread,

Nov 16, 2001, 10:18:33 AM11/16/01

to

Dag-Erling Smorgrav <d...@ofug.org> writes:
> No, 0x8915 is LINUX_SIOCGIFADDR which is not implemented in -STABLE.

Uh, never mind, actually it's 0x8916 (SIOCSIFADDR) that's not
implemented. The error you're getting comes from a different problem
(doing a socket ioctl on a non-socket fd) which I'm working on fixing
in -CURRENT.

Please use a real email address when posting to the FreeBSD lists.

DES
--
Dag-Erling Smorgrav - d...@ofug.org

To Unsubscribe: send mail to majo...@FreeBSD.org

Gerald Pfeifer

unread,

Nov 16, 2001, 11:00:10 AM11/16/01

to

On 16 Nov 2001, Dag-Erling Smorgrav wrote:
>> No, 0x8915 is LINUX_SIOCGIFADDR which is not implemented in -STABLE.
> Uh, never mind, actually it's 0x8916 (SIOCSIFADDR) that's not
> implemented.

Would you mind MFCing 0x8915 anyway, or is there a problem with doing so?

> The error you're getting comes from a different problem (doing a
> socket ioctl on a non-socket fd) which I'm working on fixing in
> -CURRENT.

Thanks!

Gerald
--
Gerald "Jerry" pfe...@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/

Sascha Holzleiter

unread,

Nov 16, 2001, 2:41:26 PM11/16/01

to

Sorry for the bad email address, didn't update the masquerade table
after some changes in the home-zone.

>implemented. The error you're getting comes from a different problem

>(doing a socket ioctl on a non-socket fd) which I'm working on fixing
>in -CURRENT.

So the patch Ian Dowse posted on this list for the VMware issue is only
for the -CURRENT branch ? Damn...

Is there any way to get VMware back to running on -STABLE ?

Ian Dowse

unread,

Nov 16, 2001, 2:52:59 PM11/16/01

to

In message <2001111620...@mother.chief.home>, Sascha Holzleiter writes:
>So the patch Ian Dowse posted on this list for the VMware issue is only
>for the -CURRENT branch ? Damn...

No, both patches I posted are against -stable. The one I posted a
few hours ago (2001111617...@salmon.maths.tcd.ie) is based
on DES's -current patch, and it is simpler to apply because it
does not involve changing the vmmon module.

(In reply to your earlier message, you probably didn't manage
to install the new version of the vmmon_up.ko module correctly,
or you didn't kldunload and reload it).

Ian

Gerhard Schmidt

unread,

Nov 19, 2001, 3:22:56 AM11/19/01

to

On Fri, Nov 16, 2001 at 09:43:29PM +0100, Sascha Holzleiter wrote:

> On Fri, Nov 16, 2001 at 07:52:48PM +0000, Ian Dowse wrote:
> >
> > (In reply to your earlier message, you probably didn't manage
> > to install the new version of the vmmon_up.ko module correctly,
> > or you didn't kldunload and reload it).
> >
>

> Hmm, I had to recompile the whole port to get it working. Now networking
> is running again. Tnx for that patch ! I really need VMware working.

Would it be possible to commit this patches to -stable. Not all users of
Freebsd have the time to search all Maillists for a patch.

Bye

Estartu