From owner-freebsd-questions Wed Nov 14 12:32:32 2001 Delivered-To: freebsd-questions@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 5759337B405; Wed, 14 Nov 2001 12:32:29 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 14 Nov 2001 20:32:28 +0000 (GMT) To: "Richard E. Hawkins" Cc: freebsd-questions@FreeBSD.ORG, marcel@FreeBSD.ORG Subject: Re: vmware looking for /dev/vmnet1 rather than 0 In-Reply-To: Your message of "Wed, 14 Nov 2001 12:57:35 EST." <200111141757.fAEHvZl05033@fac13.ds.psu.edu> Date: Wed, 14 Nov 2001 20:32:28 +0000 From: Ian Dowse Message-ID: <200111142032.aa79929@salmon.maths.tcd.ie> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200111141757.fAEHvZl05033@fac13.ds.psu.edu>, "Richard E. Hawkins" w rites: >vmware has been working fine for months. Suddenly it is now looking >for the wrong virtual network device, /dev/vmnet1, rather than >/dev/vmnet0 (isn't that where it normally goes?) I think it always used vmnet1, but something has definitely broken in the last few weeks. I suspect the changes to the linuxulator are the cause, but vmware's freebsd shims do weird things that probably depended too much on the internal workings of the linux emulation code. A ktrace of vmware as it fails shows that it opens /compat/linux/dev/vmnet1 and attempts to do a SIOCGIFADDR ioctl on that descriptor (i.e a socket ioctl on a character device descriptor) but gets an EINVAL return. I haven't figured out for sure if it uses the linux (0x8915) or freebsd number for the ioctl. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message