all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Alexandre Derumier via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Alexandre Derumier <alexandre.derumier@groupe-cyllene.com>
Subject: [pve-devel] [PATCH SERIES storage/qemu-server/-manager] RFC : add lvmqcow2 storage support
Date: Mon, 26 Aug 2024 13:00:18 +0200	[thread overview]
Message-ID: <mailman.412.1724670071.302.pve-devel@lists.proxmox.com> (raw)

[-- Attachment #1: Type: message/rfc822, Size: 5189 bytes --]

From: Alexandre Derumier <alexandre.derumier@groupe-cyllene.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH SERIES storage/qemu-server/-manager] RFC : add lvmqcow2 storage support
Date: Mon, 26 Aug 2024 13:00:18 +0200
Message-ID: <20240826110030.1744732-1-alexandre.derumier@groupe-cyllene.com>

This patch series add support for a new lvmqcow2 storage format.

Currently, we can't do snasphot && thin provisionning on shared block devices because
lvm thin can't share his metavolume. I have a lot of onprem vmware customers
where it's really blocking the proxmox migration. (and they are looking for ovirt/oracle
virtualisation where it's working fine).

It's possible to format a block device without filesystem with qcow2 format directly.
This is used by redhat rhev/ovirt since almost 10year in their vsdm daemon.

For thin provisiniong or to handle extra size of snapshot, we need to be able to resize
the lvm volume dynamically.
The volume is increased by chunk of 1GB by default (can be changed).
Qemu implement events to sent an alert when the write usage is reaching a threshold.
(Threshold is 50% of last chunk, so when vm have 500MB free)

The resize is async (around 2s), so user need to choose a correct chunk size && threshold,
if the storage is really fast (nvme for example, where you can write more than 500MB in 2ss)

If the resize is not enough fast, the vm will pause in io-error.
pvestatd is looking for this error, and try to extend again if needed and resume the vm


pve-storage:

Alexandre Derumier (5):
  add lvmqcow2 plugin
  vdisk_alloc: add underlay_size option
  add volume_underlay_resize
  add refresh volume
  add volume_underlay_shrink

 src/PVE/Storage.pm                |  52 +++++-
 src/PVE/Storage/LVMQcow2Plugin.pm | 272 ++++++++++++++++++++++++++++++
 src/PVE/Storage/Makefile          |   3 +-
 src/PVE/Storage/Plugin.pm         |  20 +++
 4 files changed, 344 insertions(+), 3 deletions(-)
 create mode 100644 src/PVE/Storage/LVMQcow2Plugin.pm


qemu-server:

Alexandre Derumier (6):
  lvmqcow2: set disk write threshold
  qm cli: add blockextend
  qmevent: call qm disk blockextend when write_threshold event is
    received
  migration: refresh remote disk size before resume
  qemu_img_format: lvmqcow2 is a path_storage
  clone: allocate && shrink lvmcow2 underlay

 PVE/CLI/qm.pm                         |  57 ++++++++++
 PVE/QemuMigrate.pm                    |  13 +++
 PVE/QemuServer.pm                     | 154 +++++++++++++++++++++++++-
 qmeventd/qmeventd.c                   |  27 +++++
 test/MigrationTest/QemuMigrateMock.pm |   2 +
 5 files changed, 251 insertions(+), 2 deletions(-)


pve-manager:

Alexandre Derumier (1):
  pvestatd: lvmqcow2 : extend disk on io-error

 PVE/Service/pvestatd.pm | 62 +++++++++++++++++++++++++++++++++++++++++
 1 file changed, 62 insertions(+)


-- 
2.39.2



[-- 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

             reply	other threads:[~2024-08-26 11:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-26 11:00 Alexandre Derumier via pve-devel [this message]
2024-08-28 12:53 ` Dominik Csapak
2024-08-29  8:27   ` DERUMIER, Alexandre via pve-devel
     [not found]   ` <98a4b03b8969f7c4aef42fc5cdd677752b4dbf83.camel@groupe-cyllene.com>
2024-08-30  8:44     ` DERUMIER, Alexandre via pve-devel
2024-09-05  7:51 ` Fabian Grünbichler

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.412.1724670071.302.pve-devel@lists.proxmox.com \
    --to=pve-devel@lists.proxmox.com \
    --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 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