From: Prashant Patil via pve-devel <pve-devel@lists.proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: Prashant Patil <Prashant.Gamepatil@arctera.io>
Subject: [pve-devel] Unable to create persistent dirty-bitmap
Date: Tue, 23 Sep 2025 05:23:26 +0000 [thread overview]
Message-ID: <mailman.275.1758611651.390.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 12445 bytes --]
From: Prashant Patil <Prashant.Gamepatil@arctera.io>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Unable to create persistent dirty-bitmap
Date: Tue, 23 Sep 2025 05:23:26 +0000
Message-ID: <SA5PPFA482AF7CB3F93BBC9D6DA1A512009E31DA@SA5PPFA482AF7CB.namprd16.prod.outlook.com>
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:~#
Thanks
Prashant
[-- 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 reply other threads:[~2025-09-23 7:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 5:23 Prashant Patil via pve-devel [this message]
[not found] <SA5PPFA482AF7CB3F93BBC9D6DA1A512009E31DA@SA5PPFA482AF7CB.namprd16.prod.outlook.com>
2025-09-23 9:30 ` 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=mailman.275.1758611651.390.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=Prashant.Gamepatil@arctera.io \
/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.