public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: "joao.sousa" <joao.sousa@eurotux.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH-SERIES v6 pve-storage/qemu-server/pve-qemu] add external qcow2 snapshot support
Date: Mon, 16 Jun 2025 10:34:56 +0200	[thread overview]
Message-ID: <acc00cf2-c269-4a42-98ea-0f430449b04d@proxmox.com> (raw)
In-Reply-To: <zwkygc6va6jmieho2h7gqsx4idrgrxvd7et2kfbi3vyddhjk7c@kfiwufb7auvv>

Am 13.06.25 um 12:25 schrieb joao.sousa:
> On 12/06/25 10:12, Fiona Ebner wrote:
>> The tests in qemu-server were updated since then. You can check out an
>> earlier commit and apply on top of that. For pve-storage, I'd guess it
>> was the code style changes, so same story:
> 
> I reverted qemu-server to commit 1fd1ca60, however it still fails to
> apply patch 12:
> 
> [PATCH qemu-server 12/13] blockdev: add backing_chain support
> 
> Applying: blockdev: add backing_chain support
> error: corrupt patch at line 18
> Patch failed at 0012 blockdev: add backing_chain support
> hint: Use 'git am --show-current-patch=diff' to see the failed patch

Right, that one failed for me as well. Didn't check out why exactly, but
there will be a separate series for the switch to blockdev [0]. After
that, Alexandre can rebase the changes for external snapshot on top and
send another version of the patches.

[0]:
https://lore.proxmox.com/pve-devel/mailman.381.1750055007.395.pve-devel@lists.proxmox.com/T/


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  parent reply	other threads:[~2025-06-16  8:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-03  7:55 Alexandre Derumier via pve-devel
2025-06-05 13:53 ` Fiona Ebner
2025-06-05 14:08   ` DERUMIER, Alexandre via pve-devel
     [not found]   ` <0aa862ab988ff9df50f4637f3712f137f23c34c2.camel@groupe-cyllene.com>
2025-06-05 14:19     ` Fiona Ebner
2025-06-06 10:17 ` joao.sousa via pve-devel
2025-06-10  8:54   ` Fiona Ebner
2025-06-11 21:28     ` joao.sousa via pve-devel
     [not found]     ` <5sqpzsnyzmfvvoco3ilo6tg3pcpomhle7h5dsnmbsbdjobpr5a@rqfsbsas36e2>
2025-06-12  7:02       ` DERUMIER, Alexandre via pve-devel
2025-06-12  8:12       ` Fiona Ebner
2025-06-13 10:25         ` joao.sousa via pve-devel
     [not found]         ` <zwkygc6va6jmieho2h7gqsx4idrgrxvd7et2kfbi3vyddhjk7c@kfiwufb7auvv>
2025-06-16  8:34           ` Fiona Ebner [this message]
     [not found]       ` <8cbed06bbe3db00e96670dec1e240123b946a917.camel@groupe-cyllene.com>
2025-06-12 11:33         ` DERUMIER, Alexandre via pve-devel
     [not found]         ` <a7185aa585b414710be6e09729adda57ed3787b8.camel@groupe-cyllene.com>
2025-06-13 16:42           ` joao.sousa--- via pve-devel
     [not found]           ` <qss36oltvd4gz5tiss7dqono5h2zmsgwmodj4cqkroboizypwj@kbyz3mymh75a>
2025-06-16  5:50             ` DERUMIER, Alexandre via pve-devel

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=acc00cf2-c269-4a42-98ea-0f430449b04d@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=joao.sousa@eurotux.com \
    --cc=pve-devel@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal