From: Prashant Patil via pve-devel <pve-devel@lists.proxmox.com>
To: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>,
"pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Cc: Prashant Patil <Prashant.Gamepatil@arctera.io>
Subject: Re: [pve-devel] Unable to create persistent dirty-bitmap
Date: Tue, 23 Sep 2025 10:16:48 +0000 [thread overview]
Message-ID: <mailman.312.1758641848.390.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <e88c612071187386f7178a4d519fad7c7f39ab09.camel@groupe-cyllene.com>
[-- Attachment #1: Type: message/rfc822, Size: 16787 bytes --]
From: Prashant Patil <Prashant.Gamepatil@arctera.io>
To: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>, "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Subject: RE: Unable to create persistent dirty-bitmap
Date: Tue, 23 Sep 2025 10:16:48 +0000
Message-ID: <SA5PPFA482AF7CB2ED9FA29E8032762B5A6E31DA@SA5PPFA482AF7CB.namprd16.prod.outlook.com>
The qcow2 disk is at scsi0 slot, hence I think that is the correct node. Please let me know if otherwise.
Thanks
Prashant
-----Original Message-----
From: DERUMIER, Alexandre <alexandre.derumier@groupe-cyllene.com>
Sent: 23 September 2025 03:00 PM
To: pve-devel@lists.proxmox.com; Prashant Patil <Prashant.Gamepatil@arctera.io>
Subject: Re: Unable to create persistent dirty-bitmap
>>-------- Message initial --------
>>De: Prashant Patil <Prashant.Gamepatil@arctera.io>
>>À: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
>>Objet: Unable to create persistent dirty-bitmap
>>Date: 23/09/2025 07:23:26
>>Hello,
>>We have configured 'Directory' storage having SAN as backing storage,
>>the SAN storage is mounted at file system path (/mnt/pve/SAN-
>>Storage1) with type ext4. We have couple of VMs running on this
>>storage. When we try to create a persistent bitmap on qcow2 file then
>>that fails with below error. The disk at 'scsi0' is "scsi0: SAN-
>>Storage1:101/vm-101-disk-1.qcow2,iothread=1,size=32G". So, the
>>question here is, why are we getting error to create persistent bitmap
>>for qcow2 disk?
>>
>>root@be1-proxmox1:~# echo '{"execute": "qmp_capabilities"}{"execute":
>>"block-dirty-bitmap-add", "arguments": {"node":"drive-
>>scsi0","name":"bm_1","persistent":true}}' | socat - unix-
>>connect:/var/run/qemu-server/101.qmp
>>{"QMP": {"version": {"qemu": {"micro": 2, "minor": 0, "major": 10},
>>"package": "pve-qemu-kvm_10.0.2-4"}, "capabilities": []}}
>>{"return": {}}
>>{"error": {"class": "GenericError", "desc": "Can't store persistent
>>bitmaps to drive-scsi0: Operation not supported"}}
>>root@be1-proxmox1:~#
I'm not 100% sure, but maybe is it the wrong node ? (on machine model 10, with blockdev enable, we use a throttle node at top node ("drive- scsi0"), maybe it need to be done on the "format" node where qcow2 is available
for example:
-blockdev '{"driver":"throttle","file":{"cache":{"direct":true,"no-
flush":false},"driver":"qcow2","file":{"aio":"io_uring","cache":{"direc
t":true,"no-flush":false},"detect-
zeroes":"unmap","discard":"unmap","driver":"file","filename":"/var/lib/
vz/images/8006/vm-8006-disk-0.qcow2","node-
name":"edd19f6c1b3a6d5a6248c3376a91a16","read-only":false},"node-
name":"fdd19f6c1b3a6d5a6248c3376a91a16","read-only":false},"node-
name":"drive-virtio0","throttle-group":"throttle-drive-virtio0"}'
you should use the node "fdd19f6c1b3a6d5a6248c3376a91a16"
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-09-23 15:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SA5PPFA482AF7CB3F93BBC9D6DA1A512009E31DA@SA5PPFA482AF7CB.namprd16.prod.outlook.com>
2025-09-23 9:30 ` DERUMIER, Alexandre via pve-devel
[not found] ` <e88c612071187386f7178a4d519fad7c7f39ab09.camel@groupe-cyllene.com>
2025-09-23 10:16 ` Prashant Patil via pve-devel [this message]
[not found] ` <SA5PPFA482AF7CB2ED9FA29E8032762B5A6E31DA@SA5PPFA482AF7CB.namprd16.prod.outlook.com>
2025-09-23 14:58 ` DERUMIER, Alexandre via pve-devel
2025-09-23 5:23 Prashant Patil 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=mailman.312.1758641848.390.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=Prashant.Gamepatil@arctera.io \
--cc=alexandre.derumier@groupe-cyllene.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