it to
the Debian packages archive, either in main, contrib, or non-free as
appropriate. I am not including any debdiff patches here because they
are too large.
Chuck Zmudzinski
package.
Thank you for your consideration of my question.
Sincerely,
Chuck Zmudzinski
package.
Thank you for your consideration of my question.
Sincerely,
Chuck Zmudzinski
Package: qemu-system-x86
Version: 6.0+dfsg-1~exp0 and 5.2+dfsg-10
Severity: normal
Tags: patch upstream
Dear Maintainer,
I find that when using qemu with a Windows Xen HVM DomU and also passing
through the Intel integrated graphics device (IGD) to the Windows Xen HVM DomU,
it is much more
Package: src:linux
Version: 5.10.28-1
Severity: normal
Tags: upstream
Dear Maintainer,
I have been using Xen's PCI and VGA passthrough feature since wheezy and jessie
were the stable versions, and back then both Windows HVMs and Linux HVMs would
function with the Intel Integrated Graphics
is for.
Chuck Zmudzinski
drivers so they are compatible with the
modern version? Does the Xen virtual keyboard need to be
managed by udev? Is there a simple way to disable incompatible
devices so udev ignores them?
Chuck Zmudzinski
On 8/25/2021 12:45 PM, Chuck Zmudzinski wrote:
On 8/24/2021 7:12 PM, Ben Hutchings wrote:
On Tue, Aug 24, 2021 at 03:27:19PM -0400, Phillip Susi wrote:
Ben Hutchings writes:
I think a proper fix would be one of:
a. If the Xen virtual keyboard driver is advertising capabilities it
��ï
On 8/24/2021 7:12 PM, Ben Hutchings wrote:
Text-based sysfs attributes are limited to a page, but udev receives
uevents through netlink, not sysfs.
The current limit on the environment of a uevent appears to be 2 KB
(UEVENT_BUFFER_SIZE defined in ). That seems like it
*might* be easier to
On 8/24/2021 1:12 PM, Ben Hutchings wrote:
On Tue, 2021-08-24 at 10:56 -0400, Chuck Zmudzinski wrote:
On 5/24/2021 3:30 AM, Michael Biebl wrote:
Hi Phillip
Am 24.05.2021 um 06:19 schrieb Cyril Brulebois:
trigger to cold plug all devices. Both scripts are set -e. The Xen
Virtual Keyboard
On 8/25/2021 4:16 PM, Phillip Susi wrote:
Chuck Zmudzinski writes:
If it doesn't work, I am also willing to try approach a by patching
the Linux kernel xen-kbdfront driver by removing the for loops that
advertise those 654 keys. I tend to agree with Philip that this is
totally unnecessary
On 8/25/2021 10:54 AM, Ben Hutchings wrote:
On Tue, 2021-08-24 at 15:19 -0400, Chuck Zmudzinski wrote:
On 8/24/2021 1:12 PM, Ben Hutchings wrote:
[...]
I think a proper fix would be one of:
a. If the Xen virtual keyboard driver is advertising capabilities it
doesn't have, stop it doing
On 8/24/2021 7:12 PM, Ben Hutchings wrote:
On Tue, Aug 24, 2021 at 03:27:19PM -0400, Phillip Susi wrote:
Ben Hutchings writes:
I think a proper fix would be one of:
a. If the Xen virtual keyboard driver is advertising capabilities it
doesn't have, stop it doing that.
b. Change the
On 9/19/2021 10:56 AM, Elliott Mitchell wrote:
On Sun, Sep 19, 2021 at 01:05:56AM -0400, Chuck Zmudzinski wrote:
On Sat, 11 Sep 2021 13:29:12 +0200 Salvatore Bonaccorso
wrote:
>
> On Fri, Sep 10, 2021 at 06:47:12PM -0700, Elliott Mitchell wrote:
> > An experiment lead to
On 9/19/2021 1:05 AM, Chuck Zmudzinski wrote:
Hello Elliott and Salvatore,
I noticed this bug on bullseye ever since I have been
running bullseye as a dom0, but my testing indicates
there is no problem with src:linux but the problem
appeared in src:xen with the 4.14 version of xen on
bullseye
a bug in src:xen.
I also would inquire with the Debian Xen Team about why they
are backporting patches from the upstream xen unstable
branch into Debian's 4.14 package that is currently shipping
on Debian stable (bullseye). IMHO, the aforementioned
patches that are not in the stable 4.14 branch upstream
sh
On 9/19/2021 1:29 PM, Elliott Mitchell wrote:
On Sun, Sep 19, 2021 at 01:05:56AM -0400, Chuck Zmudzinski wrote:
I noticed this bug on bullseye ever since I have been
running bullseye as a dom0, but my testing indicates
there is no problem with src:linux but the problem
appeared in src:xen
On 9/19/2021 4:53 PM, Elliott Mitchell wrote:
On Sun, Sep 19, 2021 at 03:54:01PM -0400, Chuck Zmudzinski wrote:
On 9/19/2021 1:29 PM, Elliott Mitchell wrote:
Have you tried memory ballooning with PVH or HVM domains?
That combination has been reliably crashing Xen for me for a while
On 9/19/2021 9:30 PM, Chuck Zmudzinski wrote:
On 9/19/2021 4:53 PM, Elliott Mitchell wrote:
On Sun, Sep 19, 2021 at 03:54:01PM -0400, Chuck Zmudzinski wrote:
On 9/19/2021 1:29 PM, Elliott Mitchell wrote:
Have you tried memory ballooning with PVH or HVM domains?
That combination has been
On 8/24/2021 7:12 PM, Ben Hutchings wrote:
On Tue, Aug 24, 2021 at 03:27:19PM -0400, Phillip Susi wrote:
Ben Hutchings writes:
I think a proper fix would be one of:
a. If the Xen virtual keyboard driver is advertising capabilities it
doesn't have, stop it doing that.
b. Change the
discussing the matter with
me in a private email.
Cheers,
Chuck Zmudzinski
On 9/23/2021 5:50 PM, Diederik de Haas wrote:
On donderdag 23 september 2021 21:54:49 CEST Chuck Zmudzinski wrote:
While I did respond point by point privately to the author
Don't do that. Any discussion relevant to the bug should be sent to the bug
itself so that everyone has all the relevant
On 5/10/2021 1:33 PM, Chuck Zmudzinski wrote:
Package: src:linux
Version: 5.10.28-1
Severity: normal
Tags: upstream
Dear Maintainer,
I have been using Xen's PCI and VGA passthrough feature since wheezy and jessie
were the stable versions, and back then both Windows HVMs and Linux HVMs would
On 9/25/2021 11:27 PM, Elliott Mitchell wrote:
Unfortunately I was too quick at installing the rebuilt 4.14.3-1 and I
missed trying the vanilla Debian 4.14.2+25-gb6a8c4f72d-2 with
Linux 4.19.181-1. I believe this combination would have hung during
reboot.
In light of what I discovered
On 9/26/2021 8:46 AM, Chuck Zmudzinski wrote:
On 9/25/2021 11:27 PM, Elliott Mitchell wrote:
Unfortunately I was too quick at installing the rebuilt 4.14.3-1 and I
missed trying the vanilla Debian 4.14.2+25-gb6a8c4f72d-2 with
Linux 4.19.181-1. I believe this combination would have hung during
Added tag upstream. Explanation is in discussion at
related bug #991967 here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991967#169
and here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991967#174
Briefly, since we are currently shipping a fork of Xen-4.14
on our unstable,
This corrects typos - I referenced the wrong bug # in
a few places.
On 9/25/2021 11:27 PM, Elliott Mitchell wrote:
Since the purpose of the bug reports is to find and diagnose bugs, I did
a bit of experimentation and made some observations.
I checked out the Debian Xen source via git. I got
please see the
messages in #994899:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994899
and in #991967:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991967
All the best,
Chuck Zmudzinski
diff -Nru xen-4.14.3/debian/changelog xen-4.14.3/debian/changelog
--- xen-4.14.3/debian/changelog 2021-09-13
Control: severity -1 normal
After reading some other bug reports, I now think this
bug's severity should be normal, not important.
Regards,
Chuck
On 9/30/2021 2:57 PM, Paul Gevers wrote:
Hi Chuck,
On 30-09-2021 18:15, Chuck Zmudzinski wrote:
... the debdiff I uploaded to BTS has UNRELEASED
rather than bullseye for the distribution field of the changelog,
and the new target version is ...deb11u1.1 instead of deb11u2.
That is how dch
On 9/30/2021 2:57 PM, Paul Gevers wrote:
Hi Chuck,
On 30-09-2021 18:15, Chuck Zmudzinski wrote:
... the debdiff I uploaded to BTS has UNRELEASED
rather than bullseye for the distribution field of the changelog,
and the new target version is ...deb11u1.1 instead of deb11u2.
That is how dch
On 9/29/2021 7:26 PM, Chuck Zmudzinski wrote:
Ordinarily, as I understand the process, a bug in the
stable version is first fixed in the unstable release
and then the fix is migrated (backported) to the
stable release. But it appears to me a fix in the
unstable release will not be forthcoming
On 9/29/2021 7:26 PM, Chuck Zmudzinski wrote:
Special instructions for applying the debdiff:
Please note that an updated debdiff has been provided
to target the correct distribution and use the correct
version number for the updated package at the following
link:
https://bugs.debian.org/cgi
On 9/20/21 12:27 AM, Elliott Mitchell wrote:
On Sun, Sep 19, 2021 at 01:05:56AM -0400, Chuck Zmudzinski wrote:
I suspect the following patch is the culprit for problems
shutting down on the amd64 architecture:
0030-xen-acpi-Rework-acpi_os_map_memory-and-acpi_os_unmap.patch
This patch does
On 9/20/21 1:43 PM, Chuck Zmudzinski wrote:
On 9/20/21 12:27 AM, Elliott Mitchell wrote:
On Sun, Sep 19, 2021 at 01:05:56AM -0400, Chuck Zmudzinski wrote:
I suspect the following patch is the culprit for problems
shutting down on the amd64 architecture:
0030-xen-acpi-Rework
On 9/20/21 7:39 PM, Diederik de Haas wrote:
On dinsdag 21 september 2021 01:15:15 CEST Elliott Mitchell wrote:
Merely having the path is a sufficiently strong indicator for me to
simply wave it past. I though would suggest Debian should instead
cherry-pick commit
On 9/20/21 6:29 PM, Chuck Zmudzinski wrote:
On 9/20/21 1:43 PM, Chuck Zmudzinski wrote:
On 9/20/21 12:27 AM, Elliott Mitchell wrote:
On Sun, Sep 19, 2021 at 01:05:56AM -0400, Chuck Zmudzinski wrote:
I suspect the following patch is the culprit for problems
shutting down on the amd64
On 9/20/21 12:27 AM, Elliott Mitchell wrote:
On Sun, Sep 19, 2021 at 01:05:56AM -0400, Chuck Zmudzinski wrote:
xen hypervisor version: 4.14.2+25-gb6a8c4f72d-2, amd64
linux kernel version: 5.10.46-4 (the current amd64 kernel
for bullseye)
Boot system: EFI, not using secure boot, booting xen
On 9/20/21 10:37 PM, Elliott Mitchell wrote:
On Mon, Sep 20, 2021 at 10:23:39PM -0400, Chuck Zmudzinski wrote:
On 9/20/21 7:39 PM, Diederik de Haas wrote:
On dinsdag 21 september 2021 01:15:15 CEST Elliott Mitchell wrote:
Merely having the path is a sufficiently strong indicator for me
On 9/20/21 10:12 PM, Chuck Zmudzinski wrote:
On 9/20/21 6:29 PM, Chuck Zmudzinski wrote:
On 9/20/21 1:43 PM, Chuck Zmudzinski wrote:
On 9/20/21 12:27 AM, Elliott Mitchell wrote:
On Sun, Sep 19, 2021 at 01:05:56AM -0400, Chuck Zmudzinski wrote:
I suspect the following patch is the culprit
.
Respectfully,
Chuck Zmudzinski
Regards,
Diederik
release and
eventully commits them to their 4.14 branch and subsequent upstream
point releases, then I would also accept them as appropriate for the Debian
package of the upstream stable 4.14 version of Xen that targets the stable
version, currently bullseye.
Regards,
Chuck Zmudzinski
What you
The original submitter has proposed a fix (see messages #30 and #35).
Another contributor to this report has indicated the package maintainer
does not endorse the submitter of the bug's proposed fix and is working
on another fix (see messages #40 and #65). The original submitter of the
bug
On 10/3/2021 11:21 AM, Chuck Zmudzinski wrote:
On 10/1/2021 5:48 AM, Diederik de Haas wrote:
We've already identified a possible fix, which I can point to if so
desired,
I think the fix referred to is here:
https://salsa.debian.org/xen-team/debian-xen/-/tree/knorrie/for-diederik-3-fixes
and
its future stable point releases 4.14.x.
IMO, the debdiff attached to message #30:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995341#30
is a better suited fix more in accordance with the stability/security
requirements of a typical Debian stable release.
Regards,
Chuck Zmudzinski
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 :-)
Cheers,
Diederik
Thank you, Diederik, for your good work finding the commits
On 10/4/2021 6:57 AM, Diederik de Haas wrote:
On Monday, 4 October 2021 11:46:54 CEST Hans van Kranenburg wrote:
The 4th one is not explicitly tagged with Fixes: 1c4aa69ca1e1, but I
agree with Diederik that we should keep them all together.
Context: Those 4 are part of 1 patch-set posted here:
As discussed in message #91, the submitter of this bug accepts the
package maintainer's fix which will close this bug.
atches into a separate directory
+ * debian/rules - disable RPI4 patches on amd64|i386 to fix #994899
+ * debian/control - add Build Dependency quilt
+
+ -- Chuck Zmudzinski Sun, 26 Sep 2021 22:23:21 -0400
+
xen (4.14.3-1~deb11u1) bullseye-security; urgency=medium
* Rebuild for bullseye-security
diff -N
A patch has been uploaded (message #55). For more information, see
message #34.
On 9/23/2021 12:49 PM, Diederik de Haas wrote:
Control: tag -1 -newcomer
Control: tag -1 -upstream
On woensdag 22 september 2021 21:50:16 CEST Chuck Zmudzinski wrote:
Finally, I tag the bug newcomer simply because there is a known solution but
That's what the 'patch' tag is for. 'newcomer
atches on amd64|i386 to fix #994899
+ * debian/control - add Build Dependency quilt
+
+ -- Chuck Zmudzinski Mon, 27 Sep 2021 11:51:04 -0400
+
xen (4.14.3-1~deb11u1) bullseye-security; urgency=medium
* Rebuild for bullseye-security
diff -Nru xen-4.14.3/debian/control xen-4.14.3/debian/c
A patch has been uploaded (see message #67). For more information, see
message #34.
to
the Debian developers to decide. Instead, I will select
this message to be a summary of the bug.
Happy computing on Debian,
Chuck Zmudzinski
On 9/25/2021 11:27 PM, Elliott Mitchell wrote:
The second we seem to have a fix. The only question is how many patches
to cherry pick? bc141e8ca562 is non-urgent as it is merely superficial
and not needed for functionality.
5a4087004d1a is a workaround for Linux kernel breakage, but how
as proposed here.
Regards,
Chuck Zmudzinski
*** Reporter, please consider answering these questions, where
appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What
On 9/21/21 7:22 AM, Fr. Chuck Zmudzinski, C.P.M. wrote:
On Sat, 7 Aug 2021 08:40:14 +0200 Salvatore Bonaccorso
wrote:
> Control: tags -1 + moreinfo
>
> Hi,
>
> On Fri, Aug 06, 2021 at 11:50:54AM -0700, Elliott Mitchell wrote:
> > Package: src:linux
> > Vers
On 9/20/2021 10:37 PM, Elliott Mitchell wrote:
On Mon, Sep 20, 2021 at 10:23:39PM -0400, Chuck Zmudzinski wrote:
On 9/20/21 7:39 PM, Diederik de Haas wrote:
On dinsdag 21 september 2021 01:15:15 CEST Elliott Mitchell wrote:
Merely having the path is a sufficiently strong indicator for me
On 9/21/2021 9:13 AM, Chuck Zmudzinski wrote:
On 9/20/2021 10:37 PM, Elliott Mitchell wrote:
On Mon, Sep 20, 2021 at 10:23:39PM -0400, Chuck Zmudzinski wrote:
On 9/20/21 7:39 PM, Diederik de Haas wrote:
On dinsdag 21 september 2021 01:15:15 CEST Elliott Mitchell wrote:
Merely having the path
On 8/26/2021 8:01 AM, Chuck Zmudzinski wrote:
On 8/24/2021 7:12 PM, Ben Hutchings wrote:
The current limit on the environment of a uevent appears to be 2 KB
(UEVENT_BUFFER_SIZE defined in ).� That seems like it
*might* be easier to change, so long as user-space doesn't have a
similar limit
On 8/24/2021 7:12 PM, Ben Hutchings wrote:
The current limit on the environment of a uevent appears to be 2 KB
(UEVENT_BUFFER_SIZE defined in ). That seems like it
*might* be easier to change, so long as user-space doesn't have a
similar limit.
I looked into systemd/udev, and it seems to use
s on differences in the BIOS or EFI, or
maybe systemd vs. sysv.
I share this result in case it is of help to you.
Regards,
Chuck Zmudzinski
On 10/26/2021 10:06 AM, Chuck Zmudzinski wrote:
On 10/25/2021 4:45 PM, Chuck Zmudzinski wrote:
On 10/23/2021 11:11 AM, Hans van Kranenburg wrote:
Hi!
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
On 10/26/2021 10:06 AM, Chuck Zmudzinski wrote:
On 10/25/2021 4:45 PM, Chuck Zmudzinski wrote:
On 10/23/2021 11:11 AM, Hans van Kranenburg wrote:
Hi!
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
On 10/23/2021 11:11 AM, Hans van Kranenburg wrote:
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
On 10/23/2021 11:11 AM, Hans van Kranenburg wrote:
Can you share the domU config file?
Yes, here it is:
builder = 'hvm'
memory = '3072'
vcpus = '4'
device_model_version = 'qemu-xen'
# device_model_version = 'qemu-xen-traditional'
# This is now bullseye
disk =
Package: general
Severity: normal
Dear Maintainer,
It is a bug that Debian considers the DSC so important, yet,
the concept of a contract is totally meaningless outside of
the context of a legal system where the obligations and rights
that arise from the terms of the contract can be enforced.
On 1/11/2023 10:58 PM, Chuck Zmudzinski wrote:
> On 1/9/23 12:55 PM, Hans van Kranenburg wrote:
> > Hi!
> >
> > On 09/01/2023 18:44, Chuck Zmudzinski wrote:
> >> Control: tag -1 + moreinfo
> >>
> >> thanks
> >>
> >> On 1/9/23 8:
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 failed:
>>
>>debian/rules override_dh_missing
>> make[1]: Entering direc
On 1/9/23 12:55 PM, Hans van Kranenburg wrote:
> Hi!
>
> On 09/01/2023 18:44, Chuck Zmudzinski wrote:
> ...
> This is why it is very much recommended to build the packages using
> something like sbuild, so that you can be sure that every time it will
> start with a super mini
Source: xen
Version: 4.17.0-1
Severity: normal
Tags: ftbfs patch
Dear Maintainer,
Hi,
I needed to test a patch to libxl so I started by trying to build
xen from source on an up-to-date sid installation.
The build failed:
debian/rules override_dh_missing
make[1]: Entering directory
On 1/9/23 12:55 PM, Hans van Kranenburg wrote:
> 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/
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 Kranenburg wrote:
>> > > Hi!
>> > >
>>
On 1/13/23 6:59 PM, Hans van Kranenburg wrote:
> 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
On 1/13/2023 9:08 PM, Chuck Zmudzinski wrote:
> On 1/13/23 6:59 PM, Hans van Kranenburg wrote:
> > 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
Sorry, the patch I posted in the original message will not apply properly.
I forgot I also edited the comment:
Here is the correct patch:
--- rules 2022-12-21 16:34:51.0 -0500
+++ rules.new 2023-01-08 05:31:24.0 -0500
@@ -327,9 +327,9 @@
| xargs -0r gzip -9vn
#
in src:xen, since the original reporter
has not been able to identify a commit in src:linux that caused
the bug and no one has been able to reproduce the bug on
Xen-4.11/Linux-4.19.194-3.
Regards,
Chuck Zmudzinski
On 9/25/2021 11:27 PM, 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 version of Xen-4.14 for bullseye as a dom0. I am not
inclined to try it until an official Debian developer
78 matches
Mail list logo
