Re: Bug#1063270: The "64bits time_t transition" in Debian/Xen

Hi, On 2/12/24 18:43, Andrew Cooper wrote: > On 12/02/2024 5:27 pm, zithro wrote: >> Hey all, >> >> the Debian project is focused on the "2038 time_t" switch. >> So the maintainers of the Debian Xen package must ensure that all >> imported Xen code conforms to the new Debian standards. >> >> I

Re: (Debian) Bug#1051862: server flooded with xen_mc_flush warnings with xen 4.17 + linux 6.1

Hi Radoslav, Thanks for your report... Hi Juergen, Boris and xen-devel, At Debian, we got the report below. (Also at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051862) This hardware, with only Xen and Dom0 running is hitting the failed multicall warning and logging in

Debian Bug#1004269: Linker segfault while building src:xen

(To both the Debian bug # and xen-devel list, reply-all is fine) Hi Xen people, I just filed a bug at Debian on the binutils package, because since the latest binutils package update (Debian 2.37.50.20220106-2), Xen (both 4.14 and 4.16) fails to build with a segfault at the following point:

Re: [PATCH] xen/iommu: smmu: Use 1UL << 31 rather than 1 << 31

On 12/24/20 4:24 PM, Julien Grall wrote: > From: Julien Grall > > Replace all the use of 1 << 31 with 1UL << 31 to prevent undefined > behavior in the SMMU driver. You're replacing it by 1U, not 1UL, in the patch below. Hans > Signed-off-by: Julien Grall > --- >

Re: [XEN PATCH v2] docs: set date to SOURCE_DATE_EPOCH if available

Hi, On 12/23/20 5:56 PM, Maximilian Engelhardt wrote: > check if a GNU date that supports the '-u -d @...' options and syntax or > a BSD date are available. If so, use the appropriate options for the > date command to produce a custom date if SOURCE_DATE_EPOCH is defined. > If SOURCE_DATE_EPOCH

Re: Compiling Xen from source

On 9/16/20 6:12 PM, Olaf Hering wrote: > On Wed, Sep 16, David I wrote: > >> So, how did the debian package was compiled ? is this the same source code >> with >> different options ? > > Xen 4.11 is from 2018. Use also a compiler from that year. > Using this years compiler will lead to

Re: Compiling Xen from source

Hi, On 9/16/20 12:00 AM, Andrew Cooper wrote: > On 15/09/2020 21:16, David I wrote: >> Hello, >> >> I am unable to mcompile xen-tools from source. >> >> here is the "stacktrace": >> >> ln -f xenstore xenstore-watch >> gcc xenstore_control.o     >>  

4.14.0 FTBFS for Debian unstable, libxlu_pci.c (╯°□°）╯︵ ┻━┻

Hi! News from the Debian Xen team (well, that's still only Ian and me). We still have Xen 4.11 in Debian unstable and stable (Buster) now, but at this point I really want to start working on the preparations for the next Debian release which will happen in about a little bit less than a year from

Re: Bug: toolstack allows too low values to be set for shadow_memory

Hi, On 5/26/20 9:41 AM, Jan Beulich wrote: > On 25.05.2020 17:51, Hans van Kranenburg wrote: >> This bug report is a follow-up to the thread "Domu windows 2012 crash" >> on the xen-users list. In there we found out that it is possible to set >> a value for shadow_m

Bug: toolstack allows too low values to be set for shadow_memory

ig for 10+ years and just only adjust things when it breaks after upgrading Xen. Hans van Kranenburg

Re: [Xen-devel] [PATCH for-4.13 2/2] Rationalize max_grant_frames and max_maptrack_frames handling

On 11/28/19 3:54 PM, George Dunlap wrote: > On 11/27/19 10:32 PM, Hans van Kranenburg wrote: >> Hi all, >> >> On 11/27/19 12:13 PM, Durrant, Paul wrote: >>>> -Original Message- >>>> From: Ian Jackson >>>> Sent: 27 November 2

Re: [Xen-devel] [PATCH for-4.13 2/2] Rationalize max_grant_frames and max_maptrack_frames handling

Hi all, On 11/27/19 12:13 PM, Durrant, Paul wrote: >> -Original Message- >> From: Ian Jackson >> Sent: 27 November 2019 11:10 >> [...] >> Subject: RE: [Xen-devel] [PATCH for-4.13 2/2] Rationalize max_grant_frames >> and max_maptrack_frames handling >> >> Durrant, Paul writes ("RE:

Re: [Xen-devel] [PATCH] docs/sphinx: Introduction

Hi, (dropped most of the Cc:) On 8/7/19 9:41 PM, Andrew Cooper wrote: > Put together an introduction page for the Sphinx/RST docs, along with a > glossary which will accumulate over time. > [...] I've been using Xen for 13+ years now, so I'm not really able to provide feedback about how someone

Re: [Xen-devel] Design session report: Xen on Distros

Hi, On 7/15/19 4:42 PM, George Dunlap wrote: > On 7/15/19 3:23 PM, Jan Beulich wrote: >> On 15.07.2019 16:11, George Dunlap wrote: >>> There was a long discussion about security patches, with the general >>> proposal being that we should cut a point release for every security issue. >> >>

Re: [Xen-devel] python3 issues

On 3/26/19 2:16 PM, Wei Liu wrote: > On Mon, Mar 25, 2019 at 10:20:05PM +, YOUNG, MICHAEL A. wrote: >> [...] >> --- xen-4.12.0-rc6/tools/pygrub/src/pygrub.orig 2019-03-24 >> 22:44:05.503582025 + >> +++ xen-4.12.0-rc6/tools/pygrub/src/pygrub 2019-03-24 22:48:24.446113809 >> +

Re: [Xen-devel] python3 issues

On 3/26/19 7:18 PM, M A Young wrote: > On Tue, 26 Mar 2019, Wei Liu wrote: > >> On Tue, Mar 26, 2019 at 01:16:35PM +, Wei Liu wrote: >>> On Mon, Mar 25, 2019 at 10:20:05PM +, YOUNG, MICHAEL A. wrote: if ty.init_fn is not None: ---

Re: [Xen-devel] [PATCH for-next v2 v2 2/5] libxl: make python scripts work with python 2.6 and up

On 3/6/19 6:52 PM, Wei Liu wrote: > Go through the transformations suggested by 2to3 and pick the > necessary ones. > > Use sys.stderr.write to avoid importing from __future__. > > Signed-off-by: Wei Liu > --- > tools/libxl/gentest.py | 2 +- > tools/libxl/gentypes.py | 10 +- >

Re: [Xen-devel] [admin] [Pkg-xen-devel] [BUG] task jbd2/xvda4-8:174 blocked for more than 120 seconds.

On 2/11/19 2:37 AM, Dongli Zhang wrote: > > On 2/10/19 12:35 AM, Samuel Thibault wrote: >> >> Hans van Kranenburg, le sam. 09 févr. 2019 17:01:55 +0100, a ecrit: >>>> I have forwarded the original mail: all VM I/O get stuck, and thus the >>>> VM becomes

Re: [Xen-devel] [admin] [Pkg-xen-devel] [BUG] task jbd2/xvda4-8:174 blocked for more than 120 seconds.

Hi, On 2/9/19 12:16 AM, Samuel Thibault wrote: > > Hans van Kranenburg, le ven. 08 févr. 2019 20:18:44 +0100, a ecrit: >> [...] >> >> On 2/8/19 6:13 PM, Samuel Thibault wrote: >>> >>> Sacha, le ven. 08 févr. 2019 18:00:22 +0100, a ecrit: >>>

Re: [Xen-devel] [Pkg-xen-devel] [admin] [BUG] task jbd2/xvda4-8:174 blocked for more than 120 seconds.

Hi, Upstream mailing list is at: xen-devel@lists.xenproject.org Apparently, x...@packages.debian.org results in a message to pkg-xen-de...@lists.alioth.debian.org On 2/8/19 6:13 PM, Samuel Thibault wrote: > > Sacha, le ven. 08 févr. 2019 18:00:22 +0100, a ecrit: >> On  Debian GNU/Linux

[Xen-devel] [PATCH] tools/misc: Remove obsolete xen-bugtool

ugtool", line 9, in from xen.util import bugtool ImportError: No module named xen.util Signed-off-by: Hans van Kranenburg Link: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866380 Cc: Ian Jackson Cc: Wei Liu --- docs/README.xen-bugtool | 16 tools/misc/Makefil

Re: [Xen-devel] [PATCH v3] xen: Fix x86 sched_clock() interface for xen

resume time to ensure a >> monotonic clock value. >> >> Fixes: f94c8d11699759 ("sched/clock, x86/tsc: Rework the x86 'unstable' >> sched_clock() interface") >> Cc: # 4.11 >> Reported-by: Hans van Kranenburg >> Signed-off-by: Juergen Gross > &

Re: [Xen-devel] [PATCH v3] xen: Fix x86 sched_clock() interface for xen

Hi, On 1/14/19 1:44 PM, Juergen Gross wrote: > Commit f94c8d11699759 ("sched/clock, x86/tsc: Rework the x86 'unstable' > sched_clock() interface") broke Xen guest time handling across > migration: > > [ 187.249951] Freezing user space processes ... (elapsed 0.001 seconds) done. > [ 187.251137]

Re: [Xen-devel] [PATCH v2] xen: Fix x86 sched_clock() interface for xen

On 1/11/19 4:57 PM, Hans van Kranenburg wrote: > On 1/11/19 3:01 PM, Juergen Gross wrote: >> On 11/01/2019 14:12, Hans van Kranenburg wrote: >>> Hi, >>> >>> On 1/11/19 1:08 PM, Juergen Gross wrote: >>>> Commit f94c8d11699759 ("sched/clock

Re: [Xen-devel] [PATCH v2] xen: Fix x86 sched_clock() interface for xen

On 1/11/19 3:01 PM, Juergen Gross wrote: > On 11/01/2019 14:12, Hans van Kranenburg wrote: >> Hi, >> >> On 1/11/19 1:08 PM, Juergen Gross wrote: >>> Commit f94c8d11699759 ("sched/clock, x86/tsc: Rework the x86 'unstable' >>> sched_clock() inte

Re: [Xen-devel] [PATCH v2] xen: Fix x86 sched_clock() interface for xen

Hi, On 1/11/19 1:08 PM, Juergen Gross wrote: > Commit f94c8d11699759 ("sched/clock, x86/tsc: Rework the x86 'unstable' > sched_clock() interface") broke Xen guest time handling across > migration: > > [ 187.249951] Freezing user space processes ... (elapsed 0.001 seconds) done. > [ 187.251137]

Re: [Xen-devel] [PATCH] xen: Fix x86 sched_clock() interface for xen

.947688] Setting capacity to 6291456 [ 74.950833] Setting capacity to 10485760 Tested-by: Hans van Kranenburg Thanks! > > Fix that by setting xen_sched_clock_offset at resume time to ensure a > monotonic clock value. > > Fixes: f94c8d11699759 ("sched/clock, x86/tsc: Rework the x8

Re: [Xen-devel] Live migrate with Linux >= 4.13 domU causes kernel time jumps and TCP connection stalls.

On 1/7/19 1:04 PM, Juergen Gross wrote: > On 28/12/2018 15:41, Hans van Kranenburg wrote: >> On 12/28/18 11:15 AM, Juergen Gross wrote: >> >> [...] >> So that explains the 18446742891.874140 number, which just corresponds >> to something near to 'minus 23 minutes

Re: [Xen-devel] Live migrate with Linux >= 4.13 domU causes kernel time jumps and TCP connection stalls.

On 12/28/18 11:15 AM, Juergen Gross wrote: > On 27/12/2018 22:12, Hans van Kranenburg wrote: >> So, >> >> On 12/24/18 1:32 AM, Hans van Kranenburg wrote: >>> >>> On 12/21/18 6:54 PM, Hans van Kranenburg wrote: >>>> >>>> We've bee

Re: [Xen-devel] Live migrate with Linux >= 4.13 domU causes kernel time jumps and TCP connection stalls.

So, On 12/24/18 1:32 AM, Hans van Kranenburg wrote: > > On 12/21/18 6:54 PM, Hans van Kranenburg wrote: >> >> We've been tracking down a live migration bug during the last three days >> here at work, and here's what we found so far. >> >> 1. Xen version and do

Re: [Xen-devel] Live migrate with Linux >= 4.13 domU causes kernel time jumps and TCP connection stalls.

Hi, On 12/21/18 6:54 PM, Hans van Kranenburg wrote: > Hi, > > We've been tracking down a live migration bug during the last three days > here at work, and here's what we found so far. > > 1. Xen version and dom0 linux kernel version don't matter. > 2. DomU kernel is >

[Xen-devel] Live migrate with Linux >= 4.13 domU causes kernel time jumps and TCP connection stalls.

Hi, We've been tracking down a live migration bug during the last three days here at work, and here's what we found so far. 1. Xen version and dom0 linux kernel version don't matter. 2. DomU kernel is >= Linux 4.13. When using live migrate to another dom0, this often happens: [ 37.511305]

Re: [Xen-devel] Linux 4.19.5 fails to boot as Xen dom0

gt;>>>> On 29/11/2018 02:22, Hans van Kranenburg wrote: >>>>>> Hi, >>>>>> >>>>>> As also seen at: >>>>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914951 >>>>>> >>>>>&

Re: [Xen-devel] Linux 4.19.5 fails to boot as Xen dom0

On 11/30/18 5:21 PM, Kirill A. Shutemov wrote: > On Fri, Nov 30, 2018 at 02:53:50PM +0000, Hans van Kranenburg wrote: >> On 11/30/18 2:26 PM, Kirill A. Shutemov wrote: >>> On Fri, Nov 30, 2018 at 01:11:56PM +, Hans van Kranenburg wrote: >>>> On 11/29/18 4:0

Re: [Xen-devel] Linux 4.19.5 fails to boot as Xen dom0

On 11/30/18 2:26 PM, Kirill A. Shutemov wrote: > On Fri, Nov 30, 2018 at 01:11:56PM +0000, Hans van Kranenburg wrote: >> On 11/29/18 4:06 PM, Kirill A. Shutemov wrote: >>> On Thu, Nov 29, 2018 at 03:00:45PM +, Juergen Gross wrote: >>>> On 29/11/2018 1

Re: [Xen-devel] Linux 4.19.5 fails to boot as Xen dom0

On 11/30/18 2:26 PM, Kirill A. Shutemov wrote: > On Fri, Nov 30, 2018 at 01:11:56PM +0000, Hans van Kranenburg wrote: >> On 11/29/18 4:06 PM, Kirill A. Shutemov wrote: >>> On Thu, Nov 29, 2018 at 03:00:45PM +, Juergen Gross wrote: >>>> On 29/11/2018 1

Re: [Xen-devel] Linux 4.19.5 fails to boot as Xen dom0

1:35:17PM +, Juergen Gross wrote: >>>>> On 29/11/2018 14:26, Kirill A. Shutemov wrote: >>>>>> On Thu, Nov 29, 2018 at 09:41:25AM +0000, Juergen Gross wrote: >>>>>>> On 29/11/2018 02:22, Hans van Kranenburg wrote: >>>>>>>&

Re: [Xen-devel] [PATCH v6 00/20] xen: add pvh guest support

t be located at the usual physical address just below 1MB. >> >> The related Linux kernel patches have been accepted for 4.20-rc4 > > Patch set LGTM. If there are no objections I will apply it in a week > or so. > > Hans, may I add "Tested-by: Hans

[Xen-devel] Linux 4.19.5 fails to boot as Xen dom0

Hi, As also seen at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914951 Attached there are two serial console output logs. One is starting with Xen 4.11 (from debian unstable) as dom0, and the other one without Xen. [2.085543] BUG: unable to handle kernel paging request at

Re: [Xen-devel] [PATCH 0/2] Move RSDP address out of setup_header

Hi, On 11/20/18 8:25 AM, Juergen Gross wrote: > Resend with Daniel's mailo address corrected > > Instead of passing the RSDP address for Xen PVH guests from grub2 to > the kernel in setup_header move it into the non-legacy part of the > boot_params structure. > > This patch series should be

Re: [Xen-devel] [PATCH v6 16/20] grub-module-verifier: Ignore all_video for xenpvh

On 11/28/18 2:55 PM, Juergen Gross wrote: > From: Hans van Kranenburg > > This solves the build failing with "Error: no symbol table and no > .moddeps section" > > Also see: > - 6371e9c10433578bb236a8284ddb9ce9e201eb59 > - https://savannah.gnu.org/bugs/?

Re: [Xen-devel] [PATCH v2] libxencall: Improve linux syscall error messages

really scary, and if they're not a bug, but an expected thing because of settings, the way of presenting them to the user should not look like a really serious problem. Hans > This assists diagnosis. > > CC: Andrew Cooper > CC: Hans van Kranenburg > --- > v2: Print sizes. >

Re: [Xen-devel] [PATCH 07/12] tools/xenstore: Re-introduce (fake) xs_restrict call to preserve ABI

On 10/12/2018 05:12 PM, Ian Jackson wrote: > From: Hans van Kranenburg No, this was in the changes that I copied back from Ubuntu, it was written by Stefan Bader: >8 Description: Re-introduce fake xs_restrict API call libxenstore cannot remove an API function without changi

Re: [Xen-devel] SMT/Hyperthreading detection not always correct

On 09/03/2018 03:35 PM, Jan Beulich wrote: On 03.09.18 at 15:24, wrote: >> (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) >> (XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x20] enabled) >> (XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x10] enabled) >> (XEN) ACPI: LAPIC (acpi_id[0x18]

Re: [Xen-devel] SMT/Hyperthreading detection not always correct

On 09/03/2018 03:13 PM, Jan Beulich wrote: On 03.09.18 at 13:55, wrote: >> I ran into the situation where I got this banner in the xl dmesg... >> >> (XEN) *** >> (XEN) Booted on L1TF-vulnerable hardware with SMT/Hyperthreading >> (XEN) enabled.

[Xen-devel] SMT/Hyperthreading detection not always correct

Hi, I ran into the situation where I got this banner in the xl dmesg... (XEN) *** (XEN) Booted on L1TF-vulnerable hardware with SMT/Hyperthreading (XEN) enabled. Please assess your configuration and choose an (XEN) explicit 'smt=' setting. See

Re: [Xen-devel] [PATCH] tools/xentop : replace use of deprecated vwprintw

Hi, On 07/19/2018 08:53 AM, Wei Liu wrote: > On Wed, Jul 18, 2018 at 03:22:17PM -0700, Christopher Clark wrote: >> gcc-8.1 complains: >> >> | xentop.c: In function 'print': >> | xentop.c:304:4: error: 'vwprintw' is deprecated >> [-Werror=deprecated-declarations] >> | vwprintw(stdscr,

Re: [Xen-devel] [Xen-users] Future of 32-bit PV support

On 08/17/2018 06:09 AM, Juergen Gross wrote: > On 17/08/18 00:33, Andy Smith wrote: >> Hi Juergen, >> >> [...] >> If so, could the final removal of 32-bit PV in the Linux kernel be >> held off until there is: >> >> 1) a kernel shipping in Debian stable, Ubuntu LTS and CentOS that >>boots

Re: [Xen-devel] [PATCH v2] libxl: put RSDP for PVH guest near 4GB

On 01/24/2018 01:06 PM, Juergen Gross wrote: > On 24/01/18 11:54, Roger Pau Monné wrote: >> On Wed, Jan 24, 2018 at 10:42:39AM +, George Dunlap wrote: >>> On Wed, Jan 24, 2018 at 2:41 AM, Boris Ostrovsky >>> wrote: On 01/18/2018 05:33 AM, Wei Liu wrote: >

Re: [Xen-devel] Clarification regarding Meltdown and 64-bit PV guests

On 14/01/2018 15:00, Dongli Zhang wrote: > Hi Hans, > > On 01/13/2018 07:12 PM, Hans van Kranenburg wrote: >> On 01/13/2018 11:08 AM, Andy Smith wrote: >>> Hi Hans, >>> >>> On Sat, Jan 13, 2018 at 10:43:03AM +0100, Hans van Kranenburg wrote: >&g

Re: [Xen-devel] Clarification regarding Meltdown and 64-bit PV guests

On 01/13/2018 11:08 AM, Andy Smith wrote: > Hi Hans, > > On Sat, Jan 13, 2018 at 10:43:03AM +0100, Hans van Kranenburg wrote: >> By injecting a copy of a hypervisor between the outer level hypervisor >> (that's called L0 right?) (in HVM or PVH mode) and the guest, having i

Re: [Xen-devel] Clarification regarding Meltdown and 64-bit PV guests

On 01/13/2018 07:42 AM, Andy Smith wrote: > Hi, > > In > : > > "On Intel processors, only 64-bit PV mode guests can attack Xen > using Variant 3. [...] 64bit PV domU userspace can attack the hypervisor -> read

Re: [Xen-devel] Xen Project Spectre/Meltdown FAQ

On 01/11/2018 08:22 PM, Peter wrote: > On 2018-01-11 22:16, Lars Kurth wrote: >> And this time with attachment >>> On 11 Jan 2018, at 09:15, Lars Kurth >>> wrote: >>> >>> I am wondering whether something like the attached table would make >>> understanding the FAQ

Re: [Xen-devel] Radical proposal: ship not-fully-tidied shim as 4.10.1

On 01/10/2018 06:50 AM, Juergen Gross wrote: > On 09/01/18 23:11, Hans van Kranenburg wrote: >> On 01/09/2018 07:22 PM, Rich Persaud wrote: >>> >> >>> Since the primary audience for security fixes are production >>> deployments of Xen where customer as

Re: [Xen-devel] Xen Project Spectre/Meltdown FAQ

On 01/11/2018 10:15 AM, Lars Kurth wrote: > I am wondering whether something like the attached table would make > understanding the FAQ easier. Page 1 is clearly what is Xen specific and > we definitely should cover. > Page 2 in general covers Linux and guests. The first block is relatively >

Re: [Xen-devel] Radical proposal: ship not-fully-tidied shim as 4.10.1

On 01/09/2018 07:22 PM, Rich Persaud wrote: >>> On Jan 9, 2018, at 12:56, Stefano Stabellini wrote: >>> >>> On Tue, 9 Jan 2018, Doug Goldstein wrote: >>> On 1/9/18 11:33 AM, Jan Beulich wrote: >>> On 09.01.18 at 18:23, wrote: > On Tue, Jan

[Xen-devel] debian bugs: kaiser patch break pvh v1

or newer. Regards, Hans van Kranenburg ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel

Re: [Xen-devel] Xen Project Spectre/Meltdown FAQ

On 01/05/2018 12:35 PM, Lars Kurth wrote: > Hi all, this is a repost of > https://blog.xenproject.org/2018/01/04/xen-project-spectremeltdown-faq/ > for xen-users/xen-devel. If you have questions, please reply to this > thread and we will try and improve the FAQ based on questions. > Regards Lars