Re: [Xen-devel] [v2][PATCH] xen/vtd/iommu: permit group devices to passthrough in relaxed mode

Den 10. sep. 2015 08:06, skrev Tian, Kevin: >> From: Chen, Tiejun >> Sent: Thursday, September 10, 2015 1:47 PM >> >> But recently someone was encountering this problem. >> >> http://www.gossamer-threads.com/lists/xen/devel/391684?page=last >> >> We'd better figure out a simple way to this

Re: [Xen-devel] [v2][PATCH] xen/vtd/iommu: permit group devices to passthrough in relaxed mode

Den 10. sep. 2015 13:04, skrev Håkon Alstadheim: > Den 10. sep. 2015 08:06, skrev Tian, Kevin: >>> From: Chen, Tiejun >>> Sent: Thursday, September 10, 2015 1:47 PM >>> >>> But recently someone was encountering this problem. >>> >>> http://

[Xen-devel] Xen makefiles wants to write to /..d ?

I confess I'm a rank amateur, but I'm trying to get xen-4.7.0_rc* rammed into a gentoo package, so that I can try it out and still switch back to 4.6 again as quickly as possible. I don't have it working yet, but aside from that, gentoo build sandbox complains about several instances like this:

Re: [Xen-devel] [BUG] Assertion '(sp == 0) || (peoi[sp-1].vector < vector)' failed at irq.c:1163

On 01/15/2016 12:05 PM, Andrew Cooper wrote: On 15/01/16 10:58, Håkon Alstadheim wrote: This is just a preliminary report, mostly just for the record. I will report again if this keeps happening after 4.7 is out, or upon request. Anyone working on this, please mail me and request more

Re: [Xen-devel] [BUG] Assertion '(sp == 0) || (peoi[sp-1].vector < vector)' failed at irq.c:1163

On 01/15/2016 01:42 PM, Jan Beulich wrote: On 15.01.16 at 13:32, wrote: placed microcode.bin in /boot/microcode.bin booted with : --- xen_commandline: ssd-xen-debug-marker console_timestamps=date loglvl=all guest_loglvl=all sync_console

[Xen-devel] [BUG] Assertion '(sp == 0) || (peoi[sp-1].vector < vector)' failed at irq.c:1163

This is just a preliminary report, mostly just for the record. I will report again if this keeps happening after 4.7 is out, or upon request. Anyone working on this, please mail me and request more information. I have available logs from dom0 boot (I dump dmesg and xl dmesg to disk after

Re: [Xen-devel] [BUG] Assertion '(sp == 0) || (peoi[sp-1].vector < vector)' failed at irq.c:1163

On 01/15/2016 02:09 PM, Ian Campbell wrote: On Fri, 2016-01-15 at 13:49 +0100, Håkon Alstadheim wrote: On 01/15/2016 01:42 PM, Jan Beulich wrote: On 15.01.16 at 13:32, <ha...@alstadheim.priv.no> wrote: placed microcode.bin in /boot/microcode.bin booted with : --- xen_comma

Re: [Xen-devel] [BUG] Assertion '(sp == 0) || (peoi[sp-1].vector < vector)' failed at irq.c:1163

On 01/15/2016 01:49 PM, Håkon Alstadheim wrote: On 01/15/2016 01:42 PM, Jan Beulich wrote: On 15.01.16 at 13:32, <ha...@alstadheim.priv.no> wrote: placed microcode.bin in /boot/microcode.bin booted with : --- xen_commandline: ssd-xen-debug-marker console_timestamps=date

Re: [Xen-devel] [BUG] Assertion '(sp == 0) || (peoi[sp-1].vector < vector)' failed at irq.c:1163

Den 18. jan. 2016 11:31, skrev Jan Beulich: On 18.01.16 at 00:07, wrote: >> There we go :-/ . Log attached from boot to assertion-failure with >> loglvl=all guest_loglvl=all . Some of the log output might be a bit >> cryptic, they are notes to myself from local

Re: [Xen-devel] [BUG] Assertion '(sp == 0) || (peoi[sp-1].vector < vector)' failed at irq.c:1163

Den 17. jan. 2016 16:16, skrev Andrew Cooper: > On 17/01/16 14:50, Håkon Alstadheim wrote: >> Den 15. jan. 2016 12:05, skrev Andrew Cooper: >>> On 15/01/16 10:58, Håkon Alstadheim wrote: >>>> CPUINFO: >>>> vendor_id: GenuineIntel >>>> cp

[Xen-devel] [BUG] Xen BUG at irq.c:1705 after [VT-D]d1:PCIe: unmap

This has happened in 2 out of four recent shutdowns of a specific domU "garbo.hvm", domid=1. --- domU specs (no tmem in cmdline arg to domU): - Linux garbo 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u4 (2016-02-29) x86_64 garbo:~# cat /proc/cmdline

[Xen-devel] kernel BUG at block/bio.c:1786 -- (xen_blkif_schedule on the stack)

I get the BUG below in dom0 when trying to start a windows 10 domu (hvm, with some pv-drivers installed ) . Below is "xl info", then comes dmesg output, and finally domu config attached at end. This domain is started very rarely, so may have been broken for some time. All my other domains ar

Re: [Xen-devel] kernel BUG at block/bio.c:1786 -- (xen_blkif_schedule on the stack)

Den 2017-02-09 18:30, skrev Roger Pau Monné: On Mon, Feb 06, 2017 at 12:31:20AM +0100, Håkon Alstadheim wrote: I get the BUG below in dom0 when trying to start a windows 10 domu (hvm, with some pv-drivers installed ) . Below is "xl info", then comes dmesg output, and finally d

Re: [Xen-devel] kernel BUG at block/bio.c:1786 -- (xen_blkif_schedule on the stack)

rants"). Den 09. feb. 2017 18:30, skrev Roger Pau Monné: > On Mon, Feb 06, 2017 at 12:31:20AM +0100, Håkon Alstadheim wrote: >> I get the BUG below in dom0 when trying to start a windows 10 domu (hvm, >> with some pv-drivers installed ) . Below is "xl info", then come

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.

Den 25. aug. 2016 23:18, skrev li...@eikelenboom.it: > On 2016-08-25 22:34, Doug Goldstein wrote: >> On 8/25/16 4:21 PM, li...@eikelenboom.it wrote: >>> Today i tried to switch some of my HVM guests (qemu-xen) from >>> booting of >>> a kernel *inside* the guest, to a dom0 supplied kernel, which is

Re: [Xen-devel] linux-4.7.* under xen-4.6.* gives "unhandled page fault (ec=0000)" at boot. -- Root cause found.

Den 17. aug. 2016 21:56, I wrote (to xen-users, as I am no developer): > I'm on gentoo, running gentoo-sources kernel for dom0. > > I am unable to run gentoo-sources-4.7.{0,1}. I'm running under xen, > currently at 4.6.3-r1 I am now on linux gentoo-sources-4.7.2, and the bug is stil present. I

Re: [Xen-devel] linux-4.7.* under xen-4.6.* gives "unhandled page fault (ec=0000)" at boot. -- Root cause found.

Den 29. aug. 2016 13:04, skrev Jan Beulich: On 29.08.16 at 01:14, wrote: > Den 17. aug. 2016 21:56, I wrote (to xen-users, as I am no developer): >>> I'm on gentoo, running gentoo-sources kernel for dom0. >>> >>> I am unable to run gentoo-sources-4.7.{0,1}. I'm

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.

Den 18. okt. 2016 14:48, skrev Wei Liu: > 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 / Wei, >>> Took a while before i had the chance to fiddle some more to find the actual >>> culprit. >>> After analyzing

Re: [Xen-devel] [BUG] Xen-4.8.0 efi/buildid.o: file not recognized/Ambiguous

Den 08. des. 2016 20:35, skrev John L. Poole: > > > On 12/7/2016 8:51 AM, Jan Beulich wrote: > On 07.12.16 at 16:57, wrote: >>> I did the the following: >>> >>> wget https://downloads.xenproject.org/release/xen/4.8.0/xen-4.8.0.tar.gz >>> tar -xvzf xen-4.8.0.tar.gz

[Xen-devel] [BUG] Segv in radeon drm

Not sure who this should go to, but running linux as domU under Xen triggers this bug. modprobe radeon on a linux domU wich has a "VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM]" -card passed through to it, causes a NULL dereference