Hi Aleksi,
Thanks for the report. I actually ran into the same situation recently,
wanting to set up a PPPoE connection from within a Xen domU, also using
openvswitch as bridge.
On 19/03/2024 12:21, Aleksi Suhonen wrote:
> Package: src:xen
> Version: 4.17.3+10-g091466ba55-1~deb12u1
> Severity:
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
Package: debian-security-support
Version: 1:11+2023.05.04
Severity: normal
Hi,
Upstream security support for Xen 4.14 has ended recently. This also
means that security support for Debian Bullseye has ended.
The complexity of the software involved does not really allow for anyone
else than the
Hi Adam,
On 9/28/23 19:09, Adam D. Barratt wrote:
> On Thu, 2023-09-28 at 18:27 +0200, Hans van Kranenburg wrote:
>> Xen 4.14 support (and security support) has ended upstream. The
>> upstream
>> stable branch for version 4.14 is frozen now, and a final maintenance
>>
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
Hi,
On 8/8/23 15:22, Valentin Kleibel wrote:
>> On [0], you can read "In both cases the device naming is subject to the
>> usual guest or backend domain facilities for renaming network devices".
>> It says "naming/renaming", but you can assume "detecting".
>>
>>> I also checked which net_ids
Control: tags -1 + fixed-upstream confirmed patch
Hi all,
I also ran into this issue while trying to build src:linux 6.1.7-1
targeting bullseye-backports.
I can confirm that I was able to build the kernel packages successfully
using gcc-10/10.2.1-6, with only the following patch on top:
Hi,
On 1/13/23 22:45, Chuck Zmudzinski wrote:
> On 1/13/23 7:39 AM, Marek Marczykowski-Górecki wrote:
>> On Fri, Jan 13, 2023 at 12:58:29AM -0500, Chuck Zmudzinski wrote:
>>> On 1/11/2023 10:58 PM, Chuck Zmudzinski wrote:
>>>> On 1/9/23 12:55 PM, Hans van Kranenbu
Hi!
On 09/01/2023 18:44, Chuck Zmudzinski wrote:
> Control: tag -1 + moreinfo
>
> thanks
>
> On 1/9/23 8:09 AM, Hans van Kranenburg wrote:
>> Hi Chuck,
>>
>> On 1/8/23 23:18, Chuck Zmudzinski wrote:
>>> [...]
>>>
>>> The build fa
Hi Chuck,
On 1/8/23 23:18, Chuck Zmudzinski wrote:
> [...]
>
> The build failed:
>
>debian/rules override_dh_missing
> make[1]: Entering directory '/home/chuckz/sources-sid/xen/xen-4.17.0'
> dh_missing --list-missing
> dh_missing: warning: usr/lib/modules-load.d/xen.conf exists in
Hi :)
On 04/11/2022 22:51, Salvatore Bonaccorso wrote:
> Hi Hans
>
> On Fri, Nov 04, 2022 at 02:59:29PM +0100, Hans van Kranenburg wrote:
>> Aha!
>>
>> On 02/11/2022 21:53, Salvatore Bonaccorso wrote:
>>> Hi,
>>>
>>> On Wed, Nov 02, 2022 a
Aha!
On 02/11/2022 21:53, Salvatore Bonaccorso wrote:
> Hi,
>
> On Wed, Nov 02, 2022 at 08:02:26PM +0100, Hans van Kranenburg wrote:
>> Hi,
>>
>> On 10/19/22 21:55, Moritz Muehlenhoff wrote:
>>>>> For the latest set of Xen issues my estimate is that
Hi,
On 10/19/22 21:55, Moritz Muehlenhoff wrote:
>>> For the latest set of Xen issues my estimate is that we can postpone
>>> them until the next batch, they seem all of moderate/limited impact.
>>> But let me know if you think otherwise.
>>
>> I agree. Let's do them together with the new stuff
Hi,
On 18/10/2022 22:31, Moritz Muehlenhoff wrote:
> On Tue, Oct 18, 2022 at 02:17:32PM +0200, Hans van Kranenburg wrote:
>> Does explicitly opening a BTS bug mean that, like we use to call it,
>> "these CVEs warrant a DSA",
>
> No, in general we aim to file bu
Hi!
On 10/12/22 19:38, Moritz Mühlenhoff wrote:
> Source: xen
> X-Debbugs-CC: t...@security.debian.org
> Severity: important
> Tags: security
>
> Hi,
>
> The following vulnerabilities were published for xen.
>
> CVE-[...]
Thanks for the overview. The XAPI one indeed does not apply to src:xen.
Package: src:libtraceevent
Version: 1:1.1.2-1
Hi maintainer, :)
Linux commit fe4d0d5dde ("rtla/Makefile: Properly handle dependencies")
helps making the dependency on libtraceevent and libtracefs more
explicit, so that the users run into less weird problems on the go.
Linux 5.19 is in Debian
Hi!
On 9/28/22 00:55, Diederik de Haas wrote:
> On Wednesday, 28 September 2022 00:24:27 CEST Patrick wrote:
>> I just applied the patch
>> (xen.git-c3bd0b83ea5b7c0da6542687436042eeea1e7909.patch) to the xen
>> packages and can confirm that this fixes the problems. The xsave flags are
>>
Hi John,
On 8/2/22 19:50, John E. Krokes wrote:
> Package: xen-hypervisor-common
> Version: 4.14.5+24-g87d90d511c-1
> Severity: minor
> File: /etc/default/grub.d/xen.cfg
>
> Dear Maintainer,
>
> When invoked via grub-mkconfig, xen.cfg outputs this as its first line:
> Including Xen
with collectd,
libvirt and qemu maintainers to have their packages changed to remove
i386 related xen things.
So, I understand that we now can ask for removal of the leftover Xen
4.14 packages in i386, which will unblock the migration of Xen 4.16 to
testing.
Thanks,
Hans van Kranenburg
Debian
On 3/7/22 18:30, Chuck Zmudzinski wrote:
[...]
Thanks for adding all the info and researching this, Chuck!
Hans
I see the mail thread 'RFC: qemu and Xen ABI-unstable libs' on the
upstream xen-devel mailing list did not get referenced from this Debian
bug yet:
https://lists.xenproject.org/archives/html/xen-devel/2020-09/threads.html#01299
It contains a lot of info about the actual work that needs to be
tags 1005176 + moreinfo
thanks
Hi Elliott, :)
On 2/8/22 14:19, Elliott Mitchell wrote:
Package: src:xen Version: 4.16.0-1~exp1
I'm guilty of pulling in later Xen source and building it based on
the experimental 4.16 packaging. As such this may actually only be
an issue for a package version
(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:
n that we'll work based on your instructions.
* After sending this report and getting the confirmation from the BTS,
I'll send a reply with the upstream Xen development mailing list in Cc.
Thanks in advance,
Hans van Kranenburg
Hi Stéphane,
On 12/26/21 9:06 PM, Stéphane Glondu wrote:
> [...]
>
> Your package FTBFS with OCaml 4.13.1 with the following error:
>> [...]
>>57 | #define Some_val(v) Field(v,0)
>> |
>> In file included from /usr/lib/ocaml/caml/alloc.h:24,
>> from
Hi Aurelien,
On 8/24/21 10:58 PM, Aurelien Jarno wrote:
>
> Due to the removal of 32-bit PV in Linux kernel 5.9 and the removal of
> the "nosegneg" hwcap from glibc 2.32, the libc6-xen package is not build
> anymore by the glibc package. This is already the case in experimental,
> and will be
Hi all,
On 10/5/21 2:16 AM, Chuck Zmudzinski wrote:
> On 10/4/2021 1:51 PM, Diederik de Haas wrote:
>> On Monday, 4 October 2021 17:27:22 CEST Chuck Zmudzinski wrote:
>>> I can confirm these 4 fix the bug on my hardware.
>> \o/
>> Thanks for testing and reporting back :-)
>
> Thank you,
Hi!
On 10/19/21 5:44 AM, Chuck Zmudzinski wrote:
> On 5/10/2021 1:33 PM, Chuck Zmudzinski wrote:
>> [...] with buster and bullseye running as the Dom0, I can only get the
>> VGA/Passthrough feature to work with Windows Xen HVMs. I would expect both
>> Windows and Linux HVMs to work comparably
Hi Elliot and others,
Also including #994899 for once, since that's the bug number for the Xen
issue now.
On 9/26/21 5:27 AM, Elliott Mitchell wrote:
> On Tue, Sep 21, 2021 at 06:33:20AM -0400, Chuck Zmudzinski wrote:
>> I presume you are suggesting I try booting 4.19.181-1 on the
>> current
Hi spi, Salvatore,
On 8/5/21 1:58 PM, s...@gmxpro.de wrote:
>
> In preparation for the bug report for upstream I did some more
> investigation.
>
> The kernel panic also occurs without bonding interfaces but needs much
> more time to happen. With a bonding interface it happens within some
>
Hi!
On 9/30/21 12:45 AM, Andy Smith wrote:
> Hi Alex,
>
> On Thu, Sep 30, 2021 at 12:10:32AM +0200, Alexander Dahl wrote:
>> Am 22.09.21 um 20:54 schrieb Hans van Kranenburg:
>>> At this point I would really recommend to not wait for a fix to arrive
>>> which
Package: src:xen
Version: 4.14.3-1
Conversation in #debian-security, 25 Sep 2021
18:28 < adsb> hmmm, were the filename changes in
https://release.debian.org/proposed-updates/bullseye_diffs/xen_4.14.3-1~deb11u1_amd64.debdiff.html
expected?
>8
Files only in first set of .debs, found in
Hi!,
Please don't (accidentally) drop the debian bug email from the recipient
list. This information might also be useful for others later.
On 9/23/21 1:47 AM, H.-R. Oberhage wrote:
> Good evening Hans,
>
> On 22.09.2021 20:54, Hans van Kranenburg wrote:
>> Hi Ruediger,
>>
Hi Ruediger,
On 9/22/21 11:37 AM, H.-R. Oberhage wrote:
> Package: xen-system-amd64
> Version: 4.14.3-1~deb11u1
>
> After applying the buster security update to xen, my VM won't start
> any longer, complaining about a memory allocation error.
Can you confirm that this is a virtual machine that
Package: debian-security-support
Version: 2020.06.21~deb10u1
Severity: normal
Hi,
Upstream security support for Xen 4.11 has ended recently. This also
means that security support for Debian ended.
The complexity of the software involved does not really allow for anyone
else than the upstream
reassign 989656 src:xen 4.14.1+11-gb0b734a8b3-1
tags 989656 + upstream
thanks
Hi Phillip,
On 6/9/21 5:04 PM, Phillip Susi wrote:
> Package: xen-utils-common
> Version: 4.14.1+11-gb0b734a8b3-1
>
> My syslog has entries that look like this:
>
> Jun 09 10:54:26 hyper1 root[621]:
tags 989560 + moreinfo
thanks
Hi,
On 8/4/21 4:00 AM, Elliott Mitchell wrote:
> I rate #989560 as a grub-common bug, *not* a xen-hypervisor-common bug.
> As you've noticed, the problem is with the file /etc/grub.d/20_linux_xen,
> which is part of grub-common, not xen-hypervisor-common.
>
> A
ging this bug 'moreinfo' now, since it will depend on your
availability and abilities to work on it to have it advance.
Have fun,
Hans van Kranenburg
Oh,
On 4/16/21 11:44 AM, Hans van Kranenburg wrote:
> [...]
>
> I have the same issue here, it started at the moment I moved from the
> 4.19 kernel to 5.9, and now 5.10. For totally non-obvious reasons fans
> start blowing like crazy regularly for a few seconds. When observin
Hi,
On 4/15/21 10:51 PM, klak wrote:
> Package: linux-image-5.10.0-6-amd64
> Version: 5.10.28-1
>
> Hello Maintainer,
>
> every few minutes the fans turn to maximum for a few seconds. The CPU
> load is less than 1 %, but the fans are turning maximum. The problen
> starts with version
closer look at it somewhere in the next week.
Note that the bug fix will not reach Xen 4.11 (or our package) any more.
Regards,
Hans van Kranenburg
Hi,
On 1/25/21 8:08 PM, Salvatore Bonaccorso wrote:
> Source: xen
> Version: 4.14.0+88-g1d1d1f5391-2
> Severity: important
> Tags: security upstream
> X-Debbugs-Cc: car...@debian.org, Debian Security Team
>
>
> Hi
>
> For details see https://xenbits.xen.org/xsa/advisory-360.html .
>
> It
Package: src:xen
Version: 4.11.4+57-g41a822c392-1
Severity: normal
When removing the Xen packages, the grub menu entries to boot should be
removed.
Currently, thanks to a missing postfix of a postrm filename...
xen-hypervisor-V-F.postrm
vs.
xen-hypervisor-V-F.postrm.vsn-in
...this script is
Hi,
On 6/5/20 1:34 PM, Ansgar wrote:
> On Fri, 2020-06-05 at 12:09 +0200, Hans van Kranenburg wrote:
>>> Installing NEWS into xen*, but not libxen* probably still reaches all
>>> relevant users.
>>
>> Yes, that makes sense.
>>
>> OTOH, what if there w
Alexander Dahl wrote:
>> On Tue, Nov 24, 2020 at 05:41:42PM +0100, Hans van Kranenburg wrote:
>>> [...]
>>>
>>> Any help with testing is appreciated, especially since there are so many
>>> combinations of hardware, different architectures and use cases (using
&g
Hi,
On 11/29/20 8:50 PM, Salvatore Bonaccorso wrote:
> Source: xen
> Version: 4.14.0+80-gd101b417b7-1
> Severity: grave
> Tags: security upstream
> Justification: user security hole
> X-Debbugs-Cc: car...@debian.org, Debian Security Team
>
>
> Hi,
>
> The following vulnerability was published
tags 942611 + pending
thanks
Hi Diederik,
On 10/19/19 2:19 AM, Diederik de Haas wrote:
> Package: xen-doc
> Version: 4.11.1+92-g6c33308a8d-2+b1
> Severity: normal
>
> file:///usr/share/doc/xen/html/index.html contains a link to
> file:///usr/share/doc/xen/html/misc/vtd.txt (VT-d HOWTO), but
tags 963607 + moreinfo
thanks
Hi Alex,
On 7/2/20 9:26 AM, debianb...@red-sand.com wrote:
>
> [...]
>
> I am about to purchase a new SAS HBA card to test as we have a number of
> these servers with Areca cards that I imagine will have the same problem
> on Xen 4.11. I am leaning towards mpt3
tags 944247 + moreinfo
severity 944247 normal
thanks
Hi Mario,
On 11/6/19 4:46 PM, mario wrote:
> Source: xen
> Severity: important
>
> Dear Maintainer,
>
> we have updated our server from debian oldstable (which unfortunately wasn't
> running stable after the last update, bug reported) to
reassign 955994 src:xen
tags 955994 + pending
thanks
Hi Samuel,
On 4/5/20 9:14 PM, Samuel Thibault wrote:
> Package: xen-utils-common
> Version: 4.11.3+24-g14b62ab3e5-1
> Severity: normal
> Tags: patch
>
> Hello,
>
> I was having issues with starting domains with vif-nat:
>
> ♭ xl cr -c
Hi,
On 9/2/19 5:18 AM, Elliott Mitchell wrote:
> Package: xen-hypervisor-4.8-amd64
> Version: 4.8.5+shim4.10.2+xsa282-1+deb9u11
>
> Trying to create a HVM domain with memory != maxmem reliably crashes
> Debian's build of Xen 4.8. This may be a nonsensical configuration, but
> it still shouldn't
Hi,
This bug was reported against Xen 4.8 (which is out of support and out
of security support now) and there has not been any activity for over
almost two years.
I'm cleaning up old open bugs, and I will close the issue now.
If you found a solution to this problem, please let us know, so the
Hi Mario,
On 8/14/19 11:00 PM, mario wrote:
> Package: xen-system-amd64
> Version: 4.8.5+shim4.10.2+xsa282-1+deb9u11
> Severity: important
>
> hello everyone,
>
> we have a vm with kernel 4.9.0-5-amd64 running dabian oldstable
> if we run an "npm run build" on one of the virtual machines, the
On 11/20/20 8:02 PM, Hans van Kranenburg wrote:
> So,
>
> On 9/21/20 4:16 PM, Hans van Kranenburg wrote:
>> [...]
>>
> [...]
> >8
>
> dh_install: warning: Cannot find (any matches for)
> "usr/lib/debug/usr/lib/xen-*/boot/*" (tried in .
On 11/21/20 5:40 AM, Elliott Mitchell wrote:
> On Fri, Nov 20, 2020 at 08:02:26PM +0100, Hans van Kranenburg wrote:
>> So,
>>
>> On 9/21/20 4:16 PM, Hans van Kranenburg wrote:
>>> [...]
>>>
>>> gcc-Wl,-z,relro -Wl,-z,now -pthread -Wl,-soname
&
Hi!
On 11/18/20 6:45 PM, Ian Jackson wrote:
> Hans van Kranenburg writes ("Bug#975062: Python 3 (pygrub) in 4.14 packages"):
>> So, apparently there are cases in which pygrub 'works' and in which it
>> does not, and apparently using pygrub with "amd64 kernel and
On 11/18/20 9:39 PM, Ian Jackson wrote:
> It seems I was distracted when I wrote this mail.
>
> Ian Jackson writes ("Re: Bug#975062: Python 3 (pygrub) in 4.14 packages"):
>> The problem with pygrub with 32-bit userland is as follows:
>>
>> * Xen has to be 64-bit since there is no 64-bit Xen.
>
Package: src:xen
Version: 4.14.0-1~exp1
Control: submitter -1 ehem+deb...@m5p.com
X-Debbugs-CC: ehem+deb...@m5p.com, ijack...@chiark.greenend.org.uk
Hi, I think this should be in a bug report in the BTS to track it in a
better way.
8< Forwarded Message 8<
Subject: [Pkg-xen-devel]
On 9/23/20 4:59 PM, Julien Grall wrote:
> X-Debbugs-CC: i...@xenproject.org
> X-Debbugs-CC: h...@knorrie.org
> Package: gcc-10
> Version: 10.2.0-9
> Severity: important
>
> Dear Maintainer,
>
> There was an FTBFS for Xen when building using GCC 10 on armhf (see
> bug #9689645 [1]).
FYI [1]
notfixed 961511 xen/4.14.0-1~exp1
thanks
Right... so in the end I made an off-by-one error while rebasing and
totally lost that commit. It's not actually in 4.14.0-1~exp1 now. That's
bad.
On 9/21/20 3:50 AM, Elliott Mitchell wrote:
> This is fun. Actually isn't too difficult to trigger, simply
notfixed -1 xen/4.14.0-1~exp1
reopen
found -1 xen/4.14.0-1~exp1
thanks
Hi,
On 9/4/20 1:55 PM, Hans van Kranenburg wrote:
>
> On 8/24/20 7:03 PM, Gianfranco Costamagna wrote:
>> Source: xen
>> Version: 4.11.4+24-gddaaccbbab-1
>> Severity: serious
>>
>> He
Hi again,
On 5/1/19 12:55 AM, Elliott Mitchell wrote:
> On Mon, Apr 22, 2019 at 04:02:28PM +0200, Hans van Kranenburg wrote:
>> On 4/22/19 1:10 AM, Elliott Mitchell wrote:
>>> There is plenty of free memory for creating additional VMs (perhaps too
>>> much,
Hi!
On 8/16/20 3:36 PM, Elrond wrote:
> Package: btrfs-heatmap
> Version: 8-1
> Severity: wishlist
> User: multiarch-de...@lists.alioth.debian.org
> Usertags: multiarch
>
> Hi,
>
> btrfs-heatmap currently depends on just python3.
> As btrfs-heatmap is Architecture=all, it probably
> should
tag -1 + pending
thanks
On 9/7/20 12:40 PM, Ian Jackson wrote:
> ~Hans van Kranenburg writes ("[PATCH] d/xen-utils-common.xen.init: disable
> oom killer for xenstored"):
>> In case of oom killer terminating some process, we'd rather not see
>> xenstored go. Xenstor
to the user report, it happened.
Closes: #961511
Suggested-by: Samuel Thibault
Signed-off-by: Hans van Kranenburg
---
Cc: Ian Jackson
---
This is in my knorrie/4.14-extra branch now. I think we should do this.
---
debian/xen-utils-common.xen.init | 3 ++-
1 file changed, 2 insertions(+), 1
Hi,
On 5/25/20 3:18 PM, Samuel Thibault wrote:
> Samuel Thibault, le lun. 25 mai 2020 15:11:44 +0200, a ecrit:
>> I'm currently using a hack such as
>>
>> for i in $(pgrep xenconsoled) ; do
>> echo -1000 > /proc/$i/oom_score_adj
>> done
>>
>> in /etc/init.d/xen,
Hi Gianfranco,
On 8/24/20 7:03 PM, Gianfranco Costamagna wrote:
> Source: xen
> Version: 4.11.4+24-gddaaccbbab-1
> Severity: serious
>
> Hello, looks like xen is FTBFS because of some bd-uninstallable python
> package and a gcc-10 related build failure.
Yes. Thanks for the report.
Currently
Hi,
On Wed, 15 Jul 2020 20:52:40 -0700 Sarah Newman wrote:
> On 7/7/20 8:13 PM, Ben Hutchings wrote:
> > Control: reassign -1 src:linux
> > Control: tag -1 moreinfo
> >
> > On Tue, 2020-07-07 at 17:30 -0700, Sarah Newman wrote:
> >> Package: linux-signed-amd64
> >> Version: 4.19.0-9-amd64
> >>
Hi Elliott,
On 7/18/20 5:53 AM, Elliott Mitchell wrote:
> Package: src:xen
> Version: 4.13
> Tags: patch
>
> I've been playing try to get Xen 4.13 to cross-build for ARM. In the
> process I've been running into bunches of problems, so here are fixes.
Can you:
* add a 'why' line to the commit
However,
On 7/13/20 4:19 PM, Hans van Kranenburg wrote:
> (Adding more To:; Note that mailing the bug number does not make it end
> up at the submitter automatically, only the package maintainer).
>
> Hi Christian,
>
> thanks for the hints!
>
> On Mon, 13 Jul 2020
(Adding more To:; Note that mailing the bug number does not make it end
up at the submitter automatically, only the package maintainer).
Hi Christian,
thanks for the hints!
On Mon, 13 Jul 2020 09:01:18 +0200 Christian Ehrhardt
wrote:
> Hi,
> I was seeing the bug updates flying by and just
Hi,
On 7/8/20 9:35 AM, Moritz Muehlenhoff wrote:
> On Tue, Jul 07, 2020 at 10:56:18PM +0200, Hans van Kranenburg wrote:
>> Additional To: t...@security.debian.org
>>
>> Hi Security team,
>>
>> After our last security update, which was
>> 4.11.3
On 7/7/20 9:51 PM, Adam D. Barratt wrote:
> Control: tags -1 + moreinfo
>
> On Tue, 2020-07-07 at 21:16 +0200, Hans van Kranenburg wrote:
>> I'd like to update the xen packages in buster to
>> 4.11.4+24-gddaaccbbab-1~deb10u1 for the 10.5 point release. This is
>>
/10baa2d48db43a5ff675bddf5482717f60fb748a
Testing and code review can also be seen in:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932759#38
So, since 4.11.4-1 is in unstable already, these changes have been out
there for weeks now. We have not seen any user report about any regression.
Thanks,
Hans van Kranenburg
Hi,
On 6/25/20 1:44 PM, Alex Sanderson wrote:
>
> Hi Hans,
>
> Thank you for your assistance with this. I hesitated to log this with
> xen-dev but thought I should wait for a response here first.
>
>
> On 25/06/2020 01:30, Hans van Kranenburg wrote:
>> Hi A
Hi Alex,
On 6/24/20 12:31 PM, Alex Sanderson wrote:
> Package: xen-hypervisor-4.11-amd64
> Version: 4.11.3+24-g14b62ab3e5-1~deb10u1
> Severity: important
>
> Dear Maintainer,
>
> After updating to Buster and Xen 4.11 our machine no longer boots the Xen
> kernel. The default kernel
Hi Ansgar,
On 6/5/20 11:57 AM, Ansgar wrote:
> Source: xen
> Version: 4.11.4-1
> Severity: minor
> File: /usr/share/doc/libxenmisc4.11/NEWS.Debian.gz
>
> Please consider to not install debian/NEWS into runtime library
> packages. They get pulled into systems that do not run Xen at all in
>
Hi,
On 5/27/20 7:39 PM, Debian Bug Tracking System wrote:
> Your message dated Wed, 27 May 2020 17:36:26 +
> with message-id
> and subject line Bug#932759: fixed in xen 4.11.4-1
> has caused the Debian Bug report #932759,
> regarding After upgrade from stretch to buster, removal of obsolete
Hi,
On 5/26/20 12:44 PM, Ian Jackson wrote:
> Hans van Kranenburg writes ("[PATCH 2/2] debian/rules: --no-start for xen
> dh_installinit"):
>> When debugging the xen-utils postinst/prerm to find the cause of the
>> mysteriously disappearing xenconsoled processes,
actively support doing
interesting things inside a domU with these packages however.
Hans van Kranenburg (2):
xen init/maint scripts: Do nothing if running for wrong Xen package
debian/rules: --no-start for xen dh_installinit
debian/rules | 2 +-
debian/xen-utils
by dh_installdeb into the postinst and prerm during package build time.
We only want to call the script from xen-utils-V, so disable this
behavior by using --no-start
Closes: #932759 (2/2)
Signed-off-by: Hans van Kranenburg
---
debian/rules | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
en version.
Signed-off-by: Hans van Kranenburg
Closes: #932759 (1/2)
Fixes: cc85504103 "xen init script: Do nothing if running for wrong Xen package"
---
debian/xen-utils-V.postinst.vsn-in | 10 +-
debian/xen-utils-V.prerm.vsn-in| 10 +-
debian/xen-utils-co
Hi Guillem,
On 9/6/19 12:55 PM, Guillem Jover wrote:
> [...]
>
> During the debhelper recommendation thread there was a mail from Ian
> pointing out to the xen debian/rules file, I took a look and noticed
> the following. :)
>
> The debian/rules file [...]
Thanks for the report! The fixes will
On 5/9/20 9:57 PM, Moritz Mühlenhoff wrote:
> On Sat, May 09, 2020 at 02:36:24AM +0200, Thomas Goirand wrote:
>> On 5/8/20 9:35 PM, Moritz Mühlenhoff wrote:
>>> On Fri, Aug 30, 2019 at 07:45:40AM +, Matthias Klose wrote:
Package: src:python-pyxenstore
Version: 0.0.2-1
Severity:
more inspection of the history of that file is necessary to
collect the pieces for a proper fix together.
I can help testing a new package if you want.
Thanks,
Hans van Kranenburg
1.x/commit/1615689e259bfd67e43cf7711948abc23f998ca9
Thanks,
Hans van Kranenburg
Hi,
Friendly ping for this issue. Today I ran into the situation that after
getting DM status to be able to help with the security updates for a
specific package (Xen), I found out I was not able to actually make this
happen, since I still need to send the result of my package build to
someone
On 1/7/20 11:34 PM, Hans van Kranenburg wrote:
> [...]
>
> Today I have finally been working on this. The result is that I at least
> have a new (WIP) version for buster. I'm running it on a dom0 right now
> and did smoke testing, live migrate, restarting domUs etc. It j
hangelog entry.
I also added a commit to put in the CVE numbers in previous changelog
entries:
https://salsa.debian.org/xen-team/debian-xen/commit/0ee295f5caf6178f64febeb976d7ea968e44a191
Is this ok/wanted/great/what-you-like? Because, regularly, the numbers
are not available yet when we push out the update.
Thanks,
Hans van Kranenburg
Hi,
On 1/3/20 5:42 PM, Martin Maney wrote:
>
> [...]
>
> Yes, the shutdown hang is a different issue, but I'm going to hope that
> the real systemd units mentioned in this bug will fix my problem, too.
What you could do already now is try testing those scripts, just
shutting down and starting
that case, try triggering the problem by
generate the same workload that's now coming from the domUs.
Curious to hear what happens,
Thanks,
Hans van Kranenburg
On 7/18/19 1:30 AM, Hans van Kranenburg wrote:
> Hi,
>
> On 10/23/18 7:34 PM, Ian Jackson wrote:
>> Control: retitle -1 max grant frames problem (domu freeze with
>> linux-image-4.9.0-4-amd64)
>> Control: severity -1 important
>> Control: reassign -1 src:xen
oblems might or might not be specific
to Debian, I don't know.
I'm available to facilitate the process, for example by creating new
packages with a specific patch to test, but unfortunately I don't have
spare hardware and time to try reproduce the problems myself and dig
deep into it.
Thanks,
Hans van Kranenburg
On 7/23/19 4:07 PM, niek wrote:
> [...]
> 2019-07-21 07:38:40 status installed xen-utils-4.8:amd64
> 4.8.5+shim4.10.2+xsa282-1+deb9u11
> 2019-07-21 07:38:40 remove xen-utils-4.8:amd64
> 4.8.5+shim4.10.2+xsa282-1+deb9u11
> 2019-07-21 07:38:40 status half-configured xen-utils-4.8:amd64
>
Hi niek,
Thanks for the report!
On 7/22/19 8:32 PM, niek wrote:
> Package: xen-hypervisor-4.11-amd64
> Version: 4.11.1+92-g6c33308a8d-2
>
> What happened:
> - upgraded Debian Xen Dom0 from stretch to buster and rebooted, as
> described in
>
Hi,
On 10/23/18 7:34 PM, Ian Jackson wrote:
> Control: retitle -1 max grant frames problem (domu freeze with
> linux-image-4.9.0-4-amd64)
> Control: severity -1 important
> Control: reassign -1 src:xen 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9
my last comment in this bts bug was about:
Next step would be to follow Rogers
instructions, and provide config dumps, serial console output etc...
We're certainly available to include changes / etc to fix things, given
proper information / testing reports from the user. But, the user has to
actively help to make that happen.
Control: tags -1 - moreinfo
Hi Paul,
On 6/21/19 10:02 PM, Paul Gevers wrote:
> Control: tags -1 moreinfo
>
> Hi Hans,
>
> On 20-06-2019 21:14, Hans van Kranenburg wrote:
>> * Note that the fixes for XSA-297 will only have effect when also loading
>> updated
sor command line
documentation about the 'ucode=scan' option.
* Fixes for XSA-295 "Unlimited Arm Atomics Operations" will be added
in the
next upload.
-- Hans van Kranenburg Tue, 18 Jun 2019 09:50:19 +0200
>8
We prefer to keep releasing from the upstream stable
On 6/19/19 4:43 PM, Wiebe Cazemier wrote:
> This is an update to the unstable release. What is one running Debian
> stable (9), with Xen Hypervisor 4.8, to do?
This is not meant as a middle finger to users of stable.
All of the bug numbers will be closed twice, also by the 4.8 upload,
which also
1 - 100 of 364 matches
Mail list logo
