all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] applied: [PATCH edk2-firmware] add patch to work around older guest kernel bug
Date: Wed, 7 Jun 2023 11:04:34 +0200	[thread overview]
Message-ID: <f408dd24-a12e-00f0-513d-72f91f0db50a@proxmox.com> (raw)
In-Reply-To: <5ef14027-21ba-53d6-1520-5b11cb5e3434@proxmox.com>

Am 06.06.23 um 16:26 schrieb Thomas Lamprecht:
> 
> nit: a slightly more telling subject could have been something like:
> 
> backport limiting the phys-bits to 46 for bug in old guest kernel

Yes, sorry. My commit title was too generic.

> 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.ebner@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:
> 

Hmm, it's correct in my repository and in the formatted patch, but not
here in the mail anymore. Do I need to specify something special with
git send-email?




  reply	other threads:[~2023-06-07  9:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-05  7:43 [pve-devel] " Fiona Ebner
2023-06-06 14:26 ` [pve-devel] applied: " Thomas Lamprecht
2023-06-07  9:04   ` Fiona Ebner [this message]
2023-06-07 10:12     ` Fiona Ebner
2023-06-07 10:25       ` Thomas Lamprecht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f408dd24-a12e-00f0-513d-72f91f0db50a@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=t.lamprecht@proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal