Current problem reports assigned to freebsd-xen@FreeBSD.org
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/180788 xen[xen] [panic] XEN PV kernel 9.2-BETA1 panics on boot o kern/180403 xen[xen] Problems with GENERIC and XENHVM kernels with Xe o kern/180402 xen[xen] XEN kernel does not load in XenClient 4.5.5 o kern/179814 xen[xen] mountroot fails with error=19 under Xen on 9-STA o kern/176471 xen[xen] xn driver crash on detach o kern/176053 xen[xen] [patch] i386: Correct wrong usage of vsnprintf() o kern/175954 xen[xen] XENHVM xn network driver extreme packet loss dur o kern/175822 xen[xen] FreeBSD 9.1 does not work with Xen 4.0 o kern/175757 xen[xen] [patch] xen pvhvm looses keyboard input from VNC o kern/171873 xen[xen] xn network device floods warning in dmesg o kern/171118 xen[xen] FreeBSD XENHVM guest doesn't shutdown cleanly o kern/166174 xen[xen] Problems ROOT MOUNT ERROR freebsd 8.3 o kern/165418 xen[xen] Problems mounting root filesystem from XENHVM o kern/164630 xen[xen] XEN HVM kernel: run_interrupt_driven_hooks: stil o kern/164450 xen[xen] Failed to install FreeeBSD 9.0-RELEASE from CD i o kern/162677 xen[xen] FreeBSD not compatible with Current Stable Xen o kern/161318 xen[xen] sysinstall crashes with floating point exception o kern/155468 xen[xen] Xen PV i386 multi-kernel CPU system is not worki o kern/155353 xen[xen] [patch] put nudging TOD message under boot_ver o kern/154833 xen[xen]: xen 4.0 - DomU freebsd8.2RC3 i386, XEN kernel. o kern/154473 xen[xen] xen 4.0 - DomU freebsd8.1 i386, XEN kernel. Not o kern/154472 xen[xen] xen 4.0 - DomU freebsd8.1 i386 xen kernel reboot o kern/154428 xen[xen] xn0 network interface and PF - Massive performan 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 xenufs 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 p 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 39 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
Re: kern/171118: [xen] FreeBSD XENHVM guest doesn
The following reply was made to PR kern/171118; it has been noted by GNATS. From: Mark Felder f...@feld.me To: shidj sh...@arraynetworks.com.cn, bug-followup bug-follo...@freebsd.org Cc: Subject: Re: kern/171118: [xen] FreeBSD XENHVM guest doesn Date: Mon, 21 Oct 2013 08:00:43 -0500 On Tue, Aug 13, 2013, at 21:01, Jason Shi wrote: Though you may not get exactly what you expect when you really want your VMs to halt. I'm struggling to think of a scenario where I want a VM to halt and not shutdown. ___ 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
Re: kern/171118: [xen] FreeBSD XENHVM guest doesn
The following reply was made to PR kern/171118; it has been noted by GNATS. From: Mark Felder f...@feld.me To: bug-followup bug-follo...@freebsd.org Cc: Subject: Re: kern/171118: [xen] FreeBSD XENHVM guest doesn Date: Mon, 21 Oct 2013 08:25:47 -0500 Quoting this in a reply to the PR -- it seems Jason's message was rejected by spam perhaps and didn't make it into GNATS? On Tue, Aug 13, 2013, at 21:01, Jason Shi wrote: After we lanuch a shutdown operation in Xen Center, Xen Server issues a clean_shutdown operation. And actually the signal sended to VM is halt. We can see that from the xen source log on dom0. e.g.: Aug 13 15:03:48 xenserver-lxpwbbml xenopsd: [debug|xenserver-lxpwbbml|7|Async.VM.clean_shutdown R:832f756cad74|xenops] VM = dc401e38-97af-5972-7150-d067d701fa88; domid = 115; Requesting domain halt FreeBSD VM receives the signal and do shutdown_nice(RB_HALT). This is a halt action which will not lead to a poweroff ending. So the VM domain will not be destroyed. Xen Server expected the target domain to be destroyed until it times out. Then Xen Center gets a timeout and it logs shutdown failed then. I think this a xen bug. But as a workaround, you can modify the xctrl_halt function from: shutdown_nice(RB_HALT); to shutdown_nice(RB_POWEROFF|RB_HALT); Though you may not get exactly what you expect when you really want your VMs to halt. Jason Shi ___ 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
