public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Friedrich Weber <f.weber@proxmox.com>
To: Fiona Ebner <f.ebner@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-storage 2/2] plugin: rbd: pass rxbounce when mapping Windows VM disks
Date: Tue, 28 Oct 2025 16:35:05 +0100	[thread overview]
Message-ID: <d0bf155d-56a8-4e2f-b4d8-bd6048e16d4f@proxmox.com> (raw)
In-Reply-To: <3377baa2-e708-4d7e-a96d-9ae42ccb7f0e@proxmox.com>

On 28/10/2025 13:19, Fiona Ebner wrote:
> Am 24.10.25 um 2:27 PM schrieb Friedrich Weber:
>> rxbounce can be needed to avoid "bad crc/signature" errors when
>> running Windows VM disks on KRBD. When mapping a volume, check
>> the guest-ostype hint, and if it denotes the volume is mapped
>> as part of a Windows VM, pass rxbounce.
>>
>> Signed-off-by: Friedrich Weber <f.weber@proxmox.com>
>> ---
>>  src/PVE/Storage/RBDPlugin.pm | 13 +++++++++----
>>  1 file changed, 9 insertions(+), 4 deletions(-)
>>
>> diff --git a/src/PVE/Storage/RBDPlugin.pm b/src/PVE/Storage/RBDPlugin.pm
>> index cf371c7..54c5a57 100644
>> --- a/src/PVE/Storage/RBDPlugin.pm
>> +++ b/src/PVE/Storage/RBDPlugin.pm
>> @@ -793,7 +793,7 @@ sub deactivate_storage {
>>  }
>>  
>>  sub map_volume {
>> -    my ($class, $storeid, $scfg, $volname, $snapname) = @_;
>> +    my ($class, $storeid, $scfg, $volname, $snapname, $hints) = @_;
>>  
>>      my ($vtype, $img_name, $vmid) = $class->parse_volname($volname);
>>  
>> @@ -807,7 +807,12 @@ sub map_volume {
>>      # features can only be enabled/disabled for image, not for snapshot!
>>      $krbd_feature_update->($scfg, $storeid, $img_name);
>>  
>> -    my $cmd = $rbd_cmd->($scfg, $storeid, 'map', $name);
>> +    my @options = ();
>> +    if (defined($hints->{'guest-ostype'}) && $hints->{'guest-ostype'} =~ /^w/) {
> 
> As already said in the last patch, this is a no-go. The RBD plugin
> should not be concerned with knowing how qemu-server defines (Windows)
> guest OS types.

Makes sense, will change this!


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


  reply	other threads:[~2025-10-28 15:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-24 12:25 [pve-devel] [RFC qemu-server/storage 0/3] fix #5779: introduce guest hints to pass rxbounce flag to KRBD Friedrich Weber
2025-10-24 12:25 ` [pve-devel] [PATCH pve-storage 1/2] plugin: map/activate volume: allow callers to pass hints Friedrich Weber
2025-10-28 12:17   ` Fiona Ebner
2025-10-24 12:25 ` [pve-devel] [PATCH pve-storage 2/2] plugin: rbd: pass rxbounce when mapping Windows VM disks Friedrich Weber
2025-10-28 12:19   ` Fiona Ebner
2025-10-28 15:35     ` Friedrich Weber [this message]
2025-10-24 12:25 ` [pve-devel] [PATCH qemu-server 1/1] fix #5997: qemu: pass guest-ostype hint when activating volumes Friedrich Weber
2025-10-28  9:02 ` [pve-devel] [RFC qemu-server/storage 0/3] fix #5779: introduce guest hints to pass rxbounce flag to KRBD Friedrich Weber
2025-10-28 10:50   ` Fiona Ebner
2025-10-28 11:12     ` Fiona Ebner
2025-10-28 12:10 ` Fiona Ebner
2025-10-28 16:35   ` Friedrich Weber

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=d0bf155d-56a8-4e2f-b4d8-bd6048e16d4f@proxmox.com \
    --to=f.weber@proxmox.com \
    --cc=f.ebner@proxmox.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