Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs for tag 'vmware'

This is an experimental report containing PRs for tag 'vmware' as of 4-24-2014. GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '[<tagname>]' to the Synopsis field. Consider this a prototype of a better search function.

This report is generated statically.

Please give feedback on this report to linimon@FreeBSD.org. Thanks.


PRs for tag 'vmware':
SSubmittedTrackerResp.Description
o2014/01/23kern/186051emulation[vmware] [panic] FreeBSD 8.4+, 9.x+, 10.0 guest panic with VMWare Server on boot
o2013/01/02kern/174908emulation[vmware] "unsupportable block size 0" after upgrading from 9.0-RELEASE-p5 to 9.1-RELEASE [regression]
o2011/05/01kern/156749[vmware] FreeBSD 8.2 does infinite disk access in VMware 3.1.4
f2011/04/28kern/156691emulation[vmware] [panic] panic when using hard disks as RAW devices within VMWare ESXi 4.1-u1
o2010/06/11kern/147793emulation[vmware] [panic] cdrom handling, panic, possible race condition in kernel SMP
o2001/11/02kern/31708[vm] [vmware] VM system / fsync / flushing delayed indefinitely?
6 problems total.

Bugs can be in one of several states:

o - open
A problem report has been submitted, no sanity checking performed.
a - analyzed
The problem is understood and a solution is being sought.
f - feedback
Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
p - patched
A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
r - repocopy
The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
s - suspended
The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
c - closed
A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.