all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: Drew Green <agreenbhm@gmail.com>
Subject: Re: [pve-devel] [PATCH qemu-server 1/1] QemuServer.pm: add support for storing VM memory in /dev/shm
Date: Wed, 14 Jan 2026 13:53:04 +0100	[thread overview]
Message-ID: <d9e3597a-b492-46e5-95b7-434ee94924e1@proxmox.com> (raw)
In-Reply-To: <mailman.1348.1763589054.362.pve-devel@lists.proxmox.com>

Hi,

Am 19.11.25 um 10:50 PM schrieb Drew Green via pve-devel:
> PVE supports the VM option "ivshmem" which creates a memory-backed file on
> the host operating system in /dev/shm to allow sharing resources between
> the guest and host and other guests.  There is currently no support for
> utilizing the Qemu feature to make the guest's system memory available via
> the filesystem, which can be useful for experimentation and testing
> purposes.  This patch adds an additional boolean option to the existing
> "ivshmem" configuration called "ram", which when set to 1 will store the
> guest's memory in the same location in /dev/shm that "ivshmem" normally
> would.  Additional logic is added to support that option, such as adding an
> additional "-machine" argument required for this and excluding the
> "-device" argument normally required for traditional "ivshmem".

yes, it is a rather niche use case. You can also add the machine flag
and object via custom '-args' in the VM configuration. Would using that
instead work for you? If yes, I'd rather postpone this, but feel free to
open a feature request on the bugzilla (referring back to your patch),
so we can better track interest from other users.

For completeness, regarding the patch submission: please use 'git
format-patch' to generate the email. And we'd also need a signed CLA and
a Signed-off-by trailer to be able to accept your patch. For details,
see: https://pve.proxmox.com/wiki/Developer_Documentation

Best Regards,
Fiona


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


      reply	other threads:[~2026-01-14 12:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19 21:50 Drew Green via pve-devel
2026-01-14 12:53 ` Fiona Ebner [this message]

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=d9e3597a-b492-46e5-95b7-434ee94924e1@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=agreenbhm@gmail.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 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