Bug#991967: #991967: Simply ACPI powerdown/reset issue?
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.
Apparently few others have run into it, yet it is reliable for me. Have
you tried the combination? Works? Panics?
I have not tried ballooning HVM or PVH domains. If the Xen
hypervisor is crashing when ballooning unprivileged domains,
doesn't that support my belief that there are bugs in src:xen
rather than in src:linux?
No.
I still think the patches to fix a panic on devices using the arm
architecture
are a bit aggressive for the Debian Xen package for Debian stable. Those
patches upstream are intended for Xen unstable, which is currently
Xen 4.16. Such patches do not belong in a stable Xen 4.14 package for
Debian stable, especially after it can be proven they cause a regression
for Xen users of amd64 devices, the regression being that they break the
proper shutdown functioning of amd64 devices.
I think the correct Debian way to support the arm devices that
panic on a true upstream Xen 4.14 hypervisor without the
patches for arm that cause dom0 to not power off properly on
amd64 is by first testing the arm patches as part of a new Xen 4.16
unstable Xen package for Debian unstable, then follow ordinary
development procedures for porting Xen 4.16 to bookworm/testing,
and then finally a backport of Xen 4.16 to bullseye. That is the
only way I can see this being done without causing grief to
Xen users who want a stable Xen on a stable Debian, unless
upstream can help with porting the arm patches back to Xen 4.14
in such a way that they don't break things on amd64.
This was also deliberately not copied to #991967 since this is unrelated.
I'm concerned this second one might be Debian, but the small delta makes
me think it likely originates from upstream Xen. I was wondering whether
you had seen it since I haven't found other reports.
(note, if you try recreating, this is a Xen panic, all domains get lost)
This is off-topic for bug #991968.
Regards,
Chuck
Reply to: