nit: a slightly more telling subject could have been something like:
backport limiting the phys-bits to 46 for bug in old guest kernel Am 05/06/2023 um 09:43 schrieb Fiona Ebner: > by limiting the phys-bits to 46 instead of 47. On Ubuntu 18.04 with > kernel 4.15, using 47 leads to a strange issue where initialization of > VirtIO devices would fail. > > Reported in the community forum: > https://forum.proxmox.com/threads/127410/ > > Signed-off-by: Fiona Ebner <f.eb...@proxmox.com> > --- > ...latformInitLib-limit-phys-bits-to-46.patch | 46 +++++++++++++++++++ > debian/patches/series | 1 + > 2 files changed, 47 insertions(+) > create mode 100644 > debian/patches/0001-OvmfPkg-PlatformInitLib-limit-phys-bits-to-46.patch > > applied, but fixed line endings of patch, edk2 (sadly) uses Windows-Style \r\n, but the patch only got \n, so failed building a DSC: cd pve-edk2-firmware-3.20230228; dpkg-buildpackage -S -uc -us -d # ... patching file OvmfPkg/Library/PlatformInitLib/MemDetect.c Hunk #1 FAILED at 657 (different line endings). 1 out of 1 hunk FAILED dpkg-source: info: the patch has fuzz which is not allowed, or is malformed dpkg-source: info: if patch '0001-OvmfPkg-PlatformInitLib-limit-phys-bits-to-46.patch' is correctly applied by quilt, use 'quilt refresh' to update it dpkg-source: info: if the file is present in the unpacked source, make sure it is also present in the orig tarball dpkg-source: info: restoring quilt backup files for 0001-OvmfPkg-PlatformInitLib-limit-phys-bits-to-46.patch dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -E -b -B .pc/0001-OvmfPkg-PlatformInitLib-limit-phys-bits-to-46.patch/ --reject-file=- < pve-edk2-firmware-3.20230228/debian/patches/0001-OvmfPkg-PlatformInitLib-limit-phys-bits-to-46.patch subprocess returned exit status 1 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
