Re: FreeBSD 10-R 8 vCPU panics at boot under XenServer (on 8 'core' CPU)
--On 24 February 2014 18:19:43 +0100 Roger Pau Monné wrote: I've passed through a dual port BCE card (Broadcom NetXtreme II BCM5709) without problems. As a test, could you try to only pass the nic or the SAS controller to see if we can figure out if this is specific to one of the devices? Ok, I tried several boots just passing through the LSI - all boots succeeded. There's quite a variance between how long it takes to 'launch' the CPU's. On a good run you'll get 'Netvsc initializing' small pause, then Launches 5 CPU's, another small pause - and the remaining 2 launch. On a bad boot you'll get quite a long pause before the first launch, then a few more pop in - then a very long pause before the final one(s) launch. I then changed to just passing through the NIC's - you get similar results - it's markedly slower than if nothing is passed through, but not so slow it fails. It's only if you pass through the NIC's and the LSI - it's *really* slow - to the point that without upping the NUM_RETRIES in the patch you did it often panics (unable to schedule timer). Some of these boots can take minutes (but, shut down the VM and try it again and it'll complete "relatively quickly" - i.e. 20-30 seconds). I can probably video some of the boots and give you a link off list to the footage (that'd probably give you a better idea of the timing involved). I don't have the other machine running at the moment - so I can't do any testing of what performance you actually get from the passed through devices - they 'seem' to work ok from the limited testing I've done. -Karl ___ 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: FreeBSD 10-R 8 vCPU panics at boot under XenServer (on 8 'core' CPU)
On 17/02/14 21:00, Karl Pielorz wrote: > > --On 17 February 2014 16:56:14 +0100 Roger Pau Monné > wrote: > >> In order to provide more debug info, could you apply the following patch: >> >> http://xenbits.xen.org/people/royger/0001-xen-debug-Xen-PV-timer.patch >> >> It will expand the panic message a little bit. Also, after applying the >> patch you can manually edit sys/dev/xen/timer/timer.c and increase >> NUM_RETRIES to see if that solves the problem. > > Ok, tried adjusting the NUM_RETRIES #define in that patch (I left the > PCI passthroughs in place at the moment). I had no idea what to set it > to - so I went for 600. With it set at 600 that same guest now boots Ok > now every time I've tried. > > But I did notice the whole 'SMP AP CPU #x Launched!' takes forever, and > varies a lot (e.g. one boot it took nearly 2 minutes to launch all CPU's > and continue). > > I removed the PCI passthroughs on that guest, and it now flies through > the AP launches. Unfortunately though I need the passthroughs :( > > I've passed through the onboard LSI 2308 SAS controller (mps), and a > dual port PCI-E Intel NIC (igb) - all the passthroughs work on FreeBSD > once it's booted - but obviously, not without causing the slow AP CPU > launches. I've passed through a dual port BCE card (Broadcom NetXtreme II BCM5709) without problems. As a test, could you try to only pass the nic or the SAS controller to see if we can figure out if this is specific to one of the devices? > I also remembered I set 'hw.pci.enable_msi=1' and 'hw.pci.enable_msix=0' > in /etc/sysctl.conf - someone else found that was necessary to use the > LSI in passthrough mode. > > Aside from the slow launches, do you think (as they work) it's going to > cause issues leaving those passthroughs active? Not sure, still have to figure out what's going on. Roger. ___ 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"
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/183139 xen[xen] [patch] ifconfig options on xn0 lost after xen v 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 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 40 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"
