PV crash

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

Xen 4.2 PV fails to boot -CURRENT PV domU

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 is

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

Hi, thanks, let me try your suggestion/patch. On Sep 9, 2013, at 13:53, Roger Pau Monné roger@citrix.com 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,

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

Hi, On Sep 9, 2013, at 14:06, Eggert, Lars l...@netapp.com 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 dumpon: /dev

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

Hi, On Sep 9, 2013, at 16:02, Roger Pau Monné roger@citrix.com 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.

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

On 2015-5-13, at 10:54, Roger Pau Monné roger@citrix.com 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

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

On 2015-5-13, at 18:00, Eggert, Lars l...@netapp.com wrote: On 2015-5-13, at 16:46, Roger Pau Monné roger@citrix.com 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

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

On 2015-5-15, at 13:59, Roger Pau Monné roger@citrix.com 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

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

On 2015-5-13, at 16:52, Roger Pau Monné roger@citrix.com 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

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

On 2015-5-15, at 16:42, Eggert, Lars l...@netapp.com 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

On 2015-5-15, at 16:14, Roger Pau Monné roger@citrix.com 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

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

On 2015-5-15, at 16:35, Roger Pau Monné roger@citrix.com 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: Intel(R) C600 Series Chipset SAS Controller (SATA mode) port

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

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

Xen dom0 crash

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

On 2015-5-18, at 15:39, Roger Pau Monné roger@citrix.com 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!

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

I'll test Friday, thanks. On 2015-5-13, at 16:52, Roger Pau Monné roger@citrix.com wrote: El 13/05/15 a les 15.48, Eggert, Lars ha escrit: isci0: Intel(R) C600 Series Chipset SAS Controller (SATA mode) port 0x6000-0x60ff mem 0xde07c000-0xde07,0xddc0-0xddff irq 16 at device

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

On 2015-5-13, at 16:46, Roger Pau Monné roger@citrix.com 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

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

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: Xen dom0 interrupt storm detected on irq16:; throttling interrupt source

On 2015-5-20, at 17:30, Roger Pau Monné roger@citrix.com 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

Re: Xen dom0 crash

On 2015-5-22, at 18:27, Roger Pau Monné roger@citrix.com 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=revisionrevision=386935 Will this make it into upstream Xen? Lars signature.asc

Re: Xen dom0 crash

On 2015-10-20, at 17:13, Eggert, Lars <l...@netapp.com> 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 > &

Re: Xen dom0 crash

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

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

Re: Xen dom0 crash

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