Re: [Xen-devel] Some Xen pci-passthrough questions

On 27/10/17 00:30, Boris Ostrovsky wrote: > On 10/26/2017 04:48 PM, Sander Eikelenboom wrote: >> Hi Boris / Andrew, >> >> In the aftermath of the linux mmap path I have some questions regarding >> pci-passthrough: >> >> - Is pci-passthrough in combinatio

[Xen-devel] Some Xen pci-passthrough questions

Hi Boris / Andrew, In the aftermath of the linux mmap path I have some questions regarding pci-passthrough: - Is pci-passthrough in combination with an auto-ballooning dom0 supposed to be a supported combination ? I have used dom0_maxmem settings for dom0 since ages and that works fine

Re: [Xen-devel] ce56a86e2a ("x86/mm: Limit mmap() of /dev/mem to valid physical addresses"): kernel BUG at arch/x86/mm/physaddr.c:79!

On 26/10/17 19:49, Craig Bergstrom wrote: > Sander, thanks for the details, they've been very useful. > > I suspect that your host system's mem=2048M parameter is causing the > problem. Any chance you can confirm by removing the parameter and > running the guest code path? I removed it, but

Re: [Xen-devel] Xen-unstable + dom0 linux-4.14-rc6: bisected pci-passthrough problem to HVM

On 25/10/17 22:34, Boris Ostrovsky wrote: > On 10/25/2017 04:05 PM, Sander Eikelenboom wrote: >> Hi Juergen and Boris, >> >> While testing out linux 4.14-rc6 i found some trouble with one of my devices >> for which I use pci-passthrough. >> It fails to start

Re: [Xen-devel] pci-passthrough loses msi-x interrupts ability after domain destroy

On 22/09/17 04:09, Christopher Clark wrote: > On Thu, Sep 21, 2017 at 1:27 PM, Sander Eikelenboom > <li...@eikelenboom.it> wrote: >> >> On Thu, September 21, 2017, 10:39:52 AM, Roger Pau Monné wrote: >> >>> On Wed, Sep 20, 2017 at 03:50:35PM -0400, Jérôme

Re: [Xen-devel] pci-passthrough loses msi-x interrupts ability after domain destroy

Thursday, September 21, 2017, 10:39:52 AM, you wrote: > On Wed, Sep 20, 2017 at 03:50:35PM -0400, Jérôme Oufella wrote: >> Hi Xen-devel, >> >> I'm using PCI pass-through to map a PCIe (intel i210) controller into >> a HVM domain. The system uses xen-pciback to hide the appropriate PCI >>

Re: [Xen-devel] Xen-unstable / Qemu-upstream: QMP server: Unsupported bus. Bus doesn't have property 'acpi-pcihp-bsel' set

On 10/08/17 18:45, Anthony PERARD wrote: > On Thu, Aug 10, 2017 at 03:00:56PM +0100, Anthony PERARD wrote: >> On Wed, Aug 09, 2017 at 06:34:43PM +0200, Sander Eikelenboom wrote: >>> L.S., >>> >>> It seems the xen qemu-upstream tree got updated from qemu upstrea

[Xen-devel] Xen-unstable / Qemu-upstream: QMP server: Unsupported bus. Bus doesn't have property 'acpi-pcihp-bsel' set

L.S., It seems the xen qemu-upstream tree got updated from qemu upstream last week. Unfortunately a change breaks pci-passthrough for HVM's: libxl: error: libxl_qmp.c:287:qmp_handle_error_response: Domain 20:received an error message from QMP server: Unsupported bus. Bus doesn't have

Re: [Xen-devel] Resend: Linux 4.11-rc7: kernel BUG at drivers/xen/events/events_base.c:1221

On 25/04/17 16:07, Juergen Gross wrote: > On 25/04/17 15:12, Sander Eikelenboom wrote: >> On 25/04/17 14:49, Juergen Gross wrote: >>> On 25/04/17 12:33, Sander Eikelenboom wrote: >>>> On 25/04/17 09:01, Juergen Gross wrote: >>>>> On 25/04/17 08:57, Sa

Re: [Xen-devel] Resend: Linux 4.11-rc7: kernel BUG at drivers/xen/events/events_base.c:1221

On 25/04/17 14:49, Juergen Gross wrote: > On 25/04/17 12:33, Sander Eikelenboom wrote: >> On 25/04/17 09:01, Juergen Gross wrote: >>> On 25/04/17 08:57, Sander Eikelenboom wrote: >>>> On 25/04/17 08:42, Juergen Gross wrote: >>>>> On 25/04/17 08:35, Sa

Re: [Xen-devel] Resend: Linux 4.11-rc7: kernel BUG at drivers/xen/events/events_base.c:1221

On 25/04/17 13:38, Juergen Gross wrote: > On 25/04/17 13:28, Sander Eikelenboom wrote: >> On 25/04/17 13:00, Juergen Gross wrote: >>> On 25/04/17 12:33, Sander Eikelenboom wrote: >>>> On 25/04/17 09:01, Juergen Gross wrote: >>>>> On 25/04/17 08:57, Sa

Re: [Xen-devel] Resend: Linux 4.11-rc7: kernel BUG at drivers/xen/events/events_base.c:1221

On 25/04/17 13:00, Juergen Gross wrote: > On 25/04/17 12:33, Sander Eikelenboom wrote: >> On 25/04/17 09:01, Juergen Gross wrote: >>> On 25/04/17 08:57, Sander Eikelenboom wrote: >>>> On 25/04/17 08:42, Juergen Gross wrote: >>>>> On 25/04/17 08:35, Sa

Re: [Xen-devel] Resend: Linux 4.11-rc7: kernel BUG at drivers/xen/events/events_base.c:1221

On 25/04/17 09:01, Juergen Gross wrote: > On 25/04/17 08:57, Sander Eikelenboom wrote: >> On 25/04/17 08:42, Juergen Gross wrote: >>> On 25/04/17 08:35, Sander Eikelenboom wrote: >>>> (XEN) [2017-04-24 21:20:53.203] d0v0 Unhandled invalid opcode fault/trap >>&

Re: [Xen-devel] Resend: Linux 4.11-rc7: kernel BUG at drivers/xen/events/events_base.c:1221

On 25/04/17 08:42, Juergen Gross wrote: > On 25/04/17 08:35, Sander Eikelenboom wrote: >> On 25/04/17 08:14, Juergen Gross wrote: >>> On 24/04/17 22:15, Boris Ostrovsky wrote: >>>> On 04/24/2017 12:10 PM, Sander Eikelenboom wrote: >>>>> On 24/04/17

Re: [Xen-devel] Resend: Linux 4.11-rc7: kernel BUG at drivers/xen/events/events_base.c:1221

On 25/04/17 08:14, Juergen Gross wrote: > On 24/04/17 22:15, Boris Ostrovsky wrote: >> On 04/24/2017 12:10 PM, Sander Eikelenboom wrote: >>> On 24/04/17 17:49, Boris Ostrovsky wrote: >>>> On 04/24/2017 10:20 AM, Sander Eikelenboom wrote: >>>>> Hi

Re: [Xen-devel] Resend: Linux 4.11-rc7: kernel BUG at drivers/xen/events/events_base.c:1221

On 24/04/17 17:49, Boris Ostrovsky wrote: > On 04/24/2017 10:20 AM, Sander Eikelenboom wrote: >> Hi Boris, >> >> Nope, not that i am aware of. > > If you can keep console while running this, can you add these changes > and see if we ever unbind the work vecto

Re: [Xen-devel] Resend: Linux 4.11-rc7: kernel BUG at drivers/xen/events/events_base.c:1221

Hi Boris, Nope, not that i am aware of. -- Sander On 24/04/17 16:17, Boris Ostrovsky wrote: > On 04/24/2017 06:06 AM, Sander Eikelenboom wrote: >> Resend: Sorry copy and pasted a wrong mailadress for the xen-devel list. >> >> >> Hi Boris / Juergen, >> >&

[Xen-devel] Resend: Linux 4.11-rc7: kernel BUG at drivers/xen/events/events_base.c:1221

Resend: Sorry copy and pasted a wrong mailadress for the xen-devel list. Hi Boris / Juergen, This morning i got this dom0 kernel crash (it occurred sporadically before (during 4.11), but i didn't have serial console enabled at that time so i had no stacktrace, only sporadic reboots). It's

Re: [Xen-devel] Legacy PCI interrupt {de}assertion count

On 04/04/17 18:07, Konrad Rzeszutek Wilk wrote: > On Mon, Apr 03, 2017 at 02:22:36PM +0200, Sander Eikelenboom wrote: >> On 31/03/17 16:38, Konrad Rzeszutek Wilk wrote: >>> On Fri, Mar 31, 2017 at 04:46:27AM -0600, Jan Beulich wrote: >>>>>>> On 31.03.17

Re: [Xen-devel] Legacy PCI interrupt {de}assertion count

On 31/03/17 16:38, Konrad Rzeszutek Wilk wrote: > On Fri, Mar 31, 2017 at 04:46:27AM -0600, Jan Beulich wrote: > On 31.03.17 at 10:07, wrote: >>> On Fri, Mar 31, 2017 at 05:05:44AM +, Tian, Kevin wrote: > From: Jan Beulich [mailto:jbeul...@suse.com] > Sent:

Re: [Xen-devel] Backport / cherrypick request for xen 4.8.1 patches fixing direct kernel boot regression

On 15/03/17 13:08, Wei Liu wrote: > On Wed, Mar 15, 2017 at 01:01:52PM +0100, Sander Eikelenboom wrote: >> Hi Ian / Wei, >> >> Qemu-xen commits: >> 021746c131cdfeab9d82ff918795a9f18d20d7ae PCMachineState: introduce >> acpi_build_enabled field >> 804ba7c10b

[Xen-devel] Backport / cherrypick request for xen 4.8.1 patches fixing direct kernel boot regression

Hi Ian / Wei, Qemu-xen commits: 021746c131cdfeab9d82ff918795a9f18d20d7ae PCMachineState: introduce acpi_build_enabled field 804ba7c10bbc66bb8a8aa73ecc60f620da7423d5 xen: Fix xenpv machine initialisation (the second one is a fix for the first one) Fixed a regression with direct kernel boot,

Re: [Xen-devel] [PATCH] x86/cpuid: Fix booting on AMD Phenom 6-core platform

On 03/03/17 11:48, Andrew Cooper wrote: > On 03/03/17 10:47, Sander Eikelenboom wrote: >> On 03/03/17 11:40, Andrew Cooper wrote: >>> On 02/03/17 20:02, Andrew Cooper wrote: >>>> c/s 5cecf60f4 "x86/cpuid: Handle leaf 0x1 in guest_cpuid()" causes Li

Re: [Xen-devel] [PATCH] x86/cpuid: Fix booting on AMD Phenom 6-core platform

tered to be >> more consistent across guests. Revert back to the previous behaviour, by >> limiting the apic_id adjustment to HVM guests only. Whomever gets to fixes >> topology representation is going to have a lot of fun with non-power-of-2 AMD >> boxes. >> >

Re: [Xen-devel] Xen-unstable: Bisected Host boot failure on AMD Phenom

On 02/03/17 20:17, Andrew Cooper wrote: > On 02/03/17 19:15, Boris Ostrovsky wrote: >> On 03/02/2017 01:56 PM, Andrew Cooper wrote: >>> On 02/03/17 18:51, Sander Eikelenboom wrote: >>>> On 02/03/17 19:29, Andrew Cooper wrote: >>>>> On 02/03/17 18:25, Sa

Re: [Xen-devel] Xen-unstable: Bisected Host boot failure on AMD Phenom

On 02/03/17 19:29, Andrew Cooper wrote: > On 02/03/17 18:25, Sander Eikelenboom wrote: >> On 02/03/17 18:38, Andrew Cooper wrote: >>> On 02/03/17 17:29, Sander Eikelenboom wrote: >>>> On 02/03/17 15:55, Andrew Cooper wrote: >>>>> On 02/03/17 14:42, San

Re: [Xen-devel] Xen-unstable: Bisected Host boot failure on AMD Phenom

On 02/03/17 18:38, Andrew Cooper wrote: > On 02/03/17 17:29, Sander Eikelenboom wrote: >> On 02/03/17 15:55, Andrew Cooper wrote: >>> On 02/03/17 14:42, Sander Eikelenboom wrote: >>>> Hi Andrew / Jan, >>>> >>>> While testing current xen-unstab

Re: [Xen-devel] Xen-unstable: Bisected Host boot failure on AMD Phenom

On 02/03/17 15:55, Andrew Cooper wrote: > On 02/03/17 14:42, Sander Eikelenboom wrote: >> Hi Andrew / Jan, >> >> While testing current xen-unstable staging i ran into my host rebooting in >> early kernel boot. >> Bisection has turned up: >> 5

[Xen-devel] Xen-unstable: Bisected Host boot failure on AMD Phenom

Hi Andrew / Jan, While testing current xen-unstable staging i ran into my host rebooting in early kernel boot. Bisection has turned up: 5cecf60f439e828f4bc0d2a368ced9a73b130cb7 is the first bad commit Author: Andrew Cooper Date: Fri Feb 17 17:10:50 2017

Re: [Xen-devel] Xenstore watch interface in the kernel

Thursday, December 22, 2016, 1:22:06 PM, you wrote: > Juergen Gross writes ("Xenstore watch interface in the kernel"): >> While working on the Linux xenbus kernel driver I stumbled over a rather >> strange interface: a Xenstore watch event is delivered via a callback >> defined as: >> >> void

Re: [Xen-devel] [PATCH] Fix errornous negation for isstubdom, which breaks HVM pci-passthrough.

On 12/12/16 10:14, Wei Liu wrote: > On Sat, Dec 10, 2016 at 06:59:08PM +0100, Sander Eikelenboom wrote: >> Commit 20b75251d9721d9c050a973c02baac396c794ade introduced an errornous >> negation which gave the isstubdom bool the opposite semantics, >> causing the subsequent code t

[Xen-devel] [PATCH] Fix errornous negation for isstubdom, which breaks HVM pci-passthrough.

Commit 20b75251d9721d9c050a973c02baac396c794ade introduced an errornous negation which gave the isstubdom bool the opposite semantics, causing the subsequent code to take the wrong code path. Signed-off-by: Sander Eikelenboom <li...@eikelenboom.it> --- tools/libxl/libxl_pci.c | 2 +-

Re: [Xen-devel] Kernel panic on Xen virtualisation in Debian

Thursday, December 1, 2016, 2:59:36 PM, you wrote: > On 01.12.2016 14:26, Wei Liu wrote: >> This is still the same kernel log that was sent some time ago. >> So, if you have built Xen with debug=y, could you try to set Xen log >> level to the highest and capture "xl dmesg" when guest crashes?

Re: [Xen-devel] xenbits.xen.org gitweb summaries advertise https version, but that url leads to a blank page.

On 23/11/16 21:26, Julien Grall wrote: On 23/11/16 20:10, Sander Eikelenboom wrote: Hi Sander, The summaries [1] on the xenbits.xen.org gitweb advertise that it should be reachable with http, git and https urls, however the https url [2] leads to a blank page. Is that expected (I can

[Xen-devel] xenbits.xen.org gitweb summaries advertise https version, but that url leads to a blank page.

Hi Lars, The summaries [1] on the xenbits.xen.org gitweb advertise that it should be reachable with http, git and https urls, however the https url [2] leads to a blank page. Is that expected (I can imagine it was switched off to lower serverload, however I wouldn't expect it to be advertised

Re: [Xen-devel] [PULL 0/1] tags/xen-20161108-tag

Tuesday, November 8, 2016, 8:59:46 PM, you wrote: > The following changes since commit 207faf24c58859f5240f66bf6decc33b87a1776e: > Merge remote-tracking branch 'pm215/tags/pull-target-arm-20161107' into > staging (2016-11-07 14:02:15 +) > are available in the git repository at: >

Re: [Xen-devel] [PATCH v2] PCMachineState: introduce acpi_build_enabled field

ony.per...@citrix.com> Cc: Stefano Stabellini <sstabell...@kernel.org> Cc: Sander Eikelenboom <li...@eikelenboom.it> v2: 1. drop acpi-build property 2. set acpi_build_enabled to acpi_has_build 3. replace acpi_has_build check in acpi_build() --- hw/i386/acpi-build.c | 2 +- hw/i386/

Re: [Xen-devel] [PATCH v2] xenfv: set has_acpi_build to false

ot > anymore, because the new ACPI tables cause the guest to exceed its > memory allocation limit. > Reported-by: Sander Eikelenboom <li...@eikelenboom.it> > Signed-off-by: Wei Liu <wei.l...@citrix.com> Just given this patch a spin and you may add a: Tested-by: Sander Eikele

Re: [Xen-devel] Regression between Xen 4.6.0 and 4.7.0, Direct kernel boot on a qemu-xen and seabios HVM guest doesn't work anymore.

On 2016-10-25 16:49, Wei Liu wrote: On Tue, Oct 25, 2016 at 01:37:45PM +0200, Sander Eikelenboom wrote: Tuesday, October 25, 2016, 1:24:12 PM, you wrote: > On Tue, Oct 18, 2016 at 01:48:23PM +0100, Wei Liu wrote: >> On Mon, Oct 17, 2016 at 05:28:17PM +0200, Sander Eikelenb

Re: [Xen-devel] Regression between Xen 4.6.0 and 4.7.0, Direct kernel boot on a qemu-xen and seabios HVM guest doesn't work anymore.

Tuesday, October 25, 2016, 1:24:12 PM, you wrote: > On Tue, Oct 18, 2016 at 01:48:23PM +0100, Wei Liu wrote: >> On Mon, Oct 17, 2016 at 05:28:17PM +0200, Sander Eikelenboom wrote: >> > Thursday, October 13, 2016, 4:43:31 PM, you wrote: >> > >> > > Hi Jan

Re: [Xen-devel] Regression between Xen 4.6.0 and 4.7.0, Direct kernel boot on a qemu-xen and seabios HVM guest doesn't work anymore.

Thursday, October 13, 2016, 4:43:31 PM, you wrote: > Hi Jan / Wei, > Took a while before i had the chance to fiddle some more to find the actual > culprit. > After analyzing the output of xl -v create somewhat more i came to the > insight it was probably Qemu and not Xen causing the fault.

Re: [Xen-devel] Regression between Xen 4.6.0 and 4.7.0, Direct kernel boot on a qemu-xen and seabios HVM guest doesn't work anymore.

Hi Jan / Wei, Took a while before i had the chance to fiddle some more to find the actual culprit. After analyzing the output of xl -v create somewhat more i came to the insight it was probably Qemu and not Xen causing the fault. As a test I just used a qemu-xen binary build with xen-4.6.0

Re: [Xen-devel] [PATCH] xen/x86: Initialize per_cpu(xen_vcpu, 0) a little earlier

ported-by: Sander Eikelenboom <li...@eikelenboom.it> --- Sander, please see if this fixes the problem. Thanks. Hi Boris, I have tested it and it fixes the dom0 crash in early boot for me. Thanks again for investigating and the swift fix ! -- Sander arch/x86/xen/enlighten.c | 3 ++- 1

Re: [Xen-devel] Linux 4.8-rc8 with Xen for-linus-4.9 branch: dom0 crashes on boot

On 2016-10-02 18:53, Boris Ostrovsky wrote: On 10/02/2016 08:50 AM, Sander Eikelenboom wrote: Sure thing: addr2line -e vmlinux-4.8.0-rc8-20161002-linus-xennext+ 8101fdb9 /usr/src/new/linux-linus/arch/x86/xen/irq.c:34 asmlinkage __visible unsigned long xen_save_fl(void

Re: [Xen-devel] Linux 4.8-rc8 with Xen for-linus-4.9 branch: dom0 crashes on boot

On 2016-10-02 14:08, Andrew Cooper wrote: On 02/10/2016 12:46, Sander Eikelenboom wrote: Hi All, Since the new merge window is emerging I took the liberty of testing a linux 4.8-rc8 tree with the Xen for-linus-4.9 branch pulled on top. Unfortunately this crashes dom0 early in boot under Xen

[Xen-devel] Linux 4.8-rc8 with Xen for-linus-4.9 branch: dom0 crashes on boot

Hi All, Since the new merge window is emerging I took the liberty of testing a linux 4.8-rc8 tree with the Xen for-linus-4.9 branch pulled on top. Unfortunately this crashes dom0 early in boot under Xen. On bare-metal the same kernel boots fine. Under Xen a linux 4.8-rc8 kernel without the Xen

Re: [Xen-devel] BUG_ON() vs ASSERT()

Wednesday, September 14, 2016, 10:35:30 AM, you wrote: > On Tue, Sep 13, 2016 at 7:16 PM, Andrew Cooper > wrote: >> On 12/09/16 16:23, Jan Beulich wrote: >>> All, >>> >>> in >>> https://lists.xenproject.org/archives/html/xen-devel/2016-09/msg01201.html >>> and >>>

Re: [Xen-devel] [Linux 4.8-rc1 Bisected] Clock on boot Xen HVM guest starts at 31/12/1999

Friday, August 12, 2016, 7:29:37 PM, you wrote: > Hi, > On 12/08/2016 at 19:23:36 +0200, Sander Eikelenboom wrote : >> L.S., >> >> I'm seeing an issue when using a Linux 4.8-rc1 kernel in a Xen HVM guest (PV >> guests and dom0 are uneffected). The clock is always

[Xen-devel] [Linux 4.8-rc1 Bisected] Clock on boot Xen HVM guest starts at 31/12/1999

L.S., I'm seeing an issue when using a Linux 4.8-rc1 kernel in a Xen HVM guest (PV guests and dom0 are uneffected). The clock is always set to 31/12/1999 on boot of the guest, instead of the system clock time. Bisecting seems to point out commit: 463a86304cae92e10277b47180ac59cf93982e5b

Re: [Xen-devel] [DRAFT v3] XenSock protocol design document

Thursday, July 28, 2016, 8:11:53 PM, you wrote: > ping Hi Stefano, JFYI: Since this doesn't seem to be checked with the upstream kernel yet, I don't know if you are aware of the opinions expressed upstream about the proposed Hyper-V socket patches:

Re: [Xen-devel] Kernel panic on Xen virtualisation in Debian

Monday, July 25, 2016, 1:27:20 PM, you wrote: > On 25.07.2016 12:51, Wei Liu wrote: >>> [...] >>> > Your report and the debian report suggested that Dom0 kernel is less >>> > likely to be the culprit because you've tried different Dom0 kernels. >>> yes we did. but nothing newer than 3.16 so

Re: [Xen-devel] [PATCH] x86/vMSI-X: Fix host crash when shutting down guests with MSI capable devices

Monday, July 25, 2016, 12:19:55 PM, you wrote: > On 25/07/16 11:16, Andrew Cooper wrote: >> On 22/07/16 09:50, Sander Eikelenboom wrote: >>> Thursday, July 21, 2016, 12:18:37 PM, you wrote: >>> >>>> c/s 74c6dc2d "x86/vMSI-X: defer intercept handler

Re: [Xen-devel] [PATCH] x86/vMSI-X: Fix host crash when shutting down guests with MSI capable devices

sed check to msixtbl_pt_unregister(). > Furthermore, the purpose of the open-coded msixtbl_list.next check is rather > subtle. Introduce an msixtbl_initialised() predicate instead, which makes its > purpose far more obvious. > Reported-by: Sander Eikelenboom <li...@eikelenboom.it> >

Re: [Xen-devel] [PATCH] x86/vMSI-X: Fix host crash when shutting down guests with MSI capable devices

hich is still NULL. > >Introduce an is-initalised check to msixtbl_pt_unregister(). > >Furthermore, the purpose of the open-coded msixtbl_list.next check is >rather >subtle. Introduce an msixtbl_initialised() predicate instead, which >makes its >purpose far more obvious. &

Re: [Xen-devel] Xen-unstable 4.8: Host crash when shutting down guest with pci device passed through using MSI-X interrupts.

Monday, July 18, 2016, 7:48:20 PM, you wrote: > On 18/07/16 11:21, li...@eikelenboom.it wrote: >> Hi Jan, >> >> It seems that since your patch series starting with commit: >> 2016-06-22 x86/vMSI-X: defer intercept handler registration >> 74c6dc2d0ac4dcab0c6243cdf6ed550c1532b798 >> >> The

Re: [Xen-devel] Xen-unstable 4.8: HVM domain_crash called from emulate.c:144 RIP: c000:[<000000000000336a>]

Wednesday, June 15, 2016, 2:48:55 PM, you wrote: On 15.06.16 at 14:00, wrote: >> Wednesday, June 15, 2016, 12:12:37 PM, you wrote: >> On 15.06.16 at 11:38, wrote: Wednesday, June 15, 2016, 10:57:03 AM, you wrote: > Wednesday, June

Re: [Xen-devel] Xen-unstable 4.8: HVM domain_crash called from emulate.c:144 RIP: c000:[<000000000000336a>]

Wednesday, June 15, 2016, 12:12:37 PM, you wrote: On 15.06.16 at 11:38, wrote: >> Wednesday, June 15, 2016, 10:57:03 AM, you wrote: >> >>> Wednesday, June 15, 2016, 10:29:37 AM, you wrote: >> >>> On 15.06.16 at 01:49, wrote: > Just

Re: [Xen-devel] Xen-unstable 4.8: HVM domain_crash called from emulate.c:144 RIP: c000:[<000000000000336a>]

Wednesday, June 15, 2016, 10:57:03 AM, you wrote: > Wednesday, June 15, 2016, 10:29:37 AM, you wrote: > On 15.06.16 at 01:49, wrote: >>> Just tested latest xen-unstable 4.8 (xen_changeset git:d337764), >>> but one of the latest commits seems to have broken boot of HVM

Re: [Xen-devel] Xen-unstable 4.8: HVM domain_crash called from emulate.c:144 RIP: c000:[<000000000000336a>]

Wednesday, June 15, 2016, 10:29:37 AM, you wrote: On 15.06.16 at 01:49, wrote: >> Just tested latest xen-unstable 4.8 (xen_changeset git:d337764), >> but one of the latest commits seems to have broken boot of HVM guests >> (using qemu-xen) previous build with

Re: [Xen-devel] [Question] PARSEC benchmark has smaller execution time in VM than in native?

Tuesday, March 1, 2016, 9:39:25 PM, you wrote: > On Tue, Mar 01, 2016 at 02:52:14PM -0500, Meng Xu wrote: >> Hi Elena, >> >> Thank you very much for sharing this! :-) >> >> On Tue, Mar 1, 2016 at 1:20 PM, Elena Ufimtseva >> wrote: >> > >> > On Tue, Mar 01, 2016 at

Re: [Xen-devel] Xen-devel Digest, Vol 130, Issue 521

On 2015-12-21 23:58, xen-devel-requ...@lists.xen.org wrote: Send Xen-devel mailing list submissions to xen-devel@lists.xen.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel or, via email, send a message with

Re: [Xen-devel] linux 4.4 Regression: 100% cpu usage on idle pv guest under Xen with single vcpu

picked up yet, but hopefully will be anytime soon (for the patch see http://lkml.iu.edu/hypermail/linux/kernel/1512.1/03504.html) -- Sander On 2015-12-02 18:30, Sander Eikelenboom wrote: On 2015-12-02 15:55, David Vrabel wrote: > On 28/11/15 15:47, Sander Eikelenboom wrote: >> geni

Re: [Xen-devel] [PATCH] x86: Xen PV guests don't have the rtc_cmos platform device

On 2015-12-09 15:42, Jan Beulich wrote: On 09.12.15 at 15:32, wrote: --- a/arch/x86/kernel/rtc.c +++ b/arch/x86/kernel/rtc.c @@ -200,6 +200,9 @@ static __init int add_rtc_cmos(void) } #endif + if (paravirt_enabled()) + return -ENODEV;

[Xen-devel] [PATCH] Fix regression in xendomains initscript: test for privcmd char device

Since commit: "xendomains initscript: test for privcmd char device" (1367e9e5ba4d1612e303123ec0bbf961100fcfa1) due to incorrect negation the xendomains initscript bails out early when both: "/dev/xen/privcmd" and "/proc/xen/privcmd" are present in dom0. Signed-

Re: [Xen-devel] Patch "x86/irq: Probe for PIC presence before allocating descs for legacy IRQs" has been added to the 4.3-stable tree

Monday, December 7, 2015, 1:54:35 PM, you wrote: > writes: >> This is a note to let you know that I've just added the patch titled >> >> x86/irq: Probe for PIC presence before allocating descs for legacy IRQs >> >> to the 4.3-stable tree which can be found at:

Re: [Xen-devel] linux 4.4 Regression: 100% cpu usage on idle pv guest under Xen with single vcpu.

On 2015-12-02 15:55, David Vrabel wrote: On 28/11/15 15:47, Sander Eikelenboom wrote: genirq: Flags mismatch irq 8. (hvc_console) vs. (rtc0) We shouldn't register an rtc_cmos device because its legacy irq conflicts with the irq needed for hvc0. For a multi VCPU guest irq 8

Re: [Xen-devel] linux 4.4 Regression: 100% cpu usage on idle pv guest under Xen with single vcpu.

On 2015-12-02 00:41, Boris Ostrovsky wrote: On 12/01/2015 06:30 PM, Sander Eikelenboom wrote: On 2015-12-02 00:19, Boris Ostrovsky wrote: On 12/01/2015 06:00 PM, Sander Eikelenboom wrote: On 2015-12-01 23:47, Boris Ostrovsky wrote: On 11/30/2015 05:55 PM, Sander Eikelenboom wrote: On 2015

Re: [Xen-devel] linux 4.4 Regression: 100% cpu usage on idle pv guest under Xen with single vcpu.

On 2015-12-01 23:47, Boris Ostrovsky wrote: On 11/30/2015 05:55 PM, Sander Eikelenboom wrote: On 2015-11-30 23:54, Boris Ostrovsky wrote: On 11/30/2015 04:46 PM, Sander Eikelenboom wrote: On 2015-11-30 22:45, Konrad Rzeszutek Wilk wrote: On Sat, Nov 28, 2015 at 04:47:43PM +0100, Sander

Re: [Xen-devel] linux 4.4 Regression: 100% cpu usage on idle pv guest under Xen with single vcpu.

On 2015-11-30 23:54, Boris Ostrovsky wrote: On 11/30/2015 04:46 PM, Sander Eikelenboom wrote: On 2015-11-30 22:45, Konrad Rzeszutek Wilk wrote: On Sat, Nov 28, 2015 at 04:47:43PM +0100, Sander Eikelenboom wrote: Hi all, I have just tested a 4.4-rc2 kernel (current linus tree) + the tip tree

Re: [Xen-devel] linux 4.4 Regression: 100% cpu usage on idle pv guest under Xen with single vcpu.

On 2015-12-02 00:19, Boris Ostrovsky wrote: On 12/01/2015 06:00 PM, Sander Eikelenboom wrote: On 2015-12-01 23:47, Boris Ostrovsky wrote: On 11/30/2015 05:55 PM, Sander Eikelenboom wrote: On 2015-11-30 23:54, Boris Ostrovsky wrote: On 11/30/2015 04:46 PM, Sander Eikelenboom wrote: On 2015

Re: [Xen-devel] linux 4.4 Regression: 100% cpu usage on idle pv guest under Xen with single vcpu.

On 2015-12-02 00:41, Boris Ostrovsky wrote: On 12/01/2015 06:30 PM, Sander Eikelenboom wrote: On 2015-12-02 00:19, Boris Ostrovsky wrote: On 12/01/2015 06:00 PM, Sander Eikelenboom wrote: On 2015-12-01 23:47, Boris Ostrovsky wrote: On 11/30/2015 05:55 PM, Sander Eikelenboom wrote: On 2015

Re: [Xen-devel] linux 4.4 Regression: 100% cpu usage on idle pv guest under Xen with single vcpu.

On 2015-11-30 23:54, Boris Ostrovsky wrote: On 11/30/2015 04:46 PM, Sander Eikelenboom wrote: On 2015-11-30 22:45, Konrad Rzeszutek Wilk wrote: On Sat, Nov 28, 2015 at 04:47:43PM +0100, Sander Eikelenboom wrote: Hi all, I have just tested a 4.4-rc2 kernel (current linus tree) + the tip tree

Re: [Xen-devel] Linux 4.4 MW: Boot under Xen fails with CONFIG_DEBUG_WX enabled: RIP: ptdump_walk_pgd_level_core

On 2015-11-05 00:13, Boris Ostrovsky wrote: On 11/04/2015 03:02 PM, Sander Eikelenboom wrote: On 2015-11-04 19:47, Stephen Smalley wrote: On 11/04/2015 01:28 PM, Sander Eikelenboom wrote: On 2015-11-04 16:52, Stephen Smalley wrote: On 11/04/2015 06:55 AM, Sander Eikelenboom wrote: Hi All

Re: [Xen-devel] Linux 4.4 MW: Boot under Xen fails with CONFIG_DEBUG_WX enabled: RIP: ptdump_walk_pgd_level_core

Thursday, November 5, 2015, 2:53:40 PM, you wrote: > On 11/05/2015 04:13 AM, Sander Eikelenboom wrote: >> >> It makes "cat /sys/kernel/debug/kernel_page_tables" work and >> prevents a kernel with CONFIG_DEBUG_WX=y from crashing at boot. > Great. Our nightly

Re: [Xen-devel] Linux 4.4 MW: Boot under Xen fails with CONFIG_DEBUG_WX enabled: RIP: ptdump_walk_pgd_level_core

On 2015-11-04 19:47, Stephen Smalley wrote: On 11/04/2015 01:28 PM, Sander Eikelenboom wrote: On 2015-11-04 16:52, Stephen Smalley wrote: On 11/04/2015 06:55 AM, Sander Eikelenboom wrote: Hi All, I just tried to boot with the current linus mergewindow tree under Xen. It fails with a kernel

[Xen-devel] Linux 4.4 MW: Boot under Xen fails with CONFIG_DEBUG_WX enabled: RIP: ptdump_walk_pgd_level_core

Hi All, I just tried to boot with the current linus mergewindow tree under Xen. It fails with a kernel panic at boot with the new "CONFIG_DEBUG_WX" option enabled. Disabling it makes the kernel boot fine. The splat: [ 18.424241] Freeing unused kernel memory: 1104K (822fc000 -

Re: [Xen-devel] Linux 4.4 MW: Boot under Xen fails with CONFIG_DEBUG_WX enabled: RIP: ptdump_walk_pgd_level_core

On 2015-11-04 19:06, Ingo Molnar wrote: * Stephen Smalley <s...@tycho.nsa.gov> wrote: On 11/04/2015 06:55 AM, Sander Eikelenboom wrote: >Hi All, > >I just tried to boot with the current linus mergewindow tree under Xen. >It fails with a kernel panic at boot with the ne

Re: [Xen-devel] Linux 4.4 MW: Boot under Xen fails with CONFIG_DEBUG_WX enabled: RIP: ptdump_walk_pgd_level_core

On 2015-11-04 16:52, Stephen Smalley wrote: On 11/04/2015 06:55 AM, Sander Eikelenboom wrote: Hi All, I just tried to boot with the current linus mergewindow tree under Xen. It fails with a kernel panic at boot with the new "CONFIG_DEBUG_WX" option enabled. Disabling it makes the k

Re: [Xen-devel] [PATCH] Add Libc multiarch package as build prerequisites on 64-bit platforms to the README

On 2015-10-07 13:52, Ian Campbell wrote: On Tue, 2015-10-06 at 18:58 +0200, Sander Eikelenboom wrote: When building on 64-bit platforms this prevents build errors for 32-bit components which are enabled on a default build. Signed-off-by: Sander Eikelenboom <li...@eikelenboom.it>

Re: [Xen-devel] [xen 4.6.0 to be] Readme missing 32bit as dependency for a default build on Debian Jessie

On 2015-10-06 13:52, Konrad Rzeszutek Wilk wrote: On October 6, 2015 7:26:35 AM EDT, Wei Liu <wei.l...@citrix.com> wrote: On Tue, Oct 06, 2015 at 01:19:17PM +0200, Sander Eikelenboom wrote: Hi, Today i tried building installing a fresh clone of Xen 4.6.0 (to be) on a minimal Debian

[Xen-devel] [xen 4.6.0 to be] Readme missing 32bit as dependency for a default build on Debian Jessie

Hi, Today i tried building installing a fresh clone of Xen 4.6.0 (to be) on a minimal Debian Jessie install. The package list in the README seems to be missing "libc6-dev-i386" which seems to be needed for a default build (.configure && make && make install) which also builds 32-bit pieces.

[Xen-devel] [PATCH] Add Libc multiarch package as build prerequisites on 64-bit platforms to the README

When building on 64-bit platforms this prevents build errors for 32-bit components which are enabled on a default build. Signed-off-by: Sander Eikelenboom <li...@eikelenboom.it> --- README | 3 +++ 1 file changed, 3 insertions(+) diff --git a/README b/README index a7d0033..1324c7c

Re: [Xen-devel] Xen-unstable: Keyboard doesn't seem to work when using VNC to HVM with qemu-xen device model.

Monday, September 7, 2015, 3:21:45 PM, you wrote: > On Sun, Sep 06, 2015 at 12:46:01PM +0200, Sander Eikelenboom wrote: >> Hi All, >> >> Today i noticed that keyboard doesn't work when using VNC on a HVM guest >> which runs under qemu-xen device-model. >>

[Xen-devel] Xen-unstable: Keyboard doesn't seem to work when using VNC to HVM with qemu-xen device model.

Hi All, Today i noticed that keyboard doesn't work when using VNC on a HVM guest which runs under qemu-xen device-model. Mouse still works with usbdevice='tablet', but keypress show no response what so ever. Unfortunately i'm on a tight time budget the next few weeks, so i just switched to

Re: [Xen-devel] Linux 4.2-rc6 regression: RIP: e030:[ffffffff8110fb18] [ffffffff8110fb18] detach_if_pending+0x18/0x80

Saturday, August 15, 2015, 12:39:25 AM, you wrote: On Sat, 2015-08-15 at 00:09 +0200, Sander Eikelenboom wrote: On 2015-08-13 00:41, Eric Dumazet wrote: On Wed, 2015-08-12 at 23:46 +0200, Sander Eikelenboom wrote: Thanks for the reminder, but luckily i was aware of that, seen enough

Re: [Xen-devel] Linux 4.2-rc6 regression: RIP: e030:[ffffffff8110fb18] [ffffffff8110fb18] detach_if_pending+0x18/0x80

Monday, August 17, 2015, 3:37:13 PM, you wrote: On Mon, 2015-08-17 at 11:09 +0200, Sander Eikelenboom wrote: Saturday, August 15, 2015, 12:39:25 AM, you wrote: On Sat, 2015-08-15 at 00:09 +0200, Sander Eikelenboom wrote: On 2015-08-13 00:41, Eric Dumazet wrote: On Wed, 2015-08-12

Re: [Xen-devel] Linux 4.2-rc6 regression: RIP: e030:[ffffffff8110fb18] [ffffffff8110fb18] detach_if_pending+0x18/0x80

Monday, August 17, 2015, 4:21:47 PM, you wrote: On Mon, 2015-08-17 at 09:02 -0500, Jon Christopherson wrote: This is very similar to the behavior I am seeing in this bug: https://bugzilla.kernel.org/show_bug.cgi?id=102911 OK, but have you applied the fix ?

Re: [Xen-devel] Linux 4.2-rc6 regression: RIP: e030:[ffffffff8110fb18] [ffffffff8110fb18] detach_if_pending+0x18/0x80

On 2015-08-17 19:18, Eric Dumazet wrote: From: Eric Dumazet eduma...@google.com On Mon, 2015-08-17 at 16:25 +0200, Sander Eikelenboom wrote: Monday, August 17, 2015, 4:21:47 PM, you wrote: On Mon, 2015-08-17 at 09:02 -0500, Jon Christopherson wrote: This is very similar to the behavior I am

Re: [Xen-devel] Xen-unstable Linux 4.2-rc6: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 51s! xen_hypercall_xen_version+0xa/0x20

Friday, August 14, 2015, 8:11:10 PM, you wrote: Hi, At the moment i'm encounterig this new splat in a PV guest, both dom0 and domU running a kernel 4.2-rc6 (last commit 7ddab73346a1277b90fd6a4d044bc948f9cc9ad8) and xen-unstable (last commit git:201eac8-dirty) -- Sander Edit: it was

[Xen-devel] Xen-unstable Linux 4.2-rc5: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 51s! xen_hypercall_xen_version+0xa/0x20

Hi, At the moment i'm encounterig this new splat in a PV guest, both dom0 and domU running a kernel 4.2-rc5 (last commit 7ddab73346a1277b90fd6a4d044bc948f9cc9ad8) and xen-unstable (last commit git:201eac8-dirty) -- Sander NMI watchdog: BUG: soft lockup - CPU#0 stuck for 51s! [swapper/0:0]

Re: [Xen-devel] Linux 4.2-rc6 regression: RIP: e030:[ffffffff8110fb18] [ffffffff8110fb18] detach_if_pending+0x18/0x80

On 2015-08-13 00:41, Eric Dumazet wrote: On Wed, 2015-08-12 at 23:46 +0200, Sander Eikelenboom wrote: Thanks for the reminder, but luckily i was aware of that, seen enough of your replies asking for patches to be resubmitted against the other tree ;) Kernel with patch is currently running so

Re: [Xen-devel] Linux 4.2-rc6 regression: RIP: e030:[ffffffff8110fb18] [ffffffff8110fb18] detach_if_pending+0x18/0x80

On 2015-08-15 00:09, Sander Eikelenboom wrote: On 2015-08-13 00:41, Eric Dumazet wrote: On Wed, 2015-08-12 at 23:46 +0200, Sander Eikelenboom wrote: Thanks for the reminder, but luckily i was aware of that, seen enough of your replies asking for patches to be resubmitted against the other

Re: [Xen-devel] Linux 4.2-rc5:

Monday, August 10, 2015, 11:00:11 AM, you wrote: On 08/06/2015 08:51 PM, li...@eikelenboom.it wrote: Hi Ross, On my dom0 with a linux 4.2-rc5 kernel i encoutered the splat below. It's probably related to your patch that went in just for 4.2-rc5: xen/events/fifo: Handle linked events when

Re: [Xen-devel] [BUG] Emulation issues

Friday, July 31, 2015, 12:22:16 PM, you wrote: -Original Message- From: xen-devel-boun...@lists.xen.org [mailto:xen-devel- boun...@lists.xen.org] On Behalf Of Paul Durrant Sent: 30 July 2015 14:20 To: Andrew Cooper; Roger Pau Monne; xen-devel Subject: Re: [Xen-devel] [BUG]

Re: [Xen-devel] xen-unstabel + linux 4.2: MMIO emulation failed: d23v0 64bit @ 0010:ffffffff814e2b1c - 66 89 02 48 8d 55 c0 48 89 5d c0 44 89 65 c8 e8

Wednesday, July 29, 2015, 11:06:37 AM, you wrote: -Original Message- From: li...@eikelenboom.it [mailto:li...@eikelenboom.it] Sent: 28 July 2015 22:16 To: Andrew Cooper Cc: xen-devel@lists.xen.org; Paul Durrant Subject: Re: [Xen-devel] xen-unstabel + linux 4.2: MMIO emulation

Re: [Xen-devel] xen-unstabel + linux 4.2: MMIO emulation failed: d23v0 64bit @ 0010:ffffffff814e2b1c - 66 89 02 48 8d 55 c0 48 89 5d c0 44 89 65 c8 e8

Monday, July 27, 2015, 4:07:39 PM, you wrote: On 24/07/15 19:56, li...@eikelenboom.it wrote: Hi All, On my AMD system running xen-unstable (last commit: ), after a few restarts of a HVM guest with pci-passthrough i got these on shutdown of the guest: (never seen this before, so it should

Re: [Xen-devel] traps.c:3227: GPF (0000): ffff82d080194a4d - ffff82d080239d85 and other dom0 induced log messages

Monday, July 6, 2015, 11:33:09 AM, you wrote: On 26.06.15 at 17:57, li...@eikelenboom.it wrote: On 2015-06-26 17:51, Jan Beulich wrote: On 26.06.15 at 17:41, li...@eikelenboom.it wrote: from 3.16 to 3.19 we gained a lot of these, if i remember correctly related to perf being enabled in the

Re: [Xen-devel] Xen-unstable: pci-passthrough of device using MSI-X interrupts not working after commit x86/MSI: track host and guest masking separately

Tuesday, July 7, 2015, 6:08:25 PM, you wrote: On 26.06.15 at 17:48, li...@eikelenboom.it wrote: On 2015-06-26 17:22, Jan Beulich wrote: I have an idea: In static unsigned int startup_msi_irq(struct irq_desc *desc) { bool_t guest_masked = (desc-status IRQ_GUEST)

Re: [Xen-devel] traps.c:3227: GPF (0000): ffff82d080194a4d - ffff82d080239d85 and other dom0 induced log messages

Wednesday, July 8, 2015, 10:58:02 AM, you wrote: On 08/07/2015 09:45, Sander Eikelenboom wrote: Monday, July 6, 2015, 11:33:09 AM, you wrote: On 26.06.15 at 17:57, li...@eikelenboom.it wrote: On 2015-06-26 17:51, Jan Beulich wrote: On 26.06.15 at 17:41, li...@eikelenboom.it wrote: from

Re: [Xen-devel] Xen-unstable: pci-passthrough of device using MSI-X interrupts not working after commit x86/MSI: track host and guest masking separately

Thursday, June 25, 2015, 10:48:40 AM, you wrote: On 24.06.15 at 21:38, li...@eikelenboom.it wrote: I'm having some trouble with a xhci controller passed through with pci-passthrough to one of my HVM guests. It uses MSI-X for interrupts, a bisection turned up the following commit:

  1   2   3   >