Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o kern/154302  xen        [xen] [panic] [patch] xn0: Error 2 parsing device/vif/
o kern/153789  xen        [xen] [regression] FreeBSD 8.2-RC1 crashes under Solar
o kern/153674  xen        [xen] i386/XEN idle thread shows wrong percentages
o kern/153672  xen        [xen] [panic] i386/XEN panics under heavy fork load
o kern/153620  xen        [xen] Xen guest system clock drifts in AWS EC2 (FreeBS
o kern/153477  xen        [xen] XEN pmap code abuses vm page queue lock
o kern/153150  xen        [xen] xen/ec2: disable checksum offloading on interfac
o kern/152228  xen        [xen] [panic] Xen/PV panic with machdep.idle_mwait=1
o kern/144629  xen        [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor
o kern/143398  xen        [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor
o kern/143340  xen        [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor
f kern/143069  xen        [xen] [panic] Xen Kernel Panic - Memory modified after
f kern/135667  xen        ufs filesystem corruption on XEN DomU system
f kern/135421  xen        [xen] FreeBSD Xen PVM DomU network failure - netfronc.
f kern/135178  xen        [xen] Xen domU outgoing data transfer stall when TSO i
o kern/135069  xen        [xen] FreeBSD-current/Xen SMP doesn't function at all 
f i386/124516  xen        [xen] FreeBSD-CURRENT Xen Kernel Segfaults when config
o kern/118734  xen        [xen] FreeBSD 6.3-RC1 and FreeBSD 7.0-BETA 4 fail to b

18 problems total.

_______________________________________________
freebsd-xen@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"

Reply via email to