On 30/08/2019 09:49, Jan Beulich wrote:
> On 30.08.2019 04:09, Chao Gao wrote:
>> On Fri, Aug 30, 2019 at 01:04:54AM +0200, Sander Eikelenboom wrote:
>>> L.S.,
>>>
>>> While testing xen-unstable, my AMD system crashes during early boot while
>>> load
On 02/09/2019 18:41, Andrew Cooper wrote:
> This logic is all terrible. This series should resolve the reported build
> failure, but definitely isn't a "proper" fix.
>
> Andrew Cooper (2):
> tools/shim: Fix race condition creating linkfarm.stamp
> tools/shim: Apply more duct tape to the linkf
Hi Anthony,
While testing I encountered a problem with my HVM guests which use pci
passthrough.
When trying to shutdown the guest it will stay in the "---s--" runstate
indefinitely.
On the guest console I get:
[ 518.587669] xenbus: xenbus_dev_shutdown: device/pci/0: Initialising !=
Connec
ts earlier, as soon
> as they are not needed anymore.
>
> Reported-by: Sander Eikelenboom
> Fixes: fae4880c45fe015e567afa223f78bf17a6d98e1b
> Signed-off-by: Anthony PERARD
Hi Anthony,
Just tested and it works for me, thanks !
--
Sander
Hi Roger,
I gave PVH dom0 a spin, see how far I would get.
With current xen-unstable unfortunately not that far, i got the splat below.
If you need more info, would like me to test a patch (or some other git
tree/branch),
I will be happy to give it a spin !
--
Sander
__ ___ _
On 18/01/2019 13:50, Roger Pau Monné wrote:
> On Fri, Jan 18, 2019 at 01:03:04PM +0100, Sander Eikelenboom wrote:
>> Hi Roger,
>>
>> I gave PVH dom0 a spin, see how far I would get.
>
> Thanks!
>
>> With current xen-unstable unfortunately not that far, i got
On 18/01/2019 18:56, Roger Pau Monné wrote:
> On Fri, Jan 18, 2019 at 03:17:57PM +0100, Sander Eikelenboom wrote:
>> On 18/01/2019 13:50, Roger Pau Monné wrote:
>>> On Fri, Jan 18, 2019 at 01:03:04PM +0100, Sander Eikelenboom wrote:
>>>> Hi Roger,
>>>>
On 23/01/2019 19:25, Roger Pau Monné wrote:
> On Wed, Jan 23, 2019 at 12:39:21AM +0100, Sander Eikelenboom wrote:
>> On 22/01/2019 17:14, Roger Pau Monné wrote:
>>> On Sun, Jan 20, 2019 at 11:09:25PM +0100, Sander Eikelenboom wrote:
>>>> On 18/01/2019 18:56, Roger
On 24/01/2019 08:50, Roger Pau Monné wrote:
> On Wed, Jan 23, 2019 at 08:56:48PM +0100, Sander Eikelenboom wrote:
>> On 23/01/2019 19:25, Roger Pau Monné wrote:
>>> On Wed, Jan 23, 2019 at 12:39:21AM +0100, Sander Eikelenboom wrote:
>>>> On 22/01/2019 17:14, Roger
On 24/01/2019 11:11, Roger Pau Monné wrote:
> On Thu, Jan 24, 2019 at 10:25:33AM +0100, Sander Eikelenboom wrote:
>> On 24/01/2019 08:50, Roger Pau Monné wrote:
>>> On Wed, Jan 23, 2019 at 08:56:48PM +0100, Sander Eikelenboom wrote:
>>>> On 23/01/2019 19:25, Roger
On 25/01/2019 15:38, Roger Pau Monné wrote:
> On Thu, Jan 24, 2019 at 01:04:31PM +0100, Roger Pau Monné wrote:
>> On Thu, Jan 24, 2019 at 12:55:06PM +0100, Sander Eikelenboom wrote:
>>> On 24/01/2019 11:11, Roger Pau Monné wrote:
>>>> On Thu, Jan 24, 2019 at 10:25:
Hi Andrew,
It seems the pvshim patches in xen-unstable staging break the build on my
machine.
I cloned a fresh tree to be sure, haven't checked which of the two commits
causes it:
060f4eee0fb408b316548775ab921e16b7acd0e0 or
32b1d62887d01f85f0c1d2e0103f69f74e1f6fa3
--
Sander
[ -d //usr/local
On 08/08/2019 23:05, Andrew Cooper wrote:
> On 08/08/2019 21:59, Sander Eikelenboom wrote:
>> Hi Andrew,
>>
>> It seems the pvshim patches in xen-unstable staging break the build on my
>> machine.
>> I cloned a fresh tree to be sure, haven't checked
On 09/08/2019 00:44, Andrew Cooper wrote:
> On 08/08/2019 23:34, Sander Eikelenboom wrote:
>> On 08/08/2019 23:14, Andrew Cooper wrote:
>>> On 08/08/2019 22:16, Sander Eikelenboom wrote:
>>>> On 08/08/2019 23:05, Andrew Cooper wrote:
>>>>> On 08/08/20
On 13/08/2019 13:21, Andrew Cooper wrote:
> On 09/08/2019 00:28, Sander Eikelenboom wrote:
>> On 09/08/2019 00:44, Andrew Cooper wrote:
>>> On 08/08/2019 23:34, Sander Eikelenboom wrote:
>>>> On 08/08/2019 23:14, Andrew Cooper wrote:
>>>>> On 08/08/20
On 13/08/2019 15:31, Andrew Cooper wrote:
> On 13/08/2019 12:51, Sander Eikelenboom wrote:
>> On 13/08/2019 13:21, Andrew Cooper wrote:
>>> On 09/08/2019 00:28, Sander Eikelenboom wrote:
>>>> On 09/08/2019 00:44, Andrew Cooper wrote:
>>>>> On 08/08/20
On 13/08/2019 23:05, Andrew Cooper wrote:
> On 13/08/2019 22:03, Sander Eikelenboom wrote:
>> On 13/08/2019 15:31, Andrew Cooper wrote:
>>> On 13/08/2019 12:51, Sander Eikelenboom wrote:
>>>> On 13/08/2019 13:21, Andrew Cooper wrote:
>>>>> On 09/08/20
On 28/08/2019 15:16, Andrew Cooper wrote:
> On 08/08/2019 21:59, Sander Eikelenboom wrote:
>> Hi Andrew,
>>
>> It seems the pvshim patches in xen-unstable staging break the build on my
>> machine.
>> I cloned a fresh tree to be sure, haven't checked
L.S.,
While testing xen-unstable, my AMD system crashes during early boot while
loading microcode with an "Early fatal page fault".
Reverting commit de45e3ff37bb1602796054afabfa626ea5661c45 "microcode/amd: fix
memory leak" fixes the boot issue.
At present I don't have my serial console stuff at
On 08/02/2019 16:10, Roger Pau Monné wrote:
> On Fri, Jan 25, 2019 at 07:44:40PM +0100, Sander Eikelenboom wrote:
>> On 25/01/2019 15:38, Roger Pau Monné wrote:
>>> On Thu, Jan 24, 2019 at 01:04:31PM +0100, Roger Pau Monné wrote:
>>> Sorry, fixing that error took longer
On 08/02/2019 17:47, Roger Pau Monné wrote:
> On Fri, Feb 08, 2019 at 05:15:22PM +0100, Sander Eikelenboom wrote:
>> On 08/02/2019 16:10, Roger Pau Monné wrote:
>>> On Fri, Jan 25, 2019 at 07:44:40PM +0100, Sander Eikelenboom wrote:
>>>> On 25/01/2019 15:38, Roger
L.S.,
While testing a Linux 5.0-rc5-ish kernel (pull of yesterday) with some
additional patches for
already reported other issues i came across the issue below which i haven't
seen with 4.20.x
I haven't got a reproducer so i might be hard to hit it again,
system is AMD and this is from the ho
On 09/02/2019 19:48, Juergen Gross wrote:
> On 09/02/2019 19:45, Sander Eikelenboom wrote:
>> On 09/02/2019 09:26, Sander Eikelenboom wrote:
>>> L.S.,
>>>
>>>
>>> While testing a Linux 5.0-rc5-ish kernel (pull of yesterday) with some
>>> addi
On 11/02/2019 14:16, Roger Pau Monné wrote:
> On Fri, Feb 08, 2019 at 08:36:54PM +0100, Sander Eikelenboom wrote:
>> On 08/02/2019 17:47, Roger Pau Monné wrote:
>>> On Fri, Feb 08, 2019 at 05:15:22PM +0100, Sander Eikelenboom wrote:
>>>> On 08/02/2019 16:10, Roger
oyger/xen.git fixes-4.12-v2.1
I have tested this on AMD hardware, both as PVH dom0 and PV dom0
(running both PVH and HVM guests). So FWIW:
Tested-by: Sander Eikelenboom
> Roger Pau Monne (7):
> dom0/pvh: align allocation and mapping order to start address
> amd/npt/shadow: replace a
Hi Juergen,
Although xen-stable-4.12 is released now for some time (thanks for the timely
release !),
the release tag "RELEASE-4.12.0" is still only available in the "staging-4.12"
branch of the Xen git tree.
The "stable-4.12" is still a few (release-) commits short, it seems a bit
awkward.
L.S.,
At present one of my PVH VM's kernel crashed with the splat below
(haven't seen it before, so could be something that happens sporadically).
Any ideas ?
--
Sander
database databaselogin: login: [184503.428811] general protection fault:
[#1] SMP NOPTI
[184503.428887] CPU: 0 PID: 0
On 25/11/2019 15:42, Jan Beulich wrote:
> On 25.11.2019 15:21, Sander Eikelenboom wrote:
>> L.S.,
>>
>> At present one of my PVH VM's kernel crashed with the splat below
>> (haven't seen it before, so could be something that happens sporadically).
On 25/11/2019 15:42, Jan Beulich wrote:
> On 25.11.2019 15:21, Sander Eikelenboom wrote:
>> L.S.,
>>
>> At present one of my PVH VM's kernel crashed with the splat below
>> (haven't seen it before, so could be something that happens sporadically).
L.S.,
On current xen-unstable (4.14 to be) and AMD cpu:
After rebooting the host, while the guests are starting, I hit the assertion
below.
xen-staging-4.13 seems fine on the same machine.
--
Sander
(XEN) [2019-12-04 17:03:25.062] grant_table.c:1808:d7v0 Expanding d7 grant
table from 3 to 4
On 04/12/2019 18:30, Jan Beulich wrote:
> On 04.12.2019 18:21, Sander Eikelenboom wrote:
>> On current xen-unstable (4.14 to be) and AMD cpu:
>>
>> After rebooting the host, while the guests are starting, I hit the assertion
>> below.
>> xen-staging-4.
On 04/12/2019 22:31, Igor Druzhinin wrote:
> The locking responsibilities have changed and a premature break in
> this section now causes the following assertion:
>
> Assertion '!preempt_count()' failed at preempt.c:36
>
> Reported-by: Sander Eikelenboom
>
AMD IOMMU pagetables
>
>
> CREDITS
> ===
>
> This issue was discovered by Sander Eikelenboom, along with Andrew Cooper of
> Citrix.
Ahh this was why Jan's two patches were skipped, I was about to inquire
if it would be picked up in the future in some form.
--
Sander
On 16/12/2019 08:24, Jürgen Groß wrote:
> On 16.12.19 06:58, Tian, Kevin wrote:
>>> From: Jürgen Groß
>>> Sent: Friday, December 13, 2019 11:36 PM
>>>
>>> On 13.12.19 15:45, Jan Beulich wrote:
On 13.12.2019 15:24, Jürgen Groß wrote:
> On 13.12.19 15:11, Jan Beulich wrote:
>> On 13.12.
On 18/12/2019 18:00, Juergen Gross wrote:
> Dear community members,
>
> I'm pleased to announce that Xen 4.13.0 is released.
>
> Thanks everyone who contributed to this release. This release would
> not have happened without all the awesome contributions from around
> the globe.
>
> Regards,
>
so clean the QMP states and associated timeouts earlier, as soon
> as they are not needed anymore.
>
> Reported-by: Sander Eikelenboom
> Fixes: fae4880c45fe015e567afa223f78bf17a6d98e1b
> Signed-off-by: Anthony PERARD
>
Hi Anthony / Chao,
I have to come back to this, a bit beca
Hi Anthony,
While testing xen-unstable 4.13.0-rc0 I ran in to the following issue:
When passing through all 8 functions of a pci(e) device I can't start the guest
anymore, note that the trouble only starts at 0:9:0.3, not at 0:9:0.0:
libxl: error: libxl_qmp.c:1270:qmp_ev_connect: Domain
On 14/10/2019 17:03, Chao Gao wrote:
> On Thu, Oct 10, 2019 at 06:13:43PM +0200, Sander Eikelenboom wrote:
>> On 01/10/2019 12:35, Anthony PERARD wrote:
>>> Rewrite of the commit message:
>>>
>>> Before the problematic commit, libxl used to ignore error w
On 15/10/2019 18:59, Sander Eikelenboom wrote:
> On 14/10/2019 17:03, Chao Gao wrote:
>> On Thu, Oct 10, 2019 at 06:13:43PM +0200, Sander Eikelenboom wrote:
>>> On 01/10/2019 12:35, Anthony PERARD wrote:
>>>> Rewrite of the commit message:
>>>>
>>
On 18/10/2019 18:11, Anthony PERARD wrote:
> On Mon, Oct 14, 2019 at 11:03:43PM +0800, Chao Gao wrote:
>> On Thu, Oct 10, 2019 at 06:13:43PM +0200, Sander Eikelenboom wrote:
>>> Hi Anthony / Chao,
>>>
>>> I have to come back to this, a bit because perha
; tools/libxl/libxl_pci.c | 8 ++--
> tools/libxl/libxl_qmp.c | 75 +++++
> tools/libxl/libxl_usb.c | 28 ++--
> 12 files changed, 219 insertions(+), 60 deletions(-)
>
--
Met vriendelijke groet,
Sander Eikelenboom
mailto:s
Hi Jan / Andrew,
While testing the latest xen-unstable and starting an HVM guest with
pci-passtrough on my AMD machine,
my eye catched the following messages in xl dmesg I haven't seen before:
(XEN) [2019-10-28 10:23:16.372] AMD-Vi: update_paging_mode Try to access
pdev_list without aquiring pc
On 30/10/2019 16:48, Jan Beulich wrote:
> On 28.10.2019 11:32, Sander Eikelenboom wrote:
>> While testing the latest xen-unstable and starting an HVM guest with
>> pci-passtrough on my AMD machine,
>> my eye catched the following messages in xl dmesg I haven't seen befor
On 30/10/2019 19:06, Anthony PERARD wrote:
> Patch series available in this git branch:
> https://xenbits.xen.org/git-http/people/aperard/xen-unstable.git
> br.fix-ev_qmp-multi-connect-v2
>
> Hi,
>
> QEMU's QMP socket doesn't allow multiple concurrent connection. Also, it
> listen() on the socke
On 31/10/2019 10:18, Jan Beulich wrote:
> On 31.10.2019 09:35, Sander Eikelenboom wrote:
>> Platform is perhaps what specific (older AMD 890FX chipset) and I need the
>> bios workaround:
>> ivrs_ioapic[6]=00:14.0 iommu=on.
>
> Shouldn't matter here.
>
>
On 31/10/2019 11:15, Jan Beulich wrote:
> On 30.10.2019 23:21, Sander Eikelenboom wrote:
>> Call trace seems to be the same in all cases.
>>
>> --
>> Sander
>>
>>
>> (XEN) [2019-10-30 22:07:05.748] AMD-Vi: update_paging_mode Try to access
>> pdev
On 06/11/2019 16:16, Jan Beulich wrote:
> update_paging_mode() in the AMD IOMMU code expects to be invoked with
> the PCI devices lock held. The check occurring only when the mode
> actually needs updating, the violation of this rule by the majority
> of callers did go unnoticed until per-domain IO
On 07/11/2019 17:44, Jürgen Groß wrote:
> Hi Ian,
>
> in the Xen community call we agreed to try to speed up OSStest for
> xen-unstable in order to make better progress with the 4.13 release.
>
> Could you please suspend testing for Xen 4.10 and older (Jan agreed on
> that), and disable the Linux
On 08/11/2019 19:49, Ian Jackson wrote:
> Earlier this week we discovered that sg-report-host-history was running
> extremely slowly. We applied an emergency fix 0fa72b13f5af
> sg-report-host-history: Reduce limit from 2000 to 200
>
> The main problem is that sg-report-host-history runs once fo
On 11/11/2019 12:00, Ian Jackson wrote:
> Sander Eikelenboom writes ("Re: [Xen-devel] [OSSTEST PATCH 00/13] Speed up
> and restore host history"):
>> Not mend to bike shed, so just for consideration:
>
> Suggestions are very welcome. Be careful, I'm still looki
On 11/11/2019 16:35, Jan Beulich wrote:
> On 31.10.2019 21:48, Sander Eikelenboom wrote:
>> - The usb3 controller malfunctioning seems indeed to be a separate issue
>> (which seems unfortunate,
>> because a bisect seems to become even nastier with all th
On 12/11/2019 12:05, Jan Beulich wrote:
> On 11.11.2019 22:38, Sander Eikelenboom wrote:
>> When supplying "pci=nomsi" to the guest kernel, the device works fine,
>> and I don't get the "INVALID_DEV_REQUEST".
>>
>> After reverting 1b00c
On 08/11/2019 07:06, Jürgen Groß wrote:
> On 30.10.19 19:06, Anthony PERARD wrote:
>> Patch series available in this git branch:
>> https://xenbits.xen.org/git-http/people/aperard/xen-unstable.git
>> br.fix-ev_qmp-multi-connect-v2
>>
>> Hi,
>>
>> QEMU's QMP socket doesn't allow multiple concurrent
On 08/11/2019 07:07, Jürgen Groß wrote:
> On 31.10.19 13:17, Anthony PERARD wrote:
>> After sending the 'device_del' command for a PCI passthrough device,
>> we wait until QEMU has effectively deleted the device, this involves
>> executing more QMP commands. While waiting, libxl hold the connection
On 03/04/18 12:29, Juergen Gross wrote:
> On 03/04/18 12:19, osstest service owner wrote:
>> branch xen-unstable
>> xenbranch xen-unstable
>> job test-amd64-amd64-xl-pvhv2-amd
>> testid guest-start
>>
>> Tree: linux
>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
>> Tree: l
On 05/04/18 09:11, Juergen Gross wrote:
> On 03/04/18 18:55, Sander Eikelenboom wrote:
>> On 03/04/18 12:29, Juergen Gross wrote:
>>> On 03/04/18 12:19, osstest service owner wrote:
>>>> branch xen-unstable
>>>> xenbranch xen-unstable
>>>> job
L.S.,
When starting a guest with the 'xl create' command (non-verbose) i get
this extra output on PVH guest types only:
S3 disabled
S4 disabled
CONV disabled
It seems libacpi/* only contains normal printf's, so for the other guest
types i probably just never triggered one of them.
Shouldn't th
On 08/03/18 10:09, Jan Beulich wrote:
On 07.03.18 at 21:52, wrote:
>> When starting a guest with the 'xl create' command (non-verbose) i get
>> this extra output on PVH guest types only:
>>
>> S3 disabled
>> S4 disabled
>> CONV disabled
>>
>>
>> It seems libacpi/* only contains normal printf'
Hi Andrew,
It seems commit "x86/pv: Drop int80_bounce from struct pv_vcpu"
(f75b1a5247b3b311d3aa50de4c0e5f2d68085cb1) causes an issue on my machine,
an AMD phenom X6.
When trying to installing a new kernel package which runs the Debian
update-initramfs tools with xen-unstable which happened to
On 19/02/18 22:13, Sander Eikelenboom wrote:
> On 19/02/18 11:16, Juergen Gross wrote:
>> On 19/02/18 10:47, Sander Eikelenboom wrote:
>>> On 24/01/18 16:26, George Dunlap wrote:
>>>> On Wed, Jan 24, 2018 at 3:20 PM, Juergen Gross wrote:
>>>>> On 24/01
On 12/03/18 20:05, Andrew Cooper wrote:
> On 10/03/18 16:27, Andrew Cooper wrote:
>> On 10/03/2018 16:14, Sander Eikelenboom wrote:
>>> Hi Andrew,
>>>
>>> It seems commit "x86/pv: Drop int80_bounce from struct pv_vcpu"
>>> (f75b1a5247b3b311
On 12/03/18 21:04, Boris Ostrovsky wrote:
> On 03/12/2018 03:05 PM, Andrew Cooper wrote:
>> On 10/03/18 16:27, Andrew Cooper wrote:
>>> On 10/03/2018 16:14, Sander Eikelenboom wrote:
>>>> Hi Andrew,
>>>>
>>>> It seems
On 13/03/18 23:01, Andrew Cooper wrote:
> On 10/03/18 16:14, Sander Eikelenboom wrote:
>> Hi Andrew,
>>
>> It seems commit "x86/pv: Drop int80_bounce from struct pv_vcpu"
>> (f75b1a5247b3b311d3aa50de4c0e5f2d68085cb1) causes an issue on my machine,
>
On 05/07/18 10:43, Roger Pau Monné wrote:
> On Thu, Jul 05, 2018 at 09:19:10AM +0100, Wei Liu wrote:
>> On Thu, Jul 05, 2018 at 10:06:52AM +0200, Roger Pau Monné wrote:
>>> On Thu, Jul 05, 2018 at 08:53:51AM +0100, Wei Liu wrote:
On Wed, Jul 04, 2018 at 03:26:16PM +, George Dunlap wrote:
>
Thursday, July 5, 2018, 5:14:39 PM, you wrote:
> Juergen Gross writes ("Re: [Xen-devel] [Notes for xen summit 2018 design
> session] Process changes: is the 6 monthly release Cadence too short,
> Security Process, ..."):
>> Same applies to the host: the base system (without the to be tested
>>
On 05/07/18 19:02, Ian Jackson wrote:
> Andrew Cooper writes ("Re: [Xen-devel] [Notes for xen summit 2018 design
> session] Process changes: is the 6 monthly release Cadence too short,
> Security Process, ..."):
>> XenRT, which is XenServers provisioning and testing system and install,
>> can dep
On 05/07/18 19:11, Ian Jackson wrote:
> Sander Eikelenboom writes ("Re: [Xen-devel] [Notes for xen summit 2018 design
> session] Process changes: is the 6 monthly release Cadence too short,
> Security Process, ..."):
>> Just wondering, are there any timing statis
On 05/07/18 19:25, Ian Jackson wrote:
> George Dunlap writes ("Re: [Xen-devel] [Notes for xen summit 2018 design
> session] Process changes: is the 6 monthly release Cadence too short,
> Security Process, ..."):
>> I don’t really understand why you’re more worried about a test
>> corrupting a bac
On 05/07/18 19:11, Ian Jackson wrote:
> Sander Eikelenboom writes ("Re: [Xen-devel] [Notes for xen summit 2018 design
> session] Process changes: is the 6 monthly release Cadence too short,
> Security Process, ..."):
>> Just wondering, are there any timing statis
On 06/07/18 00:47, Sander Eikelenboom wrote:
> On 05/07/18 19:11, Ian Jackson wrote:
>> Sander Eikelenboom writes ("Re: [Xen-devel] [Notes for xen summit 2018
>> design session] Process changes: is the 6 monthly release Cadence too short,
>> Security Process, ...")
Marek / Ian,
Nice to see PCI-passthrough getting some attention again.
On 17/05/18 17:12, Ian Jackson wrote:
> Marek Marczykowski-Górecki writes ("Re: Test for osstest, features used in
> Qubes OS"):
>> On Thu, May 17, 2018 at 01:26:30PM +0100, Ian Jackson wrote:
>>> Is it likely that this will
On 27/09/18 16:26, Jens Axboe wrote:
> On 9/27/18 1:12 AM, Juergen Gross wrote:
>> On 22/09/18 21:55, Boris Ostrovsky wrote:
>>> Commit a46b53672b2c ("xen/blkfront: cleanup stale persistent grants")
>>> added support for purging persistent grants when they are not in use. As
>>> part of the purge,
On 27/09/18 21:06, Boris Ostrovsky wrote:
> On 9/27/18 2:56 PM, Jens Axboe wrote:
>> On 9/27/18 12:52 PM, Sander Eikelenboom wrote:
>>> On 27/09/18 16:26, Jens Axboe wrote:
>>>> On 9/27/18 1:12 AM, Juergen Gross wrote:
>>>>> On 22/09/18 21:55, Bori
On 27/09/18 23:48, Boris Ostrovsky wrote:
> On 9/27/18 5:37 PM, Jens Axboe wrote:
>> On 9/27/18 2:33 PM, Sander Eikelenboom wrote:
>>> On 27/09/18 21:06, Boris Ostrovsky wrote:
>>>> On 9/27/18 2:56 PM, Jens Axboe wrote:
>>>>> On 9/27/18 12:52 PM, Sande
On 24/01/18 16:26, George Dunlap wrote:
> On Wed, Jan 24, 2018 at 3:20 PM, Juergen Gross wrote:
>> On 24/01/18 16:07, George Dunlap wrote:
>>> On Wed, Jan 24, 2018 at 2:10 PM, Boris Ostrovsky
>>> wrote:
On 01/24/2018 07:06 AM, Juergen Gross wrote:
> On 24/01/18 11:54, Roger Pau Monné wro
On 19/02/18 11:16, Juergen Gross wrote:
> On 19/02/18 10:47, Sander Eikelenboom wrote:
>> On 24/01/18 16:26, George Dunlap wrote:
>>> On Wed, Jan 24, 2018 at 3:20 PM, Juergen Gross wrote:
>>>> On 24/01/18 16:07, George Dunlap wrote:
>>>>> On
Hi Juergen / Boris,
Last week i tested Linux kernel 4.19.0 stable with the Xen "for-linus-4.20"
branch pulled on top.
Unfortunately i was seeing guests lockup after some time, see below for the
logging from one of the guest
which i was able to capture.
Reverting "xen: make xen_qlock_wait() nesta
On 07/11/18 23:34, Boris Ostrovsky wrote:
> On 11/7/18 4:30 AM, Sander Eikelenboom wrote:
>> Hi Juergen / Boris,
>>
>> Last week i tested Linux kernel 4.19.0 stable with the Xen "for-linus-4.20"
>> branch pulled on top.
>> Unfortunately i was seeing g
Hi Ian,
I just tested a manual install of a Win10-1703-x86 iso, with about as much the
same
xen config as the OSStest has.
The install succeeds in about an hour on my machine, with networking (DHCP) up
and running,
without the need for any extra drivers.
So i haven't ran into the issue where
On 08/11/18 08:08, Juergen Gross wrote:
> On 07/11/2018 10:30, Sander Eikelenboom wrote:
>> Hi Juergen / Boris,
>>
>> Last week i tested Linux kernel 4.19.0 stable with the Xen "for-linus-4.20"
>> branch pulled on top.
>> Unfortunately i was seeing guest
On 08/11/18 09:18, Juergen Gross wrote:
> On 08/11/2018 09:14, Sander Eikelenboom wrote:
>> On 08/11/18 08:08, Juergen Gross wrote:
>>> On 07/11/2018 10:30, Sander Eikelenboom wrote:
>>>> Hi Juergen / Boris,
>>>>
>>>> Last week i tested Linux k
On 08/11/18 11:18, Juergen Gross wrote:
> On 08/11/2018 10:57, Sander Eikelenboom wrote:
>> On 08/11/18 09:18, Juergen Gross wrote:
>>> On 08/11/2018 09:14, Sander Eikelenboom wrote:
>>>> On 08/11/18 08:08, Juergen Gross wrote:
>>>>> On 07/11/2018 10:30
it() nestable")
> Cc: sta...@vger.kernel.org
> Signed-off-by: Juergen Gross
Although you don't seem too interested, you can stick on a:
Tested-by: Sander Eikelenboom
if you like.
--
Sander
> ---
> arch/x86/xen/spinlock.c | 14 --
> 1 file changed, 8 insertio
On 09/11/18 16:20, Juergen Gross wrote:
> On 09/11/2018 16:02, Sander Eikelenboom wrote:
>> On 09/11/18 13:04, Juergen Gross wrote:
>>> Commit a856531951dc80 ("xen: make xen_qlock_wait() nestable")
>>> introduced a regression for Xen guests running fully virtu
On 23/11/18 14:34, Lars Kurth wrote:
> FYI: no Xen Project booth at FOSDEM this year
Bummer, no fresh T-shirt :(.
--
Sander
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
On 04/01/18 12:44, Juergen Gross wrote:
> On 04/01/18 11:17, Sander Eikelenboom wrote:
>> Hi Boris / Juergen,
>>
>> First of all best wishes for a quite turbulent starting new year.
>>
>> Now the holidays are over I finally gotten to test a linux 4.15-rc6 kernel
&g
Since it's already rc7:
"Give me a subtle ping, Vasili. One subtle ping only, please."
On 04/01/18 21:02, Sander Eikelenboom wrote:
> On 04/01/18 12:44, Juergen Gross wrote:
>> On 04/01/18 11:17, Sander Eikelenboom wrote:
>>> Hi Boris / Juergen,
>>>
;
> Thank you,
> Pavel
>
> On 01/09/2018 11:10 AM, Juergen Gross wrote:
>> On 09/01/18 16:29, Sander Eikelenboom wrote:
>>> Since it's already rc7:
>>> "Give me a subtle ping, Vasili. One subtle ping only, please."
>>
>> I like that film
On 09/01/18 17:38, Boris Ostrovsky wrote:
> On 01/09/2018 11:31 AM, Sander Eikelenboom wrote:
>> On 09/01/18 17:16, Pavel Tatashin wrote:
>>> Hi Juergen,
>>>
>>> Do you have this patch applied:
>>>
>>> https://github.com/torvalds/linux/commit/
Hi Igor/Jan,
I tried to update my AMD machine to current xen-unstable, but
unfortunately the HVM guests don't boot after that. The guest keeps
using CPU-cycles but I don't get to a command prompt (or any output at
all). PVH guests run fine.
Bisection leads to commit:
8efa46516c5f4cf185c8df179812
On 11/10/2020 02:06, Igor Druzhinin wrote:
> On 10/10/2020 18:51, Sander Eikelenboom wrote:
>> Hi Igor/Jan,
>>
>> I tried to update my AMD machine to current xen-unstable, but
>> unfortunately the HVM guests don't boot after that. The guest keeps
>> using C
On 11/10/2020 13:20, Igor Druzhinin wrote:
> On 11/10/2020 11:40, Igor Druzhinin wrote:
>> On 11/10/2020 10:43, Sander Eikelenboom wrote:
>>> On 11/10/2020 02:06, Igor Druzhinin wrote:
>>>> On 10/10/2020 18:51, Sander Eikelenboom wrote:
>>>>> Hi I
On 16/10/2020 08:34, Jan Beulich wrote:
> On 16.10.2020 02:39, Igor Druzhinin wrote:
>> ACPI specification contains statements describing memory marked with regular
>> "ACPI data" type as reclaimable by the guest. Although the guest shouldn't
>> really do it if it wants kexec or similar functionali
On 09/04/2020 09:41, Jan Beulich wrote:
> All,
>
> the releases are due in a week or two. Please point out backports
> you find missing from the respective staging branches, but which
> you consider relevant. (Ian, I notice there haven't been any
> tools side backports at all so far. Julien, Stefa
On 03/02/2020 14:21, Roger Pau Monné wrote:
> On Mon, Feb 03, 2020 at 01:44:06PM +0100, Sander Eikelenboom wrote:
>> On 03/02/2020 13:41, Roger Pau Monné wrote:
>>> On Mon, Feb 03, 2020 at 01:30:55PM +0100, Sander Eikelenboom wrote:
>>>> On 03/02/2020 13:23, Roger
On 11/02/2020 15:00, Roger Pau Monné wrote:
> On Mon, Feb 10, 2020 at 09:49:30PM +0100, Sander Eikelenboom wrote:
>> On 03/02/2020 14:21, Roger Pau Monné wrote:
>>> On Mon, Feb 03, 2020 at 01:44:06PM +0100, Sander Eikelenboom wrote:
>>>> On 03/02/2020 13:41, Roger
On 12/02/2020 17:49, Roger Pau Monne wrote:
> Hello,
>
> Commit:
>
> 5500d265a2a8fa63d60c08beb549de8ec82ff7a5
> x86/smp: use APIC ALLBUT destination shorthand when possible
>
> Introduced a bogus usage of the scratch cpumask: it was used in a
> function that could be called from interrupt contex
On 12/02/2020 18:01, Roger Pau Monné wrote:
> On Wed, Feb 12, 2020 at 05:53:39PM +0100, Sander Eikelenboom wrote:
>> On 12/02/2020 17:49, Roger Pau Monne wrote:
>>> Hello,
>>>
>>> Commit:
>>>
>>> 5500d265a2a8fa63d60c08beb549de8ec82ff7a5
&
On 12/02/2020 18:13, Sander Eikelenboom wrote:
> On 12/02/2020 18:01, Roger Pau Monné wrote:
>> On Wed, Feb 12, 2020 at 05:53:39PM +0100, Sander Eikelenboom wrote:
>>> On 12/02/2020 17:49, Roger Pau Monne wrote:
>>>> Hello,
>>>>
>>>> Comm
On 17/02/2020 20:58, Sarah Newman wrote:
> On 1/7/20 6:25 AM, Alastair Browne wrote:
>>
>> CONCLUSION
>>
>> So in conclusion, the tests indicate that credit2 might be unstable.
>>
>> For the time being, we are using credit as the chosen scheduler. We
>> are booting the kernel with a parameter "sche
1 - 100 of 133 matches
Mail list logo
