Date: Fri, 27 Feb 2004 20:01:15 +0100 (CET) From: Orlando Bassotto <orlando.bassotto@ieo-research.it> To: FreeBSD-gnats-submit@FreeBSD.org Subject: ports/63466: VMware3 on recent 5.2-CURRENT Message-ID: <200402271901.i1RJ1FRE076304@mad.ieo-research.it> Resent-Message-ID: <200402271900.i1RJ0M5E029110@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 63466 >Category: ports >Synopsis: VMware3 on recent 5.2-CURRENT >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: update >Submitter-Id: current-users >Arrival-Date: Fri Feb 27 11:00:21 PST 2004 >Closed-Date: >Last-Modified: >Originator: Orlando Bassotto >Release: FreeBSD 5.2-CURRENT i386 >Organization: >Environment: System: FreeBSD haze.n3.home 5.2-CURRENT FreeBSD 5.2-CURRENT #1: Fri Feb 27 07:32:00 CET 2004 nextie@haze.n3.home:/usr/src/sys/i386/compile/HAZE i386 >Description: After the device megapatch a new field in the cdevsw structure is needed, d_version, this patch is addressed to satisfy this requirement. I've also integrated the change from vm_page_alloc_contig to contigmalloc in this patch, so there's no more need of the patch-aa file. Another problem arised with 5.2-CURRENT as today, with WITNESS enabled; almost immediatly, after the vm has been powered up, the kernel will panic in vm_page_free_toq as a consequence of a call to contigmalloc. There's a post in freebsd-current (Feb 04), from Andre Guibert de Bruet about an identical problem, but in a completly different place. As a workaround disable WITNESS, I didn't experience any problem after that. And yet, there's another problem, but on the networking side. The problem isn't a big concern, but involves changes to the rc.d script. vmnet device has a new minor, ifname numbering starts from 4096 and the devices vmmon and vmnet1 in /compat/linux/dev are not needed anymore. If someone has an idea how to patch the rc.d scripts in an elegant way to accomodate these changes, feel free to mail me, and/or if you can directly commit to CVS a patch for it, would be very appreciated. >How-To-Repeat: >Fix: Check out http://bag.ieo-research.it/~nextie/vmware3/ for the new patch to the port, if someone can commit it I would be very thankful. For the panic, the workaround is to disable WITNESS. For the network, on the webpage I've included steps and a patch for the rc.d script. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200402271901.i1RJ1FRE076304>