Re: Xen dom0 crash

2015-10-21 Thread Eggert, Lars
On 2015-10-21, at 11:11, Roger Pau Monné wrote: > Are you loading hwpmc by default? Yes. > Performance monitor counters are not > yet implemented in the FreeBSD PVH port, so you should not load hwpmc. I > have to look at providing an error message here rather than panicking. Strange, the same k

Re: Xen dom0 crash

2015-10-21 Thread Eggert, Lars
On 2015-10-21, at 10:53, Roger Pau Monné wrote: > hw.pci.mcfg=0 Thanks! That gets me a bit further, but it now crashes with: ... SMP: AP CPU #7 Launched! SMP: AP CPU #14 Launched! SMP: AP CPU #11 Launched! SMP: AP CPU #21 Launched! SMP: AP CPU #30 Launched! SMP: AP CPU #4 Launched! SMP: AP CPU #

Re: Xen dom0 crash

2015-10-21 Thread Eggert, Lars
On 2015-10-21, at 9:40, Roger Pau Monné wrote: > Can you execute: > > # addr2line -e /boot/kernel/kernel 8097bf80 > > In order to get the file and line where the failure happens? I guess you meant kernel.debug? Then I get: /usr/home/elars/src/sys/amd64/pci/pci_cfgreg.c:365 Which is th

Re: Xen dom0 crash

2015-10-20 Thread Eggert, Lars
On 2015-10-20, at 17:13, Eggert, Lars wrote: > with a recent -CURRENT and xen-4.6.0, I now see a different crash at boot on > the same box. Any ideas? Actually, it's a different box (Supermicro) Lars > &g

Re: Xen dom0 crash

2015-10-20 Thread Eggert, Lars
Hi, with a recent -CURRENT and xen-4.6.0, I now see a different crash at boot on the same box. Any ideas? Thanks, Lars B2 __ _ _ | | | _ \ / | __ \ | |___ _ _

Re: Xen dom0 crash

2015-05-26 Thread Eggert, Lars
On 2015-5-22, at 18:27, Roger Pau Monné wrote: > > The issue mentioned in this thread has been fixed in the xen-kernel port > with the following commit: > > https://svnweb.freebsd.org/ports?view=revision&revision=386935 Will this make it into upstream Xen? Lars signature.asc Description: Mes

Re: Xen dom0 "interrupt storm detected on "irq16:"; throttling interrupt source"

2015-05-20 Thread Eggert, Lars
On 2015-5-20, at 17:30, Roger Pau Monné wrote: > > Did you manage to get past this? > > TBH I don't know why Xen tries to build the tests, my build of tools > doesn't even try to. Yes, I think the issue was that I tried to build Xen 4.5-release. I'm now building master without problems. Lars

Re: Xen dom0 "interrupt storm detected on "irq16:"; throttling interrupt source"

2015-05-18 Thread Eggert, Lars
On 2015-5-18, at 15:39, Roger Pau Monné wrote: > I guess you will have to resort to using > hw.isci.force_legacy_interrupts=1 until I get around to implement MSI-X > support for Xen Dom0, sorry for the trouble. No worries, that's a fine workaround. Thanks for all the help! Lars signature.asc

Re: Xen dom0 "interrupt storm detected on "irq16:"; throttling interrupt source"

2015-05-18 Thread Eggert, Lars
Unfortunately, the storm is still there with this patch. On 2015-5-15, at 18:28, Roger Pau Monné wrote: > > El 15/05/15 a les 16.42, Eggert, Lars ha escrit: >> On 2015-5-15, at 16:35, Roger Pau Monné wrote: >>> >>> Yes, but I've realized that isci for exampl

Xen dom0 crash

2015-05-18 Thread Eggert, Lars
Hi, I'm trying to boot a Xen dom0 on another machine (Fujitsu RX308) and Xen crashes when starting the kernel. Log below; any ideas? Thanks, Lars B2 __ _ _ | | | _

Re: Xen dom0 "interrupt storm detected on "irq16:"; throttling interrupt source"

2015-05-15 Thread Eggert, Lars
On 2015-5-15, at 16:42, Eggert, Lars wrote: > > Will now set hw.isci.force_legacy_interrupts=1 and check if the device then > works correctly. That seems to be the case. Lars signature.asc Description: Message signed with OpenPGP using GPGMail

Re: Xen dom0 "interrupt storm detected on "irq16:"; throttling interrupt source"

2015-05-15 Thread Eggert, Lars
On 2015-5-15, at 16:35, Roger Pau Monné wrote: > > Yes, but I've realized that isci for example passes an uint32_t instead > of an int, so it might be best to set it to 0. Here is what I see now: isci0: port 0x6000-0x60ff mem 0xde07c000-0xde07,0xddc0-0xddff irq 16 at device 0.0 o

Re: Xen dom0 "interrupt storm detected on "irq16:"; throttling interrupt source"

2015-05-15 Thread Eggert, Lars
On 2015-5-15, at 16:14, Roger Pau Monné wrote: > I've attached another patch that will force isci to print some > messages, can you try that? Trying this now. > + *irq = 0; FWIW, this was "*irq = -1" in your previous patch... Lars signature.asc Description: Message signed with OpenPGP u

Re: Xen dom0 "interrupt storm detected on "irq16:"; throttling interrupt source"

2015-05-15 Thread Eggert, Lars
On 2015-5-15, at 13:59, Roger Pau Monné wrote: > Can you provide the bootlog with the patch applied? Below. > Also, can you try if there's any difference when setting: > hw.isci.force_legacy_interrupts=1 > on /boot/loader.conf? That seems to elimintate the storm. The isci line is now simply: i

Re: Xen dom0 "interrupt storm detected on "irq16:"; throttling interrupt source"

2015-05-15 Thread Eggert, Lars
On 2015-5-13, at 18:00, Eggert, Lars wrote: > > On 2015-5-13, at 16:46, Roger Pau Monné wrote: >> I guess migration-rdma gets compiled because Qemu detects that you have >> some library and assumes that you want it enabled. Did you install >> something new between your p

Re: Xen dom0 "interrupt storm detected on "irq16:"; throttling interrupt source"

2015-05-15 Thread Eggert, Lars
On 2015-5-13, at 16:52, Roger Pau Monné wrote: > I have a patch for FreeBSD which > might solve it, however I don't have any similar box I can use to test > it, would you mind giving it a spin? Unfortunately, the irq storm is still present with that patch applied. Lars signature.asc Descriptio

Re: Xen dom0 "interrupt storm detected on "irq16:"; throttling interrupt source"

2015-05-13 Thread Eggert, Lars
I'll test Friday, thanks. On 2015-5-13, at 16:52, Roger Pau Monné wrote: > > El 13/05/15 a les 15.48, Eggert, Lars ha escrit: >> isci0: port >> 0x6000-0x60ff mem 0xde07c000-0xde07,0xddc0-0xddff irq 16 at >> device 0.0 on pci10 >> isci0: attemp

Re: Xen dom0 "interrupt storm detected on "irq16:"; throttling interrupt source"

2015-05-13 Thread Eggert, Lars
On 2015-5-13, at 16:46, Roger Pau Monné wrote: > I guess migration-rdma gets compiled because Qemu detects that you have > some library and assumes that you want it enabled. Did you install > something new between your previous build of Xen and this one? Yes, this box has world built with OFED. I

Re: Xen dom0 "interrupt storm detected on "irq16:"; throttling interrupt source"

2015-05-13 Thread Eggert, Lars
Also, building the xen tools currently seems to fail with: gmake[3]: Entering directory '/usr/home/elars/xen/tools/qemu-xen-dir-remote' GEN config-host.h GEN trace/generated-tracers.h GEN trace/generated-tcg-tracers.h GEN trace/generated-helpers-wrappers.h GEN trace/generated-h

Re: Xen dom0 "interrupt storm detected on "irq16:"; throttling interrupt source"

2015-05-13 Thread Eggert, Lars
On 2015-5-13, at 10:54, Roger Pau Monné wrote: > Can you post the full output of vmstat -i and the log of Xen and FreeBSD > booting (with boot_verbose=YES)? If you don't have a serial console > setup you can get the Xen boot log using xl dmesg. Here you go: Xen 4.6-unstabletcp.ko size 0x2f90 at

Xen dom0 "interrupt storm detected on "irq16:"; throttling interrupt source"

2015-05-13 Thread Eggert, Lars
Hi, with Xen from git and a recent -CURRENT, I get "interrupt storm detected on "irq16:"; throttling interrupt source" messages on the dom0 console about once a second. irq16 is used for ehci: # vmstat -i | grep irq16 irq16: ehci0 1229805 6559 Any ideas? Thanks, Lars

Re: xn devices not working on rootbsd VPSs

2014-12-19 Thread Eggert, Lars
On 2014-12-16, at 16:01, Roger Pau Monné wrote: > Can you try if it solves your issue? Ran into the same issue and can confirm this patch makes xn work again here. Lars signature.asc Description: Message signed with OpenPGP using GPGMail

Re: FreeBSD PVHVM call for testing

2013-10-11 Thread Eggert, Lars
Hi, On May 13, 2013, at 20:32, Roger Pau Monné wrote: > Right now the code is in a state where it can be tested by users, so we > would like to encourage FreeBSD and Xen users to test it and provide > feedback. any idea if/when this code will be merged into -CURRENT? Thanks, Lars signature.as

Re: Xen 4.2 PV fails to boot -CURRENT PV domU

2013-09-09 Thread Eggert, Lars
Hi, On Sep 9, 2013, at 16:02, Roger Pau Monné wrote: > Applying the patch I've sent and reverting r244237 seems to be enough > for me, I can get the guest to boot fine. same here, now that I removed the "TARGET_CPUTYPE=core2" flag that had been left over in the local setup. Thanks, Lars sig

Re: Xen 4.2 PV fails to boot -CURRENT PV domU

2013-09-09 Thread Eggert, Lars
Hi, On Sep 9, 2013, at 14:06, "Eggert, Lars" wrote: > thanks, let me try your suggestion/patch. I applied the patch and tried booting. That failed (as expected) with a "bad pte" panic: ... Trying to mount root from ufs:/dev/ada0s1a []... start_init: trying /sbin/init

Re: Xen 4.2 PV fails to boot -CURRENT PV domU

2013-09-09 Thread Eggert, Lars
Hi, On Sep 9, 2013, at 14:16, Roger Pau Monné wrote: > Performance will probably be better on most workloads with PVHVM if you > have HAP (Intel's Extended Page Table or AMD's Nested Page Tables). And > also, i386 PV port is limited to only one vcpu, while PVHVM will allow > you to use as many v

Re: Xen 4.2 PV fails to boot -CURRENT PV domU

2013-09-09 Thread Eggert, Lars
Hi, thanks, let me try your suggestion/patch. On Sep 9, 2013, at 13:53, Roger Pau Monné wrote: > May I ask if there's anything that prevents you from switching to the > PVHVM port? I wouldn't recommend using the i386 PV port. I was thinking that performance would be better, and resource require

Xen 4.2 PV fails to boot -CURRENT PV domU

2013-09-09 Thread Eggert, Lars
Hi, I'm trying to run a recent-CURRENT XEN i386 kernel in a Xen 4.2 PV domU. I had to add the following options to the kernel config file in order to compile the XEN kernel: makeoptions WITHOUT_MODULES+="mlx4 mlx4ib mlxen mthca" The resulting kernel compiles, but fails to boot. Attached i

Re: PV crash

2013-06-28 Thread Eggert, Lars
Hi, On Jun 27, 2013, at 22:38, Sean Bruno wrote: > On Wed, 2013-06-26 at 13:40 +0000, Eggert, Lars wrote: >> real memory = 67108864 (64 MB) >> avail memory = 58556416 (55 MB) > > That looks a bit small for a x86 instance of FreeBSD 10 IMO. > Try bumping that to >512

PV crash

2013-06-26 Thread Eggert, Lars
Hi, I'm trying to get my feet wet with running the i386 PV -CURRENT kernel under Xen 4.1. It seems to crash immediately after the kernel has booted. Any ideas? Trace below. Thanks, Lars Using config file "./xenfreebsd.cfg". Started domain xenfreebsd (id=30) WARNING: loader(8) metadata is miss